[Other] Adapt C&H test cluster to SCS Flavor Naming Standard (scs-0100)

[anjastrunk]

Adapt C&H test cluster to SCS Flavor Naming Standard (scs-0100) and evaluate its costs.

Todos:

• Adapt C&H test cluster to SCS standard
• Update standard documentation with costs/cost estimation
• Write how to and/or adaption script

[cah-hbaum]

Cost estimation for this standard can be found here.

The how to and script can be found in here and here.

[anjastrunk]

Cost estimation for this standard can be found here.

The how to and script can be found in here and here.

Thanks for collecting cost of making a cloud SCS compliant. We should decide, where to place this information. Implementation and Testing Notes of each standard could be a good candidate. Goal is, that providers, who want to become SCS compliant can access our lessons learned, easily.

[anjastrunk]

Furthermore, if we moved cost of making a cloud SCS compliant to its final place and our clusters (productive and test cluster) are SCS compliant, we should close this issue.

[cah-hbaum]

Test script output indicating that the test cluster complies to the SCS-0100-v3-flavors standard:

    ./iaas/flavor-naming/flavor-names-openstack.py -c scs-test --mand=./iaas/scs-0100-v3-flavors.yaml:
      rc: 0
      stdout:
      - 'scs-test:'
      - '  OtherFlavorSummary:'
      - '    TotalAmount: 0'
      - '  SCSFlavorSummary:'
      - '    FlavorsWithWarnings: 0'
      - '    MandatoryFlavorsMissing: 0'
      - '    MandatoryFlavorsPresent: 0'
      - '    OptionalFlavorsValid: 28'
      - '    OptionalFlavorsWrong: 0'
      - '    TotalAmount: 28'
      - '  TotalSummary:'
      - '    Errors: 0'
      - '    Warnings: 0'
      - ''
      stderr: []
      info: 0
      warning: 0
      error: 0
      critical: 0
      result: 1

[cah-hbaum]

Test cluster is up and compliant, so the issue will be closed.