Enable separate pillars for OVS and SRIOV agents extensions
Currently l2 agent extensions are specified in a single pillar
and then used by ovs and sriov agents.
This is not correct since there might be different extensions for
different agents on the same compute node.
With this patch ovs agent ini file will first look for 'ovs_extension'
pillar and then fallback to 'extension'. Same for sriov agent ini.
Thus, it will allow configuring different extensions for different agents,
if needed (on the same compute).
Change-Id: I15192dfc52e05c1087f667ddac8c3a537156e276
Related-Prod: PROD-19318
diff --git a/README.rst b/README.rst
index 16a261d..36581f9 100644
--- a/README.rst
+++ b/README.rst
@@ -771,7 +771,7 @@
autonomous_system: 64512 # Autonomous System number
enable_rtc: True # Enable RT Constraint (RFC4684)
backend:
- extension:
+ ovs_extension: # for OVS agent only, not supported in SRIOV agent
bagpipe_bgpvpn:
enabled: True
@@ -1199,6 +1199,25 @@
qos
enabled: True
+Different Neutron extensions for different agents
+-------------------------------------------------
+.. code-block:: yaml
+
+ neutron:
+ server:
+ backend:
+ extension: # common extensions for OVS and SRIOV agents
+ dns:
+ enabled: True
+ ...
+ qos
+ enabled: True
+ ovs_extension: # OVS specific extensions
+ bagpipe_bgpvpn:
+ enabled: True
+ sriov_extension: # SRIOV specific extensions
+ dummy:
+ enabled: True
Neutron with Designate