Fencing configuration should be automatically generated
Bug #1649695 reported by
Chris Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Chris Jones |
Bug Description
t-h-t already has a mechanism for configuring fence agents on overcloud nodes, if EnableFencing is true, and an appropriate FencingConfig is passed in.
It should really be possible for the deployment to figure out the FencingConfig for itself.
Changed in tripleo: | |
assignee: | nobody → Chris Jones (cmsj) |
Changed in tripleo: | |
milestone: | none → ocata-3 |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in tripleo: | |
status: | Triaged → In Progress |
tags: | added: puppet tripleoclient |
To post a comment you must log in.
Patch is at https:/ /review. openstack. org/417898 adding some tests at the moment.