Difference between revisions of "GroupBasedPolicy"
(→Group Policy Patche) |
|||
| Line 21: | Line 21: | ||
[https://blueprints.launchpad.net/neutron/+spec/group-based-policy-abstraction Launchpad] | [https://blueprints.launchpad.net/neutron/+spec/group-based-policy-abstraction Launchpad] | ||
| − | = Group Policy | + | = Group Policy Patches = |
== StackForge == | == StackForge == | ||
Revision as of 03:32, 25 September 2014
Contents
Overview
The Group-based policy abstractions extend the Neutron API with a declarative policy driven connectivity model that presents simplified application-oriented interfaces to the user.
Juno Code Sprint
Meetings
IRC channel
#openstack-gbp
Blueprints
The blueprints are:
Group Policy Patches
StackForge
https://wiki.openstack.org/wiki/GroupBasedPolicy/StackForge/repos
Neutron
https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches
Supporting documents
Group Policy to Classical Neutron Mapping
Vendor/Open Source Controller Drivers
OpenStack Summit - Atlanta
Proof of Concept implementation and demo
Try it yourself:
git clone http://github.com/noironetworks/devstack.git
cd devstack/
git checkout group-policy-poc
./stack.sh
Run the following script (to create the demo scenario): https://github.com/noironetworks/devstack/blob/group-policy-poc/demo-script.sh
Older documents
Group Based Policy Taxonomy Document
Related project(s)
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
