summaryrefslogtreecommitdiffstats
path: root/environments/neutron-bgpvpn.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-04-07Add BGPVPN services to scenario004Carlos Camacho1-1/+1
This submission will enable the BGPVPN API on scenario004. This addition to scenario004 does not provide any sanity check for the Neutron API extension. At this stage is meant to install the required packages and prerequisites, configure the extension and having the services started correctly. In the README.rst file, this is displayed as neutron-bgpvpn, so for further integrations should be added as neutron-<extension_name> for an easier reading. Depends-On: I4d0617b0d7801426ea6827e70f5f31f10bbcc038 Depends-On: I2be0fab671ec1a804d029afc6dc27d19a193b064 Change-Id: I6c257417a9231c44e13535bc408d67d2a3cacbf8
2017-04-05Fixing acronym for BGPVPN composable serviceRicardo Noriega1-1/+1
Change-Id: I397a6ad430cef5ddb4eee48347ad4c89144ad01e Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
2017-03-10Add BGPVPN composable serviceRicardo Noriega1-0/+16
This project aims at supporting inter-connection between L3VPNs and Neutron resources, i.e. Networks, Routers and Ports. Partially-Implements: blueprint bgpvpn-service-integration Depends-On:I7c1686693a29cc1985f009bd7a3c268c0e211876 Change-Id: I576c9ac2b443dbb6886824b3da457dcc4f87b442 Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>