72d5dfbf48
The plugin implementations need to be isolated from the entity that is using os-vif. Plugins should be allowed to define their own custom config parameters, without needing the user of os-vif to pass further options into the os_vif.initialize() method. This change introduces a CONFIG_OPTS attribute on the Plugin class. This provides a list of oslo_config options that are to be used by the plugin. os_vif will register these options into a group 'os_vif_$PLUGIN' eg 'os_vif_linux_bridge'. This gives the plugin impls the ability to have config options in the main project conf (ie /etc/nova/nova.conf) without exposing them directly to all of nova's own config options. Change-Id: I9634b474cd0d3fda09aef5800020c9415c28e3d8
13 lines
411 B
Plaintext
13 lines
411 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr>=1.6
|
|
netaddr>=0.7.12,!=0.7.16
|
|
oslo.config>=3.4.0 # Apache-2.0
|
|
oslo.log>=1.14.0 # Apache-2.0
|
|
oslo.i18n>=1.5.0 # Apache-2.0
|
|
oslo.versionedobjects>=0.13.0
|
|
six>=1.9.0
|
|
stevedore>=1.5.0 # Apache-2.0
|