OpenStack Networking (Neutron)
d41bd58f31
Neutron-ovs-agent configures physical bridges that they works in fail_mode=secure. This means that only packets which match some OpenFlow rule in the bridge can be processed. This may cause problem on hosts with only one physical NIC where same bridge is used to provide control plane connectivity like connection to rabbitmq and data plane connectivity for VM. After e.g. host reboot bridge will still be in fail_mode=secure but there will be no any OpenFlow rule on it thus there will be no communication to rabbitmq. With current order of actions in __init__ method of OVSNeutronAgent class it first tries to establish connection to rabbitmq and later configure physical bridges with some initial OpenFlow rules. And in case described above it will fail as there is no connectivity to rabbitmq through physical bridge. So this patch changes order of actions in __init__ method that it first setup physical bridges and than configure rpc connection. Change-Id: I41c02b0164537c5b1c766feab8117cc88487bc77 Closes-Bug: #1840443 |
||
---|---|---|
api-ref | ||
bin | ||
devstack | ||
doc | ||
etc | ||
neutron | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
roles | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
.zuul.yaml | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TESTING.rst | ||
tox.ini |
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst