]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Mechanisms to move extensions and config into service repos
authorDoug Wiegley <dougw@a10networks.com>
Wed, 28 Jan 2015 03:17:00 +0000 (20:17 -0700)
committerDoug Wiegley <dougw@a10networks.com>
Fri, 30 Jan 2015 17:52:21 +0000 (10:52 -0700)
commit29aa644eb33cbf6bd54935fd0d0f3283872f72cc
tree91c12b49232acd1fc8a8f5f20b319bb4fb0a0ad2
parent98beceeb2073645f3fea2e6795df5b079600023e
Mechanisms to move extensions and config into service repos

- Extensions will automatically be loaded from service repos in addition
  to neutron proper, but neutron proper will take precedence.
- Config entries for service repos will be read out of neutron-{service}.conf
  first, and then neutron.conf. After Kilo, they will be read only from
  neutron-{service}.conf.
- Service providers for drivers will be collected from all neutron conf files.

This is review 1 of 3.  The second set will be in the server repos, moving
the extensions.  The third will be in neutron, removing the service exts.

Change-Id: I16b5e5b2bb70717166da14faa975fa2ab9129049
Partially-Implements: blueprint services-split
etc/neutron.conf
neutron/api/extensions.py
neutron/common/repos.py [new file with mode: 0644]
neutron/services/provider_configuration.py
neutron/tests/unit/test_provider_configuration.py