x
/
group-based-policy
Code Issues Proposed changes
Group Based Policy
1,253 Commits 18 Branches 6 Tags 58 MiB
Python 99.2%
Shell 0.8%
Go to file
Robert Kukura add2c14abd [AIM] Fix legacy SNAT migration 
Avoid issues caused by missing NetworkMapping DB records when cleaning
up the legacy plugin's SNAT-related resources. The test_legacy_cleanup
UT is enhanced to create a router and an interfaced internal network
and to delete all mapping and extension records, so that code
manipulating legacy SNAT resources with missing mapping records is
exercised.

Missing NetworkMapping and AddressScopeMapping records are silently
ignored in delete_*_precommit methods. They are logged and ignored in
extend_*_dict methods.

When an AddressScopeMapping or a NetworkMapping record is added, the
corresponding AddressScope or Network instance's aim_mapping
relationship field is updated to reference it. This avoids aim_mapping
being None when the AddressScope or Network instance is subsequently
retrieved from the session cache within the same transaction.

Change-Id: I84f3c401df7c79deb9151b0b232262139fca9429
 		2018-12-02 12:08:20 -05:00
devstack For queens sync 2018-09-07 16:24:08 -07:00
doc/source Replace Chinese quotes to English quotes 2018-02-12 10:41:23 +08:00
etc Remove monolithic service chain plugin and drivers 2017-06-13 13:35:03 -07:00
gbpservice [AIM] Fix legacy SNAT migration 2018-12-02 12:08:20 -05:00
tools For queens sync 2018-09-07 16:24:08 -07:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:59:28 +00:00
.gitignore Status attributes for GBP resources 2016-06-22 01:29:46 -07:00
.gitreview Changing stackforge references 2015-10-17 13:43:25 -07:00
.stestr.conf For queens sync 2018-09-07 16:24:08 -07:00
.testr.conf Raise OS_TEST_TIMEOUT 2017-09-13 20:58:48 +00:00
CONTRIBUTING.rst Update the outdated links 2018-03-20 06:09:16 +00:00
HACKING.rst Update links to the latest addresses 2017-08-18 21:38:05 +08:00
LICENSE Project boilerplate and base modules 2014-09-26 15:16:17 -07:00
MANIFEST.in Project boilerplate and base modules 2014-09-26 15:16:17 -07:00
README.rst Add some acronyms for brevity in README 2017-10-13 17:24:42 +08:00
TESTING.rst Adding dir structure for developer reference docs 2016-02-19 14:46:27 -08:00
babel.cfg Project boilerplate and base modules 2014-09-26 15:16:17 -07:00
openstack-common.conf Renaming gbp package to gbpservice 2014-12-31 19:13:19 -08:00
requirements.txt For queens sync 2018-09-07 16:24:08 -07:00
run_tests.sh For queens sync 2018-09-07 16:24:08 -07:00
setup.cfg [AIM] Validation/Repair/Migration Tool 2018-05-21 15:30:01 -04:00
setup.py Syncing with mitaka dependencies 2016-02-25 18:35:47 -08:00
test-requirements.txt For queens sync 2018-09-07 16:24:08 -07:00
tox.ini For queens sync 2018-09-07 16:24:08 -07:00

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: <https://wiki.openstack.org/wiki/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: <https://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
  • SC: Service Chain
  • SP: Service Profile