GroupBasedPolicy
Contents
Overview
The Group-based policy abstractions introduce simplified and application-oriented interfaces with the current Neutron API model that allow for easier consumption of the networking resources by separate organizations and management systems.
Meetings
Blueprints
The blueprints are:
Gerrit: TBA
Launchpad: https://blueprints.launchpad.net/neutron/+spec/group-based-policy-abstraction
Supporting documents
Model: https://docs.google.com/a/noironetworks.com/presentation/d/1Nn1HjghAvk2RTPwvltSrnCUJkidWKWY2ckU7OYAVNpo/edit#slide=id.g1c910cf8b_038 PoC: https://docs.google.com/document/d/14UyvBkptmrxB9FsWEP8PEGv9kLqTQbsmlRxnqeF9Be8/edit#heading=h.hyj8vcqqd6ib
Older documents
Original proposal: https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit
Group Based Policy Taxonomy Document: https://docs.google.com/drawings/d/1HYGUSnxcx_8wkCAwE4Wtv3a30JstOBPyuknf7UnJMp0/edit?usp=sharing
Related project(s): https://wiki.opendaylight.org/view/Project_Proposals:Application_Policy_Plugin
Juno Plan
Bugs
All open Group Policy bugs across the projects.
How To Install and Test
Integration Repo
Temporary integration repo:
Neutron: https://github.com/noironetworks/neutron-group-policy
Neutron Client: https://github.com/noironetworks/python-neutronclient
Integration repo usage:
1. We will create a feature branch for any feature that requires collaboration between us before we can push it upstream. The API branch is for API changes, for a different feature, we will should create a new branch.
2. To work on that specific feature, we should take personal development branch from that branch. And when ready, we should create a pull request for the feature branch.
3. Once the feature had the multiple updates integrated and ready for upstream, we will push upstream from that feature branch