6423c820c4
1. Introduced a new subnet extension attribute for this. When its enabled, this subnet can't be connected to a router. And to make things simple, this new attribute's value can't be changed after creation. 2. VM port's active_active_aap mode in the EP file is dtermined by checking this port's fixded_ip subnets one by one, and only if the active_active_aap value is true for all the subnets then we will mark it accordingly in this VM port's EP file. And when active_active_aap is on, the owned address concept doesn't apply to those AAPs. 3. An AAP can't be added to a port if this port's active_active_aap mode is different than any of the other ports (in the same VRF) whose AAPs is overlapping with this AAP. 4. Also added a helper function to create a subnet with those extension attributes in the UT environment. Change-Id: Icb3af7b33442eda739f93f9e6ca16174a26f5c21 (cherry picked from commit |
||
|---|---|---|
| devstack | ||
| doc/source | ||
| etc | ||
| gbpservice | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| TESTING.rst | ||
| babel.cfg | ||
| openstack-common.conf | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Group Based Policy (GBP) provides declarative abstractions for achieving scalable intent-based infrastructure automation.
GBP complements the OpenStack networking model with the notion of policies that can be applied between groups of network endpoints. As users look beyond basic connectivity, richer network services with diverse implementations and network properties are naturally expressed as policies. Examples include service chaining, QoS, path properties, access control, etc.
GBP allows application administrators to express their networking requirements using a Group and a Policy Rules-Set abstraction. The specifics of policy rendering are left to the underlying pluggable policy driver.
GBP model also supports a redirect operation that makes it easy to abstract and consume complex network service chains and graphs.
Checkout the GBP wiki page for more detailed information: <http://wiki.openstack.org/GroupBasedPolicy>
The latest code is available at: <http://git.openstack.org/cgit/openstack/group-based-policy>.
GBP project management (blueprints, bugs) is done via Launchpad: <http://launchpad.net/group-based-policy>
For help using or hacking on GBP, you can send mail to <mailto:openstack-dev@lists.openstack.org>.
Acronyms used in code for brevity:
- PT: Policy Target
- PTG: Policy Target Group
- PR: Policy Rule
- PRS: Policy Rule Set
- L2P: L2 Policy
- L3P: L3 Policy
- NSP: Network Service Policy
- EP: External Policy
- ES: External Segment