$ ./launch_8GB.sh
Checking for 'expect'... OK
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"
Checking for "VBoxManage"... OK
Checking for VirtualBox Extension Pack... OK
Checking for Mirantis OpenStack ISO image... OK
Going to use Mirantis OpenStack ISO file iso/fuel-6.1-437-2015-05-19_10-05-51.iso
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Setup is done.
Deleting host-only interface: vboxnet0...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting host-only interface: vboxnet1...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Deleting host-only interface: vboxnet2...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Creating host-only interface
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface vboxnet0 was successfully created
Disabling DHCP server on interface: vboxnet0...
Configuring IP address 10.20.0.1 and network mask 255.255.255.0 on interface: vboxnet0...
+ VBoxManage hostonlyif ipconfig vboxnet0 --ip 10.20.0.1 --netmask 255.255.255.0
+ set +x
Verifying interface vboxnet0 has IP 10.20.0.1 and mask 255.255.255.0 properly set.
OK.
Creating host-only interface
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface vboxnet1 was successfully created
Disabling DHCP server on interface: vboxnet1...
Configuring IP address 172.16.0.254 and network mask 255.255.255.0 on interface: vboxnet1...
+ VBoxManage hostonlyif ipconfig vboxnet1 --ip 172.16.0.254 --netmask 255.255.255.0
+ set +x
Verifying interface vboxnet1 has IP 172.16.0.254 and mask 255.255.255.0 properly set.
OK.
Creating host-only interface
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface vboxnet2 was successfully created
Disabling DHCP server on interface: vboxnet2...
Configuring IP address 172.16.1.1 and network mask 255.255.255.0 on interface: vboxnet2...
+ VBoxManage hostonlyif ipconfig vboxnet2 --ip 172.16.1.1 --netmask 255.255.255.0
+ set +x
Verifying interface vboxnet2 has IP 172.16.1.1 and mask 255.255.255.0 properly set.
OK.
Virtual machine 'fuel-master' is created and registered.
UUID: b8dd01f0-b0df-4d70-b292-240f643aefc9
Settings file: '/home/kromanenko/VirtualBox VMs/fuel-master/fuel-master.vbox'
Adding hostonly adapter to fuel-master and bridging with host NIC vboxnet0...
Adding disk to fuel-master, with size 65535 Mb...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Disk image created. UUID: dae48d2f-73a3-4c0d-953d-4fb7277ff718
Adding serial numbers of disks to fuel-master...
Adding hostonly adapter to fuel-master and bridging with host NIC vboxnet1...
Adding NAT adapter to fuel-master for outbound network access through the host system...
Waiting for VM "fuel-master" to power on...
VM "fuel-master" has been successfully started.
Waiting for product VM to install. Please do NOT abort the script...
--
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OS: Ubuntu 14.04 LTS Desktop
VB: Version 4.3.30
RAM: 8GB
Disk: 500GB
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I got to install the Fuel Master Node, but the Slave Nodes I didn't.
Do I need to have internet connectivity on my host machine to complete this deployment?
Fuel master node should have Internet access during the last phase because it builds the bootstrap image used by slave nodes to boot.