Caasp

CaaSP4

If you are running the make targets locally, be sure to have met the Local requirements.

Getting a CaaSP4 on Openstack configured for CAP

$> BACKEND=caasp4os make k8s

This target gives you a CaaSP4 cluster, using k8s CPI, on Openstack. It also configures the cluster for CAP.

For the skuba client, it creates a docker skuba punctured image with the CaaSP4 product: certain paths are mounted as volumes so the container can access the host, the host env is passed for ssh-agent, and /etc/passwd is passed so the container can seamlessly create files in the host.

⚠️ this means that you need a setup that allows for starting the container with those mounts. For example, OSX docker installation does not easily allow this ⚠️

With it, it spawns the Openstack infrastructure by Terraform, bootstraps the cluster with skuba (the CaaSP4 cli), and configures and prepares the cluster for cap by adding correct RBACs, storageclasses, etc. It will build the skuba docker image if not present.

Needs an Openstack's openrc.sh sourced for the terraform-openstack provider. Adds an ssh key to ssh-agent if not present, and injects it into the machines.

Destroying the deployment of CaaSP4 on Openstack

Since the infrastructure is living on Openstack, instead of deleting the corresponding build folder, please run:

$> BACKEND=caasp4os make clean

which first destroys the k8s storageclass (note that Openstack CPI integration doesn't clean the cinder volumes automatically) and then destroys the infrastructure on Openstack with Terraform.

Deploying CaaSP4 and CAP on top

Same procedure, but call:

$> BACKEND=caasp4os make all