backend.engine contrail, use-case juniper packaging

[epcim]

backend.engine must recognize under value contrail also a vendor (juniper vs. opencontrail).

For deployments where Juniper contrail is deployed, service_plugins = neutron_plugin_contrail.plugins.opencontrail.loadbalancer is a wrong value.

One example: neutron/files/liberty/neutron-server.conf.Debian

{%- if server.backend.engine == "contrail" %}
service_plugins = neutron_plugin_contrail.plugins.opencontrail.loadbalancer.plugin.LoadBalancerPlugin
{%- elif server.backend.engine == "midonet" %}
service_plugins = lbaas,midonet.neutron.services.l3.l3_midonet.MidonetL3ServicePlugin,midonet.neutron.services.firewall.plugin.MidonetFirewallPlugin
{%- endif %}

[pupapaik]

What is correct value? This should be same.

[epcim]

@pupapaik commented on Feb 26, 2017, 10:07 PM GMT+1:

What is correct value? This should be same.

so please clarify, juniper contrail is using: neutron_plugin_contrail.plugins.opencontrail.loadbalancer.plugin.LoadBalancerPlugin ?

in addition:
map.jina spec. for pkg of neutron-lbaas-agent should be optional, as we have found it's deps. are not properly shipped within a juniper contrail repo.

Anyway I would rather have instalation of neutron-lbaas-agent optional in neutron formula, as we consider juniper to have broken dependencies, missing dependency, in the repository.