Fix Neutron data_plane_status extension path

This way is easier to patch than patching file
neutron.egg-info/entry_points.txt, plus this feature is backported
to Ocata so it's temporary and only applicable for Euphrates.

From Pike we can move it back to 'data_plane_status' as it was before.

Change-Id: I1c2ebc55e782463793e7a8e463cc17fdf899457a
Signed-off-by: Carlos Goncalves <mail@cgoncalves.pt>
(cherry picked from commit 3ad85e5753dd4b0bf621f5d92f45725d18070e54)

diff --git a/build/opnfv-environment.yaml b/build/opnfv-environment.yaml
index 7da252e..535fb94 100644 (file)
--- a/build/opnfv-environment.yaml
+++ b/build/opnfv-environment.yaml
@@ -12,7 +12,8 @@ parameter_defaults:
   NeutronEnableDHCPMetadata: true
   NeutronEnableIsolatedMetadata: true
   # NeutronDhcpAgentsPerNetwork: 3
-  NeutronPluginExtensions: 'qos,port_security,data_plane_status'
+  NeutronPluginExtensions: 'qos,port_security,neutron.plugins.ml2.extensions.\
+                            data_plane_status:DataPlaneStatusExtensionDriver'
   # TODO: VLAN Ranges should be configurable from network settings
   NeutronNetworkVLANRanges: 'datacentre:500:525'
   # NeutronVPPAgentPhysnets: