aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud-without-mergepy.yaml
diff options
context:
space:
mode:
authormarios <marios@redhat.com>2015-09-30 13:47:58 +0300
committermarios <marios@redhat.com>2015-10-06 09:03:52 +0300
commit3dd47a7c2a4ef9f565249053c49d65561ad95741 (patch)
tree120b655a80672ac39c2a7c3c4776c142a5b8438c /overcloud-without-mergepy.yaml
parent9e918a4a517f62d4417909311041e3e54a726462 (diff)
Rework pacemaker constraints from ovs and netns cleanup agents
In the current neutron-* services constraints chain, the ovs and netns cleanup services are re-run after a neutron-server restart. As discussed at [1] this may not be desirable leaving some neutron services down and any tenant routers without IP. This review introduces a second constraints chain so we now have: neutron-server-->openvswitch-->dhcp-->l3-->metadata and ovs-cleanup-->netns-cleanup-->openvswitch Instead of a single chain like neutron-server-->ovs-cleanup-->netns-cleanup-->openvswitch--> dhcp-->l3-->metadata [1] https://bugzilla.redhat.com/show_bug.cgi?id=1266910#c12 Related-Bug: 1501378 Change-Id: I4096704257aff74ff5bd37d8d01d8a776c6c6a76
Diffstat (limited to 'overcloud-without-mergepy.yaml')
0 files changed, 0 insertions, 0 deletions