SCS-Compliant Yaook¶
What: Improve SCS operator and use k-orc (kubernetes-Openstack-resource-controller) Organizer: Stefan Hoffman, Max Harmathy
SCS Operator¶
Focis Work Items:
General considerations:
- The SCS operator will handle life-cycle relevant resources in OpenStack and therefore has potentially a different target audience (e.g. different operations team).
- The distinction on a technical level is somewhat blurred, since there are OpenStack services which also require such resources for basic functionality (e.g. Octavia requires a compute flavor and at least one Amphora image to become ready)
Action plan:
- Evaluate whether the operator can be provided as a separate entity from the Yaook operator.
- Provide a documented way of deployment (preferably together with K-Orc and resources).
SCS Flavors¶
- Initial attempt for K-Orc resources: SCS Flavors as ORC resources
- Extra specs feature implemented in K-Orc but has not landed in a release, yet.
Action plan:
- Extend the existing resources with extra specs.
- Provide the resources as part of a Yaook or SCS repository
SCS Images¶
The images still need investigation how to handle they're life-cycle (phase out old images and replace with new ones).