Go to file

TommyLike c053973138 Support certificate validation

This spec proposes to support validating certificates
when verifying image signatures.

While image signing ensures that image data is obtained
unmodified from Glance, it does not prevent an attacker from
uploading and signing a malicious image. The addition of Cinder
API changes allows Cinder users to control the certificates
which are allowed to sign images.

This is a follow up propose from signature verification [1],
also same as Nova certification validation feature [2].

Partial-Implements: bp certificate-validate

[1]: 1faf87284cf674c52a50a9feff6086c05014185c
[2]: 9f0a8999af83bff14acfb0e1adfbcbdbdc2233e6

Change-Id: I9fbab8948cf4ce2e165841fa7d4f998941516908

2018-12-27 01:42:42 +00:00

doc

Add Rocky support in doc

2017-12-12 15:50:42 +08:00

specs

Support certificate validation

2018-12-27 01:42:42 +00:00

.gitignore

Adds Block Storage v2 API specification information

2014-10-17 20:30:44 -05:00

.gitreview

Added .gitreview

2014-05-09 22:05:53 +00:00

.testr.conf

Initialize the Cinder-Specs Repository

2014-05-20 19:37:21 -06:00

bindep.txt

Update bindep.txt for doc builds

2017-12-25 15:35:20 +00:00

LICENSE

Initialize the Cinder-Specs Repository

2014-05-20 19:37:21 -06:00

README.rst

Update url of the cinder-specs's document

2017-09-15 05:38:06 +00:00

setup.cfg

Remove support for py34.

2017-06-21 07:35:25 +00:00

setup.py

Fix rst formatting and fix tox

2014-07-17 18:13:42 -07:00

test-requirements.txt

Clean up required packages

2017-11-17 16:53:57 -06:00

tox.ini

Clean up required packages

2017-11-17 16:53:57 -06:00

README.rst

Team and repository tags

OpenStack Cinder Specifications

This git repository is used to hold approved design specifications for additions to the Cinder 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:

https://blueprints.launchpad.net/cinder

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:

https://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. Please do not checkin the generated HTML files as a part of your commit.