openstack
/
barbican-specs
Code Issues Proposed changes
Blueprints for the barbican project
98 Commits 1 Branch 0 Tags 2.8 MiB
Python 100%
Go to file
Dave McCowan 1765b923da Update Project Quotas design spec 
Upon discovery and discussion, this commit brings three changes to the
design spec for project quotas.

1) Removal of quota support for transport keys.  It turns out they
   are not a project resource and should not be managed on a per
   project basis.
2) New role for quota management.  The management of project quotas
   can not fall to project level admins.  This must be the responsibility
   of a service level admin.  A new keystone role is introduced to
   implement this change.
3) Clarification of paging support.  The examples are updated to clarify
   the paging support to be implemented for listing project quotas.

Change-Id: I4d5fb76e2868f63f623a8a3cd0b14d0bba31290a
Relates-to: blueprint quota-support-on-barbican-resources
 		2015-08-18 18:33:13 -04:00
doc/source Drop incubating theme from docs 2015-05-27 15:12:33 -07:00
specs Update Project Quotas design spec 2015-08-18 18:33:13 -04:00
.gitignore Initial commit 2014-05-15 10:54:58 -07:00
.gitreview gitreview 2014-06-03 15:10:06 -05:00
LICENSE Add License and README 2014-05-15 14:02:39 -04:00
README.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:35 +00:00
requirements.txt Add RSS feed 2014-09-10 15:56:50 -04:00
setup.cfg Remove leftover references to Nova 2014-07-31 16:54:09 -05:00
setup.py First Pass at Doc Build 2014-05-19 20:56:54 -05:00
tox.ini remove py27 2014-06-04 12:03:47 -05:00

README.rst

OpenStack Barbican Specifications

This git repository is used to hold approved design specifications for additions to the Barbican project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.

The layout of this repository is:

specs/<release>/

You can find an example spec in specs/template.rst.

Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.

Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.

Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

http://blueprints.launchpad.net/barbican

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see:

http://docs.openstack.org/infra/manual/developers.html#development-workflow

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.