openstack
/
fuel-virtualbox
Code Issues Proposed changes
RETIRED, A set of bash scripts that allow to easily deploy Fuel environment and try OpenStack using VirtualBox as a virtualization layer.
105 Commits 2 Branches 12 Tags 628 KiB
Go to file
Ivan Suzdal 7bbe98976d Fix mac generate for non-GNU awk. 
Default awk in MacOSX has no gensub function.

Closes-Bug: #1517145

Change-Id: I7cda2e0ed6cdc29dc16ef74fd2cab7b8e3d735ea
 		2015-11-24 18:57:00 +00:00
actions Fix mac generate for non-GNU awk. 2015-11-24 18:57:00 +00:00
functions Use right way to skip fuelmenu 2015-10-05 10:18:25 +00:00
iso [vbox] Created folder for iso in virtualbox 2013-07-25 14:48:53 +00:00
README.md Added support to deploy product on remote machine via ssh 2015-09-23 12:54:42 +03:00
clean.sh Add script to delete host-only network interfaces 2015-10-22 18:58:35 +03:00
config.sh Enable VRDE option for VMs in vbox scripts 2015-09-24 15:03:52 +03:00
launch.sh Added support to deploy product on remote machine via ssh 2015-09-23 12:54:42 +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".

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