A light Ansible framework for TripleO integration with Ceph clusters deployed with cephadm and managed with Ceph orchestrator.
Starting in the Octopus release, Ceph has its own day1 tool called
cephadm and it's own day2 tool called orchestrator which
will replace ceph-ansible. What should TripleO's Ceph integration
do about this? We currently provide the following user experience:
Describe an OpenStack deployment, which includes Ceph, and TripleO
will "make it so"
The above has been true for TripleO since Kilo and should
continue. TripleO should also continue hyper-converged support
(collocation of OpenStack and Ceph containers). There is sufficient
value in both of these (one tool and hyper-convergence) to justify
this project. At the same time we want to deploy Ceph in a way
consistent with the way the Ceph project is moving and decouple the
complexity of day2 management of Ceph from TripleO.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- High
- Drafter:
- John Fulton
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for wallaby
- Implementation:
-
Good progress
- Milestone target:
-
wallaby-3
- Started by
- Giulio Fidente
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work Items
Dependency tree
* Blueprints in grey have been implemented.
