Deploy cinder-volume in separate availability zones on far-edge nodes via Split Controlplane
The initial implementation of the split control plane, and it's CI job [1], will run the cinder-volume service on the controller node with a single RBD backend.
This blueprint tracks the changes required so that TripleO deploys the cinder-volume service on a compute node deployed by a separate heat stack.
The cinder-volume service should be deployed in a separate availability zone and it should be possible to deploy additional cinder-volume services in their own separate availability zones. Nova would need to be configured to disable cross AZ volume access and the default volume type would need to be disabled too. TripleO may also need a new abstraction to accomplish this.
Changes made to implement this feature should have symmetrical changes made in the split control plane CI job [1]
[1] https:/
Blueprint information
- Status:
- Complete
- Approver:
- Alex Schultz
- Priority:
- Medium
- Drafter:
- John Fulton
- Direction:
- Approved
- Assignee:
- Alan Bishop
- Definition:
- Approved
- Series goal:
- Accepted for stein
- Implementation:
-
Implemented
- Milestone target:
-
stein-rc1
- Started by
- Alan Bishop
- Completed by
- Alan Bishop
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add support for cinder backend availability zones
Addressed by: https:/
Add parameters for cinder storage availability zones
Work Items
Dependency tree
* Blueprints in grey have been implemented.
