https://blueprints.launchpad.net/fuel/+spec/ccp
This is a meta specification to describe in details creation of the new experimental project under the Fuel project umbrella to provide to users Containerized OpenStack deployment on top of Kubernetes, codename “Fuel CCP”.
Containerized Control Plane (CCP) is the initiative to package OpenStack services in the containers and use standard container management framework to run and manage them. It includes following areas, but not limited to them:
Fuel CCP governance will be a separate experimental project under the openstack git namespace with unique specs and core team. There is no intention right now to apply for the Big Tent. The nearest example of the same governance is 3rd party Fuel plugin done not by Mirantis that aren’t under Big Tent and not controlled by the main Fuel core team.
Separate Launchpad project will be used for the blueprints and bugs management. Fuel’s main IRC channels will be initially used for communication (#fuel) and there will be weekly sub-team meetings as part of the main Fuel weekly IRC meetings.
CCP is to be a set of repositories with Docker image definitions together with Kubernetes applications definitions. It is a single git repository per OpenStack component plus few repositories with related software, tooling, such as 3rd party CI config, installer and etc. We’re going to start with the minimal set of the repositories for the “core” OpenStack implementation plus logging and monitoring implementation based on the existing Stacklight [0] [1] expertise. The CI system will use upstream infra CI as much as possible and 3rd party CI for running end-to-end deployment tests.
The initial list of repositories for CCP initiative:
Each repository will have it’s own core reviewers team and there will be one general core reviewers team with permissions in all repositories.
None. There will be no changes to the existing Fuel projects now.
None. There is no intention to integrate with Web UI on the early stages of the initiative.
None. There is no intention to integrate with Nailgun on the early stages of the initiative.
None
None
None
None
None
This spec is actually describes an alternative experimental approach for OpenStack deployment, but there are few questions to answer about alternatives.
It’ll be separate activity to define migration path from current to the Kubernetes / CCP based OpenStack version.
None
None
None
None
None
None
Separate 3rd party CI will be used to run end-to-end tests.
Separate documentation will be needed for CCP initiative.
Mandatory design review: * Vladimir Kozhukalov <vkozhukalov@mirantis.com> * Sergii Golovatiuk <sgolovatiuk@mirnatis.com> * Bulat Gaifullin <bgaifullin@mirantis.com> * Julia Aranovich <jkirnosova@mirantis.com>
None
It is not planned to use current Fuel QA resources. All tests will be run on a separate CI (partly upstream, partly 3-rd party) and test code is to be written by CCP sub-team.