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.
136 Commits 2 Branches 12 Tags 628 KiB
Go to file
Igor Kalnitsky 9373c6e955 Fix public network routing from slaves 
Since we assign public gateway address on master node, all public
traffic goes through it. Unfortunately, it doesn't reach destination due
to rejecting rule in FORWARD chain:

    ACCEPT              all  --  10.20.0.0/24         anywhere
    ACCEPT              all  --  anywhere             anywhere
    REJECT              all  --  anywhere             anywhere
    ext-filter-forward  all  --  anywhere             anywhere

The commit fixes that problem by inserting (-I), not appending (-A)
ext-filter-forward entry. In that case that rule will have higher
priority and won't break routing.

    ACCEPT              all  --  10.20.0.0/24         anywhere
    ACCEPT              all  --  anywhere             anywhere
    ext-filter-forward  all  --  anywhere             anywhere
    REJECT              all  --  anywhere             anywhere

Change-Id: I7887f08a175fa0ce06654dc1fc18ab412cb296f5
Closes-Bug: #1566968
(cherry picked from commit 80e86854be)
 		2016-04-11 09:36:38 +03:00
actions Add checks for the file 'dumpkeys.cache' 2016-02-27 15:47:32 +03:00
drivers ROM firmware is optional now 2015-12-22 11:50:35 +03:00
functions Fix public network routing from slaves 2016-04-11 09:36:38 +03:00
iso [vbox] Created folder for iso in virtualbox 2013-07-25 14:48:53 +00:00
.gitignore Add maintenance files 2016-02-23 01:15:18 +03:00
.gitreview Add maintenance files 2016-02-23 01:15:18 +03:00
MAINTAINERS Update MAINTAINERS 2016-03-14 14:56:14 +03:00
README.md Added a requirement for Internet access 2016-03-02 16:39:47 +03:00
clean.sh Fix PATH issue for VirtualBox on Windows 2016-01-22 08:22:10 +03:00
config.sh Enable 'skipfuelmenu' because 'showmenu=yes' is used 2016-03-22 19:04:46 +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

Mirantis VirtualBox scripts

Mirantis VirtualBox scripts are used to automate the installation of Fuel and Mirantis OpenStack. When you install Mirantis OpenStack using the Mirantis VirtualBox scripts, you do not need to configure the virtual machine network and hardware settings. The script automatically provisions the virtual machines with all required settings. However, you must place the latest Mirantis OpenStack ISO image in the iso directory. You may also modify the number of Fuel Slave nodes using the config.sh script.

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
  • Enable Internet access

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, it will automatically add the path to the VirtualBox directory to your PATH.

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