Multiple External Ceph Support
This blueprint proposes that TripleO get the ability to configure a single overcloud to use an arbitrary number of external ceph clusters.
TripleO can currently configure the overcloud to use only one external ceph cluster via the environments/
If TripleO could support multiple Ceph clusters, then a new paramter like the following would be added:
CephMultiBacken
ceph1:
CephClust
CephClien
CephExter
ceph2:
CephClust
CephClien
CephExter
CinderRbd
...
cephN:
This would then result in TripleO running ceph-ansible for the ceph-client role N times with the same parameters for each run except different parameters would be passed per run if it's included in the cluster name's hash. E.g. the FSID would be different for the cluster named ceph1. These runs would result in N keyring files getting created in the appropriate directory, N Ceph conf files like /etc/ceph/
[1] https:/
[2] https:/
Blueprint information
- Status:
- Complete
- Approver:
- wes hayutin
- Priority:
- Undefined
- Drafter:
- John Fulton
- Direction:
- Approved
- Assignee:
- John Fulton
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- John Fulton
- Completed by
- John Fulton
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP/DNM: Introduce CephExtraKeys
Addressed by: https:/
Introduce CephExtraKeys
Gerrit topic: https:/
Addressed by: https:/
WIP/DNM: Introduce CephMultiBacken
Addressed by: https:/
WIP/DNM: Add support for ceph_multi_
Gerrit topic: https:/
Addressed by: https:/
Document CephExternalMul
Addressed by: https:/
Add support for ceph_external_
Addressed by: https:/
Introduce CephExternalMul