openstack
/
fuel-main
Code Issues Proposed changes
fuel-main/virtualbox
History
Serhiy Ovsianikov 13b3e9cf07 VBox - there are a lot of ssh.exe processes under Cygwin 
When we execute the installation of the Fuel master node we are
launching ssh commands and checking messages in the file
bootstrap_admin_node.log. If the ssh processes accumulate in the
operating system you could see the following error: “The system
has no more ptys”.
Also Cygwin does not work correctly with the command
"send "res=$(for i in 1 2 3 4...)"

Change-Id: I30aab51452505e88c18abc866f88efde2d7650fb
Closes-Bug: #1457956
 		2015-05-25 10:14:23 +03:00
..
actions Fix for VBox "No Internet connection on compute nodes" 2015-05-14 20:20:57 +03:00
functions VBox - there are a lot of ssh.exe processes under Cygwin 2015-05-25 10:14:23 +03:00
iso [vbox] Created folder for iso in virtualbox 2013-07-25 14:48:53 +00:00
README.md Fix for VBox "No Internet connection on compute nodes" 2015-05-14 20:20:57 +03:00
config.sh Fix for VBox "No Internet connection on compute nodes" 2015-05-14 20:20:57 +03:00
launch.sh Fix for VBox "No Internet connection on compute nodes" 2015-05-14 20:20:57 +03:00
launch_8GB.sh Apply different configurations by separate launchers 2014-09-01 18:18:41 +03:00
launch_16GB.sh Apply different configurations by separate launchers 2014-09-01 18:18:41 +03:00

README.md

VirtualBox enviropment kit

Requirements

  • VirtualBox with VirtualBox Extension Pack
  • procps
  • expect
  • Cygwin for Windows host PC
  • Enable VT-x/AMD-V acceleration option on your hardware for 64-bits guests

Run

In order to successfully run Mirantis OpenStack under VirtualBox, you need to:

  • download the official release (.iso) and place it under 'iso/' directory
  • run "./launch.sh" (or "./launch_8GB.sh" or "./launch_16GB.sh" according to your system resources). It will automatically pick up the iso and spin up master node and slave nodes

If there are any errors, the script will report them and abort.

If you want to change settings (number of OpenStack nodes, CPU, RAM, HDD), please refer to "config.sh".