Difference between revisions of "GroupBasedPolicy"
(→Current Branches) |
m (→Python-Neutronclient Repo) |
||
| Line 64: | Line 64: | ||
==Python-Neutronclient Repo== | ==Python-Neutronclient Repo== | ||
| − | [https://github.com/noironetworks/python-neutronclient/ | + | [https://github.com/noironetworks/python-neutronclient/ The main Python-Neutronclient repo] |
* [https://github.com/noironetworks/python-neutronclient/tree/group-policy Client Branch] | * [https://github.com/noironetworks/python-neutronclient/tree/group-policy Client Branch] | ||
Revision as of 08:04, 18 April 2014
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
Supporting documents
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
