Storage Availability Zone per backend
Availability Zones (AZs) are failure domains. This could be a rack of hardware with the same power supply or a cordoned off area of one's data center that can fail individually.
Manila's service architecture and featureset (Share Provisioning, Replication) relies on the concept of AZs. Manila supports multi-backend architecture since Juno, but we still required that all enabled backends in a manila configuration file are in a single storage availability zone. This lends itself poorly to designs where one would want to run the manila share service in a completely different place than backends, for example: one could imagine a centralized control plane running all the manila processes but the storage backend itself located in a separate site (Ex: Edge Deployments)
Manila should support this architecture and allow "storage_
Blueprint information
- Status:
- Complete
- Approver:
- Tom Barron
- Priority:
- Undefined
- Drafter:
- Goutham Pacha Ravi
- Direction:
- Approved
- Assignee:
- Goutham Pacha Ravi
- Definition:
- Approved
- Series goal:
- Accepted for stein
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Goutham Pacha Ravi
- Completed by
- Goutham Pacha Ravi
Related branches
Related bugs
Sprints
Whiteboard
Specification:
Gerrit topic: https:/
Addressed by: https:/
Storage Availability Zone improvements
Implementation:
Gerrit topic: https:/
Addressed by: https:/
Allow configuration of a back end specific availability zone
Gerrit topic: https:/
Addressed by: https:/
Configure per backend availability zones in devstack