RETIRED, A set of bash scripts that allow to easily deploy Fuel environment and try OpenStack using VirtualBox as a virtualization layer.
Go to file
Jenkins 313f515875 Merge "Restore forgotten kernel name for VirtualBox" 2016-01-26 09:47:48 +00:00
actions Restore forgotten kernel name for VirtualBox 2016-01-25 23:53:51 +03:00
drivers ROM firmware is optional now 2015-12-22 11:50:35 +03:00
functions Use BSD's 'sed' regexp on MacOSX 2016-01-25 19:49:16 +03:00
iso [vbox] Created folder for iso in virtualbox 2013-07-25 14:48:53 +00:00
README.md Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
clean.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
config.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
dumpkeys.cache Do not hardcode scancodes that change isolinux boot params 2015-12-17 12:09:23 +03:00
launch.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
launch_8GB.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
launch_16GB.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00

README.md

VirtualBox enviropment kit

Requirements

  • VirtualBox with VirtualBox Extension Pack
  • procps
  • expect
  • openssh-client
  • xxd
  • 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 you run this script under Cygwin, you may have to add path to VirtualBox directory to your PATH. Usually it is enough to run: export PATH=$PATH:/cygdrive/c/Program Files/Oracle/VirtualBox

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".

To shutdown VMs and clean environment just run "./clean.sh"

To deploy on a remote machine just set environment variable REMOTE_HOST with ssh connection string. The variable REMOTE_PORT allows to specify custom port for ssh.

 REMOTE_HOST=user@user.mos.mirantis.net ./launch_8GB.sh
# or
 REMOTE_HOST=user@user.mos.mirantis.net REMOTE_PORT=23 ./launch_8GB.sh

TODO

  • add the ability to use Boot ROM during the remote deploy
  • add the new (even smaller) Boot ROM with iPXE HTTP enabled