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.
109 Commits 2 Branches 12 Tags 628 KiB
Go to file
Dmitry Bilunov 95a5cfb6f1 Do not hardcode scancodes that change isolinux boot params 
We have a "skipfuelmenu" variable in virtualbox scripts, which allows to
skip "fuelmenu" step during the installation procedure. This option is
enabled by default.

Currently, we have a hardcoded variable $boot_line, which contains scan
codes, passed by VirtualBox into isolinux on an emulated keyboard.

We should generate these scancodes from a user specified line instead of
hardcoding them.

Partial-Bug: 1525967
Change-Id: Ia2419b5e2eaa4b30cd2876112d7c080abbebcba5
 		2015-12-17 12:09:23 +03:00
actions Do not hardcode scancodes that change isolinux boot params 2015-12-17 12:09:23 +03:00
functions Do not hardcode scancodes that change isolinux boot params 2015-12-17 12:09:23 +03: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
dumpkeys.cache Do not hardcode scancodes that change isolinux boot params 2015-12-17 12:09:23 +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