Support for the deployment of Manila/CephFS with an external unmanaged Ganesha server
TripleO can deploy Manila with the CephFS backend only by colocating Ganesha and the Manila Share service; this blueprint is to track code changes necessary to be able to deploy Manila with the CephFS backend when Ganesha is remote (or not managed by TripleO)
Blueprint information
- Status:
- Complete
- Approver:
- Alex Schultz
- Priority:
- Medium
- Drafter:
- Giulio Fidente
- Direction:
- Approved
- Assignee:
- Giulio Fidente
- Definition:
- Approved
- Series goal:
- Accepted for train
- Implementation:
- Implemented
- Milestone target:
- train-2
- Started by
- Alex Schultz
- Completed by
- Alex Schultz
Related branches
Related bugs
Sprints
Whiteboard
[2019-07-30] (aschultz) Marking as implemented as all referenced patches have merged
Gerrit topic: https:/
Addressed by: https:/
Add support for external Ganesha service in Manila Share profile
Addressed by: https:/
[DNM][WIP] Allow external ganesha for the cephfs manila backend
Addressed by: https:/
Allow for configuration of Manila with a remote Ganesha service
Addressed by: https:/
Allow external Ganesha for the cephfs manila backend
Addressed by: https:/
Allow external Ganesha for the cephfs manila backend
Addressed by: https:/
Allow external Ganesha for the cephfs manila backend
Addressed by: https:/
Add support for external Ganesha service in Manila Share profile
Addressed by: https:/
Add support for external Ganesha service in Manila Share profile
Addressed by: https:/
Add support for external Ganesha service in Manila Share profile