COE Bay Drivers
At the mid-cycle meet-up, the need was discussed of making Magnum more extensible and modular. Formalising a driver structure will help organise the code, so that adding new COEs and maintaining existing ones is more effective.
A corollary function of this blueprint is to remove all COE-specific functionality (which is outside the scope of provisioning) from the core API, such as containers, RCs, services, and pods.
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- Essential
- Drafter:
- Jamie Hannaford
- Direction:
- Approved
- Assignee:
- Jamie Hannaford
- Definition:
- New
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Adrian Otto
- Completed by
- Adrian Otto
Related branches
Related bugs
Sprints
Whiteboard
https:/
Notes from the mid-cycle which discusses this: https:/
Notes from Newton Design Summit: https:/
Gerrit topic: https:/
Addressed by: https:/
Adds Bay Drivers specification
Addressed by: https:/
[WIP] Bay driver implementation
Addressed by: https:/
Swarm bay driver image
Addressed by: https:/
(WIP)Bay driver: Atomic K8s
Addressed by: https:/
Mesos-Ubuntu bay driver implementation
Addressed by: https:/
Move common bay drivers fragments in common dir
Addressed by: https:/
k8s coreos bay driver
Gerrit topic: https:/
Addressed by: https:/
Remove ReplicationCont
Addressed by: https:/
Use symlinks for common template files
Addressed by: https:/
Revert "Use symlinks for common template files" This reverts commit 748cf13182b59d7
Addressed by: https:/
Factor out common k8s definitions and mappings
Addressed by: https:/
Cluster Drivers
Gerrit topic: https:/
Addressed by: https:/
Fix magnum-
Addressed by: https:/
Move cluster delete method to driver
Gerrit topic: https:/
Addressed by: https:/
Move monitors at driver level
Addressed by: https:/
Move scale managers at driver level
Work Items
Dependency tree
* Blueprints in grey have been implemented.
