Write a how-to on installation of SCS with Yaook

[anjastrunk]

Cloud&Heat already build two SCS cluster with Yaook. The first one a test cluster based on virtual machines, which run in an Openstack environment. The second one is a productive cluster based on bare-metal machines, which has the certificate IaaS-compatible v3.

Together with SpaceNet we want to create a third SCS cluster. This cluster is based in virtual machines, managed by Proxmox.

We already got a lot of experience in installing SCS cluster with yaook. Using proxmox is an additional challenge and we will document all our lessons-learned with respect to Yaook and SCS, with the aim to provide a step-by-step how-to tutorial on to install SCS cluster with Yaook. We will publish this as blog post an SCS website for the SCS community.

[cah-hbaum]

Just wanted to ask here again in what context this should be done, especially in what repository of the SCS (or maybe externally?).

[anjastrunk]

Just wanted to ask here again in what context this should be done, especially in what repository of the SCS (or maybe externally?).

IMO, this should be in SCS' docs repo or published as blog post similar to SovereignCloudStack/website#917. @mbuechse: Any objections

[cah-hbaum]

I've decided that I will write another blog post on the website. That one can also be mirrored into the docs repository later on, but for now, I think thats the better place.

[cah-hbaum]

Had a meeting with @anjastrunk yesterday, heres a short excerpt of the the topics discussed:

• text will contain different sections for yaook/k8s and yaook/operator
• showcase differentiation between instalaltion on Openstack and proxmox (used by customer)
• updating layers to be conformant

[anjastrunk]

We had a meeting with a CPS to discuss setup of SCS cluster and to collect feedback OSISM installer.

CPS wants to setup a virtual SCS cluster on top of Proxmox. Beside a virtual SCS cluster on Openstack and a bare metal cluster, this is an additional setup to be installed with Yaook. We will document our experiences with Proxmox here and will summarize our lessons learned of all three setups in a guide on how to install a complete SCS cluster with openstack.

[berendt]

We had a meeting with a CPS to discuss setup of SCS cluster and to collect feedback OSISM installer.

Where can I find the feedback? I don't know anything about this setup of OSISM on a Proxmox right now. Which CSP are you referring to?

[anjastrunk]

We had a meeting with a CPS to discuss setup of SCS cluster and to collect feedback OSISM installer.

Where can I find the feedback? I don't know anything about this setup of OSISM on a Proxmox right now. Which CSP are you referring to?

SpaceNet (our partner) planed to install SCS stack with OSISM on bare-metal, originally. However, this did not work as expected. The feedback with respect to OSISM installer v6.x is as follows:

• Rare documentation: information were missing or outdated. Configration files were described incomplete. It is nit clear which configuration settings exist and what they effect. You have to figure this out by yourself using try and error
• Ansible Reset / Re-configuration: It was not possible to re-configure/reset service using apply. Instead of resetting all configuration, data entries of services were created twice.
• No de-install script : If you want to start installation from scratch, you have to re-install bare-metal machine. Which takes some time. Hence, if you did a mistake in installation/configuration and you want to start from scratch, you have to re-install bare-metal machine at whole.

Please feel free to contact SpaseNet for more details, directly. I can provide you the contact as PN.

[berendt]

We had a meeting with a CPS to discuss setup of SCS cluster and to collect feedback OSISM installer.

Where can I find the feedback? I don't know anything about this setup of OSISM on a Proxmox right now. Which CSP are you referring to?

SpaceNet (our partner) planed to install SCS stack with OSISM on bare-metal, originally. However, this did not work as expected. The feedback with respect to OSISM installer v6.x is as follows:

• Rare documentation: information were missing or outdated. Configration files were described incomplete. It is nit clear which configuration settings exist and what they effect. You have to figure this out by yourself using try and error
• Ansible Reset / Re-configuration: It was not possible to re-configure/reset service using apply. Instead of resetting all configuration, data entries of services were created twice.
• No de-install script : If you want to start installation from scratch, you have to re-install bare-metal machine. Which takes some time. Hence, if you did a mistake in installation/configuration and you want to start from scratch, you have to re-install bare-metal machine at whole.

Please feel free to contact SpaseNet for more details, directly. I can provide you the contact as PN.

Please give me the contact details. It's a pity as they haven't contacted us about this and haven't opened any issues on our site. These are all simple questions that could have been answered if one had asked. If they don't ask, it is of course difficult to help and to improve things.

There are reconfigure plays to reconfigure services (osism apply -a reconfigure XXX). There are purge plays to purge OpenStack, Ceph & Kubernetes (e.g. osism apply kolla-purge for OpenStack & osism apply purge-cluster for Ceph), you don't have to start from scratch. There are deploy guides and so on. Documentation can always be better of course. But it's simply difficult without feedback.