Import stable/rocky rather than stable/queens branches of upstream
and ACI-specific repositories. Changes needed for compatability
with stable/rocky that were also compatible with stable/queens were
made in previous patches, so only rocky-specific changes are included
here.
Change-Id: If533a955fb4bc23d6e4081a43df7018b1b36a0ba
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: If9ab6d55cdc50cacc69134a5268861aed9dd7074
This introduces driver for Vmware NSX Policy.
The driver assumes nsx_v3 core plugin.
It implements direct configuration of NSX Policy endpoint for security
and inherits connectivity functionality from resource mapping driver.
On startup, the driver will configure NSX Policy enforcement point to be
the NSX manager core plugin is running against.
The driver implements the following resource mapping:
Openstack project => NSX Policy domain
GBP group = > NSX Policy group + communication maps
GBP classifier => NSX Policy service
GBP rule set => NSX Policy communication profile
Change-Id: I0d5593b458f7e51c21fc2b34d1ab4d898abb6c51
This patch updates the setup for the various devstack gate jobs
to make them functional for Ocata and thus also validates
the parent patch Ocata sync patch.
Note that the NFP job still needs to be updated and has been
disabled in this patch. It can be re-enabled whenever its
updated in a followup patch.
Change-Id: I7cd5667fcc86577eb33c0233991cbb687c0ce8c9
QoS support for PTs inside PTG, as 2 new NSP param types.
The new NSP param types, qos_maxrate and qos_burstrate, map to the
Neutron QoS Policy resource, which then gets associated to a QoS
bandwith limit rule with a certain maximum rate and/or burst rate (in
Kbps) set.
Change-Id: I4a15daf5e0edd76d2d436eac6fdfb6b9f64992b2
Also updates exercise script which will catch this.
And also fixes an issue due to which the AIM gate job was
running against the master branch of GBP source versus
the branch checked out for this patchset by the infra
job. This is fixed by changing the GBP devstack plugin name
to group-based-policy instead of the earlier name 'gbp'.
This allows the job to use the 'group-based-policy' source
directory cloned by the OpenStack infra job (for the current
patchset) as opposed to cloning into a new 'gbp' directory
from the master. Unfortunately, a lot of special casing
needs to be introduced for configuration of other services
as well. It is not possible to get away from this special
casing to be able to install from the intree devstack plugin
and the GBP master branch is behind the OpenStack master
release.
Closes-bug: 1674024
Change-Id: I5bd3f1c3ecfbedbd24243c2c111472dcff9059a2
This is a very preliminary version of a new APIC mechanism driver
utilizing the ACI Integration Module (AIM) library concurrently being
developed. A corresponding extension driver exposes details regarding
the mapping of the Neutron resources to APIC. These drivers require
the Ml2Plus extended driver APIs.
See the apic-aim-ml2-driver devref for implementation details and for
devstack configuration instructions.
Change-Id: I82df32f0880d6a0d53b305f6c6391fcbea049d1b
This is a partially fix since it doesn't fully address the dev-side
documentation of all GBP related resources. More work needs to be done
on top of this to have a full DevRef.
Change-Id: I135a3d23a5a1df136c04a7114f94274bd4921cb6
Partial-Bug: #1571385
This change adds a DevStack plugin for Group-Based Policy.
A new top-level directory, devstack, has been created to fulfill
the contract of the DevStack plugin mechanism [1].
Documentation on how to enable the plugin has been added to
doc/source/installation.rst.
[1] http://docs.openstack.org/developer/devstack/plugins.html
Change-Id: I7e6c95408fbb132e33823d803a44f2867541a922
Closes-Bug: #1564893
This patch is in response to prior discussion in the
weekly IRC team meeting.
The patch does not actually add any documentation (apart
from the bits on testing and dev env setup). It does propose
topics in the index.rst for documents that need to added for
the existing components. These will be added by the team as
follow-up patches.
For any patch that adds a new feature or modifies an existing
feature it will be required to submit a devref rst document
as a part of that patch. This document should be posted in the
doc/source/devref/ location. There isn's a specific format for
the document, but it is expected that the document adequately
explains the design of the feature that is being implemented
such that its easy for the rest of the team to review, maintain,
and enhance the implementation.
Change-Id: Ifc32c330d754f623c403fb0c9a5f5c639cce41db