Deploy glance-cache on far-edge nodes via Split Controlplane
The initial implementation of the split control plane will run the glance-api service only on the controller node with the swift backend and then remote compute nodes will GET the glance images for their instances.
This blueprint tracks the changes required for TripleO to deploy glance-cache [0] on the remote compute node.
Changes made to implement this feature should have symmetrical changes made in the split contorl plane CI job [1] to prove that the change worked.
[0] https:/
[1] https:/
Blueprint information
- Status:
- Started
- Approver:
- wes hayutin
- Priority:
- Undefined
- Drafter:
- John Fulton
- Direction:
- Approved
- Assignee:
- Pranali Deore
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Alan Bishop
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Enable Glance Image Cache in OOO
Addressed by: https:/
Enable glance image cache's cleaner and pruner
Gerrit topic: https:/
Addressed by: https:/
Add more settings for glance image cache
Gerrit topic: https:/
Addressed by: https:/
Add more settings for glance image cache
Addressed by: https:/
Add more settings for glance image cache
Addressed by: https:/
Add container images for DCN/Edge deployments
Addressed by: https:/
Add ability to deploy glance at DCN/Edge sites
Addressed by: https:/
Add container images for DCN/Edge deployments
Addressed by: https:/
Add ability to deploy glance at DCN/Edge sites
Work Items
Dependency tree
* Blueprints in grey have been implemented.
