bgpvpn can't co-exist with *aas service providers

[Thomas Morin]

Details in https://bugs.launchpad.net/neutron/+bug/1473110

[Thomas Morin (tmmorin-orange)]

https://review.openstack.org/#/c/208527/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/208527
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=5be327bef115e296fb7ed5611b2920193c06bd90
Submitter: Jenkins
Branch: master

commit 5be327bef115e296fb7ed5611b2920193c06bd90
Author: Thomas Morin <email address hidden>
Date: Mon Aug 3 17:08:27 2015 +0200

    Read networking_bgpvpn.conf for service providers

    With this patch, Neutron will read (/etc/neutron/)networking_bgpvpn.conf
    for service_provider definitions, thus allowing the use of
    the BGPVPN service plugin additionally to other service relying
    on their own neutron_*aas.conf file.

    This patch also fixes README and devstack behavior so that
    a default networking-bgpvpn.conf file is deployed.

    This depends on change Ia4cad678e6c722ca05821dbdbf05d61523246a86

    Change-Id: Ifebe4c965448431737d9f0e4c25605b718850460
    Closes-bug: 1473119