Open Stack

Just a note that this patch is install-guide specific.

It shows newcomers to OpenStack how they can use VirtualBox to completely emulate the environment outlined in the install-guide.  It allows the user to enter all the same networking values to eliminate confusion and reduce complexity.

As previously mentioned by others, probably not appropriate for official install-guide docs but perhaps a blog post.

Matt Dorn
Rackspace Training

> On Nov 14, 2015, at 12:34 AM, Roger Luethi <rl at patchworkscience.org> wrote:
> 
> The training-labs project [1] already provides an automated way of setting
> up a VirtualBox (soon also KVM) VM cluster for OpenStack training. It works
> on Linux, OS X, and Windows.
> 
> The user can stop right there and proceed with a manual installation, or
> have the scripts do the complete deployment as described in the
> install-guide.
> 
> In other words, the user can get:
> 1) just the empty VMs, set up for OpenStack
> 2) VMs with the OS installed, but without OpenStack
> 3) VMs with OS and OpenStack ready to use
> 
> Current default is 3), but we can provide configuration templates for each.
> 
> Why don't you point to the training-labs project instead?
> 
> Roger
> 
> [1] http://git.openstack.org/cgit/openstack/training-labs/
> 
>> On Thu, 12 Nov 2015 17:08:13 -0700, Matt Kassawara wrote:
>> A rather significant number of people deploy OpenStack for the first time
>> using VMs rather than bare metal. Several cycles ago, we decided to provide
>> some basic notes (e.g., disable MAC address filtering and/or enable
>> promiscuous mode depending on the hypervisor) rather than developing
>> step-by-step instructions for those using VMs for the following reasons:
>> 
>> 1) Given our proactive approach of updating and testing the installation
>> content for each release, we would need additional resources to reasonably
>> test it using VMs.
>> 2) We would need additional resources to maintain the VM deployment content
>> including bug triage.
>> 3) Supporting one hypervisor means requests to support additional
>> hypervisors, each requiring additional resources.
>> 4) Not sure how to handle potential license incompatibilities.
>> 5) Most hypervisors use GUIs and screen shots don't translate.
>> 
>> A patch currently resides in the queue [1] that provides step-by-step
>> instructions for deploying VMs using VirtualBox. We need to discuss the
>> possibility of merging this patch into the installation guide and how to
>> address these (and potentially other) issues around it.
>> 
>> Matt
>> 
>> [1] https://review.openstack.org/#/c/241320/
> 
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs