[EPIC] Evaluate costs of making a cluster SCS compliant

[anjastrunk]

Epic issue to evaluate costs to make existing, non-compliant OpenStack and K8S cluster SCS compliant. In doing so, we set up a non-compliant cluster with the open source life Lifecycle Management Tool for OpenStack and K8S Yaook.

This issue acts as epic.

General

• [Other] Setup test SCS cluster at Cloud&Heat with Yaook on virtual machines #414
• [Other] Setup productive SCS cluster at Cloud&Heat with Yaook on bare metal as FITKO PoC #544
• Write blogpost on costs of making a cluster SCS-compliant  website#900
• Extend implementation notes by findings from #426 #559

IaaS

• [Other] Adapt C&H test cluster to SCS Flavor Naming Standard (scs-0100) #415
• [Other] Adapt C&H test cluster to SCS Entropy (scs-0101) #416
• [Other] Adapt C&H test cluster to SCS Image Metadata Standard (scs-0102) #417
• [Other] Adapt C&H test cluster to SCS Standard Flavors and Properties (scs-0103) #418
• [Other] Adapt C&H test cluster to SCS Standard Images (scs-0104) #419
• [Other] Adapt C&H test cluster to SCS SSD Flavors (scs-0110)  #427
• [Other] Adapt C&H test cluster to Decisions for the Volume Type Standard (scs-0111) #428
• [Other] Evaluate SCS-compliance of Yaook with respect to IaaS standards beyond SCS-compatible IaaS v4  #718

KaaS

• [Other] Adapt C&H test cluster to SCS K8S Version Policy for new Kubernetes versions (scs-0210) #420
• [Other] Adapt C&H test cluster to SCS KaaS default storage class (scs-0211) #421
• [Other] Adapt C&H test cluster to Requirements for container registry (scs-0212) #422
• [Other] Adapt C&H test cluster to Kubernetes Nodes Anti Affinity (scs-0213) #423
• [Other] Adapt C&H test cluster to Kubernetes Node Distribution and Availability (scs-0214) #424
• [Other] Adapt C&H test cluster to Requirements for testing cluster-stacks (scs-0216) #425

Extra

• [Other] Yaook SCS cluster debugging #556
• [Other] Investigate why nova cell1 database in bare metal FITKO SCS cluster is overflowing #557
• Write a how-to on installation of SCS with Yaook docs#187

[cah-hbaum]

I created a document to show what is necessary to make a Yaook cluster (OpenStack) compliant with SCS. It basically combines the standards into an easy to read document (and make it a bit easier).
Some information get lost, but I also reference to the original documents, so every reader knows where to go if questions arise.

I'm not entirely sure where to post this document to keep the SCS-Team in the loop on this, but I think I will just create a branch that will never be merged. The most current version can always be found in our internal infrastructure, since the updates here will maybe be behind 1-2 days.

Edit: https://github.com/SovereignCloudStack/standards/compare/do-not-merge/scs-compliant-yaook contains the documents.

[anjastrunk]

I created a document to show what is necessary to make a Yaook cluster (OpenStack) compliant with SCS. It basically combines the standards into an easy to read document (and make it a bit easier). Some information get lost, but I also reference to the original documents, so every reader knows where to go if questions arise.

I'm not entirely sure where to post this document to keep the SCS-Team in the loop on this, but I think I will just create a branch that will never be merged. The most current version can always be found in our internal infrastructure, since the updates here will maybe be behind 1-2 days.

Edit: https://github.com/SovereignCloudStack/standards/compare/do-not-merge/scs-compliant-yaook contains the documents.

Good idea. General outcomes on how to make arbitrary OpenStack/KaaS cluster SCS compliant, should be documented in the corresponding issue, as listed in this epic. Furthermore, we should write blog articles, whenever a topic is value-added for CSPs and SCS community.

[cah-hbaum]

I started to setup an independent K8s cluster that will be used to test the K8s standards. The cluster is already up and running, next step is to apply the standards.

[cah-hbaum]

I finally created the k8s cluster from yaook/k8s. This took a bit longer, since the latest release (5.1) generated some problems on my end (I will explain this further in the "Debugging Issue").

Nonetheless, I could create a cluster and will check this now for conformance with the SCS standards, especially SCS Compatible KaaS v2.

Further information can be found in the issues regarding this.