container ovs-agent, ensure br-ex exists
authorSteve Baker <sbaker@redhat.com>
Mon, 14 Aug 2017 22:26:24 +0000 (10:26 +1200)
committerEmilien Macchi <emilien@redhat.com>
Wed, 30 Aug 2017 12:51:12 +0000 (12:51 +0000)
commit0f2af352d15cb9c486414619a8342e727a2e207c
treebd3a323a9435c9df06d78b258fc2438333b7185d
parentd772eb77273402a54503906ff40d2d8aa0dc5630
container ovs-agent, ensure br-ex exists

Currently the container neutron-ovs-agent is stuck in a restart loop
in many environments because the bridge br-ex is missing.

This bridge is created by running the puppet class
neutron::agents::ml2::ovs but limiting that run to tag
neutron::plugins::ovs::bridge.

The hiera neutron::agents::ml2::ovs::bridge_mappings should already
exists to create the bridge with the required settings.

This change should ensure br-ex exists after step 3.

Since br-ex is created regardless of the chosen network config,
environments/docker-network.yaml is not longer required. It can be
deleted once there are no more references to it in CI and
documentation.

Change-Id: Ie425148b0ad0f38e149c5fa0a97d98ec35d0a5bb
Closes-Bug: #1699261
Closes-Bug: #1691403
Closes-Bug: #1689556
(cherry picked from commit 76f130d6e8f7434433b2602af9794f1e9c742e1f)
docker/services/neutron-ovs-agent.yaml
environments/docker-network.yaml