Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have about a dozen rather beefy machines on a separate network. This network is not (will not be, cannot be) connected to the internet. I'd like to deploy Openstack on them so that they can be used as a sort of internal cloud hosting solution. This will be a sort of "prototyping environment", so while I can tolerate things being a bit rough around the edges, the main aim is still getting work done with the machines, not merely messing around with Openstack.

Here's the options I've come up so far:

  • Run a local mirror of the relevant repositories and install a script-based installation solution such as Alamo 3+. I'm not entirely sure how to find out what all the relevant repositories are though, and I'm not looking forward to finding out using trial-and-error.
  • Use crowbar to build a stand-alone ISO, or use one of the provided ones. I'm not completely clear on whether these are supposed to work without Internet access though.
  • Use the Alamo 2.0 ISO, which uses the older Exeter version of Openstack.

I'm sure I've missed about a dozen other options. I'd like to stay away from commercial vendors if possible.

What is the best way to achieve this, in terms of effort, functionality and future-proofness?

share|improve this question
    
Does the downvoter care to comment? If the question is off-topic or otherwise unsuitable for this stack, I'll gladly take it elsewhere. If it is poorly worded or unclear, I'll do what I can to clean it up. –  user181241 Jul 11 '13 at 18:47
add comment

2 Answers

Consider creating a local private mirror of your favorite Openstack-containing distribution, such as CentOS, Fedora, Ubuntu, etc. Once you have set up the local mirror (on a networked machine) using the distribution's instructions, walk it over the air gap on an external hard drive to the disconnected network for use there.

To obtain updates, you can simply update the mirror on the network, and then walk it over the air gap again.

share|improve this answer
add comment

It is probably not the most efficient solution, but have you considered setting up OpenStack on a virtual machine and then just migrating it to your environment? That seems to be the least painful solution.

We almost had to resort to that because our web proxies were behaving weirdly, but managed to resolve it.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.