Run Flocker with VNX driver in CoreOS Vagrant env on Ubuntu 14.04.
Default Vagrant install on Ubuntu 14.04 gets version 1.4.3-1, which is unsuitable for CoreOS Vagrant VM (which requires at least 1.6.0). Get Vagrant 1.6.5.
sudo wget --no-check-certificate https://dl.bintray.com/mitchellh/vagrant/vagrant_1.6.5_x86_64.deb
sudo dpkg -i vagrant_1.6.5_x86_64.deb
Get VirtualBox:
sudo apt-get install virtualbox
Get VirtualBox extension pack to enable pci passthrough:
root@sclf200:/root/VirtualBox VMs/flocker-coreos-vnx_core-01_1445001054959_92197/Logs# VBoxManage -v
4.3.10_Ubuntur93012
root@sclf200:/root/VirtualBox VMs/flocker-coreos-vnx_core-01_1445001054959_92197/Logs# wget http://download.virtualbox.org/virtualbox/4.3.10/Oracle_VM_VirtualBox_Extension_Pack-4.3.10-93012.vbox-extpack -o /tmp/Oracle_VM_VirtualBox_Extension_Pack-4.3.10-93012.vbox-extpack
root@sclf200:/root/VirtualBox VMs/flocker-coreos-vnx_core-01_1445001054959_92197/Logs# VBoxManage extpack install /tmp/Oracle_VM_VirtualBox_Extension_Pack-4.3.10-93012.vbox-extpack
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully installed "Oracle VM VirtualBox Extension Pack".
Get nfs:
sudo apt-get install nfs-kernel-server
Run lspci -nn | grep Fibre on the host to find PCI address of the host's FC card:
root@sclf200:~/flocker-coreos-vnx# lspci -nn | grep Fibre
81:00.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03)
81:00.1 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03)
root@sclf200:~/flocker-coreos-vnx#
Edit Vagrantfile to attach these FC HBAs. Please choose destination PCI bus:device.function numbers such that bus number is an available PCI bus on guest.
vb.customize ["modifyvm", :id, "--pciattach", "81:00.0@0:08.0"]
vb.customize ["modifyvm", :id, "--pciattach", "81:00.1@0:08.1"]
vagrant up
vagrant ssh core-01
Check that FC device shows up at expected bus:device.function inside CoreOS guest.
core@core-01 ~ $ lspci -nn | grep "Fibre Channel"
00:08.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03)
00:08.1 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter [10df:f100] (rev 03)
core@core-01 ~ $
If you do not see FC card inside CoreOS guest, power off the VM, attempt pciattach from host to find out cause of failure:
root@sclf200:~/flocker-coreos-vnx# VBoxManage controlvm flocker-coreos-vnx_core-01_1444996043539_3663 poweroff
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
root@sclf200:~/flocker-coreos-vnx# VBoxManage modifyvm flocker-coreos-vnx_core-01_1444996043539_3663 --pciattach '81:0.0'
VBoxManage: error: Host PCI attachment only supported with ICH9 chipset
root@sclf200:~/flocker-coreos-vnx# VBoxManage modifyvm flocker-coreos-vnx_core-01_1444996043539_3663 --chipset ich9
root@sclf200:~/flocker-coreos-vnx# VBoxManage modifyvm flocker-coreos-vnx_core-01_1444996043539_3663 --pciattach '81:0.0'
root@sclf200:~/flocker-coreos-vnx#
-
Install Unofficial Flocker Tools
- You will need Unofficial Flocker Tools 0.3 or later for CoreOS support, use
pip show UnofficialFlockerToolsto check the version.
- You will need Unofficial Flocker Tools 0.3 or later for CoreOS support, use
-
Pick a node from EC2 to host the control service, label it as the master (see screenshot)
-
When you create a
cluster.yml, you will need the following details from the AWS control panel:
The cluster.yml should look like this, see screenshot for where to get much of this information from:
cluster_name: <descriptive name>
agent_nodes:
- {public: <node 1 public IP>, private: <node 1 private IP>}
- {public: <node 2 public IP>, private: <node 2 private IP>}
- {public: <node 3 public IP>, private: <node 3 private IP>}
control_node: <DNS name of the master node>
users:
- coreuser
os: coreos
private_key_path: <path on your machine to your .pem file>
agent_config:
version: 1
control-service:
hostname: <DNS name of the master node>
port: 4524
dataset:
backend: "aws"
region: <region, e.g. us-east-1>
zone: <zone that the nodes showed up in>
access_key_id: <your AWS access key>
secret_access_key: <your AWS secret key>
- Run the following script from your computer, replacing the list of nodes with the public IP addresses of the nodes:
for X in <node 1 public IP> <node 2 public IP> <node 3 public IP>; do
ssh -i <path on your machine to your .pem file> core@$X \
'sudo mkdir /root/.ssh && \
sudo cp .ssh/authorized_keys /root/.ssh/authorized_keys'
done
- This is a tool from Unofficial Flocker Tools which will deploy the Flocker containers on your nodes:
flocker-config cluster.yml
- When it's finished, try this to check that all your nodes came up:
flocker-volumes list-nodes
- Now you can start using Flocker on your CoreOS cluster!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent