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
Maksim Malchuk b48c7f5293 VirtualBox network fixes and the dockerless mode support
This commit include changes:

 * using the VirtualBox scripts the Fuel master node now always
   booted with kernel option 'wait_for_external_config=yes' to
   provide the same deployment functionality as in the 'fuel-qa'.

 * settings for the kernel command line moved to the top config
   file, because the settings wich could be edited should be placed
   there.

 * because of configuration task moved to the correct place there
   is no need to parse 'bootstrap_admin_node.log' and always follow
   the changes in the 'fuel-library', so all parsing logic removed
   from the scripts. This also simplifies networking changes and
   there is no need to patch the files on the fly and restart
   docker containers if they used.

 * variable 'vm_master_nat_gateway' removed from the 'config.sh'
   and from the 'enable_outbound_network_for_product_vm' because
   gateway should be set from the DHCP lease.

 * the sysconfig configuration files on the fuel master node now
   configured the right way. the backup files for configuration
   files are created. also added some comments for changes in the
   scripts.

 * now the default routing on the fuel master node correctly
   configured without creating the second default route. also
   ZeroConf route creation and NetworkManager now switched off
   to correct work of the network service.

 * the 'resolv.conf', 'dnsmasq.upstream' and 'astute.yaml' now
   correctly modified and could contain up to three DNS nameservers.

 * added support for the new dockerless 9.0 Fuel.

Implements blueprint: get-rid-docker-containers

Change-Id: I8f32fb8105d0781938757fa13d5dcbbacbf9c845
Closes-Bug: #1544241
Partial-Bug: #1323365
2016-02-15 00:13:47 +03:00
actions VirtualBox network fixes and the dockerless mode support 2016-02-15 00:13:47 +03:00
drivers ROM firmware is optional now 2015-12-22 11:50:35 +03:00
functions VirtualBox network fixes and the dockerless mode support 2016-02-15 00:13:47 +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 VirtualBox network fixes and the dockerless mode support 2016-02-15 00:13:47 +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