Tom Cocozzello
9a92c471e4
`patch_cover` checks to make sure your patch has adequate test coverage. How it works is it stashes your changes, runs `tox -e cover`, saves the results then stash pops your change and runs cover again. It then reports to show if your code in your patch has 100% test coverage or not. The intent of this job is to be a non-voting / warning like job that can inform reviewers if the review clearly needs more testing. Since cover.sh is copied from [0] the copyright should reflect the owners of the code. [0]: https://github.com/openstack/rally/blob/master/tests/ci/cover.sh Change-Id: I66572072aa4d9563b6e1f73a8f8b3437116ef3c4
OpenStack Keystone
Keystone provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. It is most commonly deployed as an HTTP interface to existing identity systems, such as LDAP.
Developer documentation, the source of which is in
doc/source/, is published at:
The API specification and documentation are available at:
The canonical client library is available at:
https://git.openstack.org/cgit/openstack/python-keystoneclient
Documentation for cloud administrators is available at:
The source of documentation for cloud administrators is available at:
Information about our team meeting is available at:
Bugs and feature requests are tracked on Launchpad at:
Future design work is tracked at:
http://specs.openstack.org/openstack/keystone-specs/#identity-program-specifications
Contributors are encouraged to join IRC
(#openstack-keystone on freenode):
For information on contributing to Keystone, see
CONTRIBUTING.rst.