SovereignCloudStack / SovereignCloudStack/cluster-stacks

Add image metadata to the OpenStack node-images.yaml as is defined in the related SCS standard

Open
#23 4 comments 0 reactions 1 assignee View on GitHub

@michal-gubricky is already working on this.

Since Apr 16, 2024.

Container
Dominant language
Python
Stars
13
Forks
8
PR merge metrics
No merged PRs in 30d

Description

/kind feature

SCS standard scs-0102-v1-image-metadata describes what metadata (properties and tags) should be assigned to the image that is offered by the CSP.

These properties and tags are then evaluated by the Conformance Tests (script image-md-check.py).

CSPO supports a full list of create options, defined by the OpenStack API. Hence the node-images.yaml should include all mandatory properties and tags for each image.

Current state of node-images.yaml (openstack cluster stack)
apiVersion: openstack.infrastructure.clusterstack.x-k8s.io/v1alpha1
openStackNodeImages:
  - url: https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2204-kube-v1.28/ubuntu-2204-kube-v1.28.6.qcow2
    createOpts:
      name: ubuntu-capi-image-v1.28.6
      disk_format: qcow2
      container_format: bare
      visibility: shared
Desired state of node-images.yaml (openstack cluster stack)
apiVersion: openstack.infrastructure.clusterstack.x-k8s.io/v1alpha1
openStackNodeImages:
  - url: https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2204-kube-v1.28/ubuntu-2204-kube-v1.28.6.qcow2
    createOpts:
      name: ubuntu-capi-image-v1.28.6
      disk_format: qcow2
      container_format: bare
      visibility: shared
      properties:
      - architecture: x86_64 
      - ....
      tags:
      - managed_by_scs

Note: see KaaS V1 implementation

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.