tripleoclient generates ceph keys only when a ceph node is deployed
Bug #1603010 reported by
Marius Cornea
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Currently tripleoclient generates Ceph parameters only when a ceph node gets deployed. With the enablement of hyperconverged ceph nodes[1] we can colocate the ceph OSDs on compute nodes therefore not needing dedicated ceph nodes. The tripleoclient should cover this case and generate the parameters required by Ceph even when there's no ceph node deployed.
| tags: | added: tripleoclient |
Revision history for this message
| Dougal Matthews (d0ugal) wrote | #1 |
| Changed in tripleo: | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
To post a comment you must log in.
In Newton these parameters are generated in tripleo-common and this is done for all plans and deployments.