IBM Spectrum Conductor for Containers is an on premises platform for managing containerized applications that is based on the container orchestrator Kubernetes. Through the implementation of a robust resource manager, Apache Mesos, IBM Spectrum Conductor for Containers is able to manage resources for hybrid environments that contain both containerized and non-containerized applications as well as mixed hardware architecture. IBM Spectrum Conductor for Containers also includes a graphical user interface which provides a centralized location from where you can deploy, manage, monitor and scale your applications.
To intall CfC:
-
Load a Power 8 or OpenPower system with Ubuntu 16.10
Remove apparmor
systemctl stop apparmor.service update-rc.d -f apparmor remove apt-get remove apparmor apt-get purge apparmor
Install SSH
apt-get install -y openssh-server
Setup 'root' password Enable ssh login for 'root'
ssh-keygen vi /etc/ssh/sshd_config # PermitRootLogin prohibit-password PermitRootLogin yes # PermitEmptyPasswords no #PasswordAuthentication yes service ssh restart
Make sure that you have passwordless connection to 'localhost'. The 'ssh root@localhost' should return without asking for password. If not:
ssh-copy-id root@localhost
Make sure that SMT is turn off
ppc64_cpu --smt=off
-
Install pre-requisites
sed -i 's/^# deb-src/deb-src/g' /etc/apt/sources.list apt-get update apt-get install -y vagrant ruby-libvirt apt-get install -y qemu-kvm libvirt-bin ebtables dnsmasq apt-get install -y libvirt-daemon-system apt-get install -y libxslt-dev libxml2-dev libvirt-dev zlib1g-dev ruby-dev git git-review apt-get install -y software-properties-common apt-add-repository -y ppa:ansible/ansible apt-get install -y ansible
Make sure that libvirt can be run by the 'root' user
vi /etc/libvirt/qemu.conf user = "root" group = "root" service libvirtd restart
If you want to change the network setup
vi /etc/libvirt/qemu/networks/default.xml
Check that the KVM kernel modules are loaded
lsmod | fgrep kvm modprobe kvm_[hv, pr] # kvm_pr is used for nested KVM
Check the network
virsh net-list --all virsh net-start default virsh net-autostart default
-
Install Vagrant
apt-get install -y vagrant apt-get install -y build-essential libssl-dev libffi-dev python-dev
-
Install Vagrant plugins
vagrant plugin install vagrant-mutate vagrant plugin install vagrant-libvirt vagrant plugin install vagrant-host-shell vagrant plugin install vagrant-env vagrant plugin install vagrant-git vagrant plugin install vagrant-openstack-provider vagrant plugin install vagrant-proxyconf
Note: on Ubuntu 16.04 patch the 'vagrant/budler.rb' file using the instructions at: http://stackoverflow.com/questions/36811863/cant-install-vagrant-plugins-in-ubuntu-16-04/36991648#36991648
-
Clone the CfC repository
cd /root git clone https://github.com/fbarilla/CfC.git
-
Deploy CfC
cd CfC vagrant up
Note: the CfC dashboard URL and credentials are provided as the last message of the installation process.
TASK [deploy-cfc : Congratulations! Conductor for Container (CfC) has been successfully installed.] ***
ok: [cfc1] => {
"msg": "To access CfC point a browser to https://192.168.122.xxx . Use 'admin/admin' as credentials"
}
Note: by default, the installation process is started from '/root/CfC'. If the github project has been cloned in a different directory, update the 'install_dir' variable in './cfc/cfc-deploy/group_vars/all.yml'.
Note: by default the VM network interface name is 'eth1'. If your VM has a different interface naming convention, update the name in 'root/CfC/config.rb' and './cfc/cfc-deploy/group_vars/all.yml'
Note: additional info is available at: https://hub.docker.com/r/ibmcom/cfc-installer-ppc64le/?cm_mc_uid=78549162759914854428789&cm_mc_sid_50200000=1486050575