keystone/docs/source/developing.rst

Developing with Keystone

Contributing Code

To contribute code, sign up for a Launchpad account and sign a contributor license agreement, available on the http://wiki.openstack.org/CLA. Once the CLA is signed you can contribute code through the Gerrit version control system which is related to your Launchpad account.

To contribute tests, docs, code, etc, refer to our Gerrit-Jenkins-Github Workflow.

Setup

Get your development environment set up according to setup. The instructions from here will assume that you have installed keystone into a virtualenv. If you chose not to, simply exclude "tools/with_venv.sh" from the example commands below.

Running Keystone

To run the keystone Admin and API server instances, use:

$ tools/with_venv.sh bin/keystone-all

this runs keystone with the configuration the etc/ directory of the project. See configuration for details on how Keystone is configured.

Interacting with Keystone

You can interact with Keystone through the command line using man/keystone-manage which allows you to establish tenants, users, etc.

You can also interact with Keystone through it's REST API. There is a python keystone client library python-keystoneclient which interacts exclusively through the REST API, and which keystone itself uses to provide it's command-line interface.

When initially getting set up, after you've configured which databases to use, you're probably going to need to run the following to your database schema in place :

$ bin/keystone-manage db_sync

Running Tests

To run the full suites of tests maintained within Keystone, run:

$ ./run_tests.sh

This shows realtime feedback during test execution, iterates over multiple configuration variations, and uses external projects to do light integration testing to verify the keystone API against other projects.

Test Structure

./run_test.sh uses its python cohort (run_tests.py) to iterate through the tests directory, using Nosetest to collect the tests and invoke them using an OpenStack custom test running that displays the tests as well as the time taken to run those tests.

Within the tests directory, the general structure of the tests is a basic set of tests represented under a test class, and then subclasses of those tests under other classes with different configurations to drive different backends through the APIs.

For example, test_backend.py has a sequence of tests under the class IdentityTests that will work with the default drivers as configured in this projects etc/ directory. test_backend_sql.py subclasses those tests, changing the configuration by overriding with configuration files stored in the tests directory aimed at enabling the SQL backend for the Identity module.

Likewise, test_cli.py takes advantage of the tests written aainst test_keystoneclient to verify the same tests function through different drivers.

Testing Schema Migrations

The application of schema migrations can be tested using SQLAlchemy Migrate’s built-in test runner, one migration at a time.

Warning

This may leave your database in an inconsistent state; attempt this in non-production environments only!

This is useful for testing the next migration in sequence (both forward & backward) in a database under version control:

python keystone/common/sql/migrate_repo/manage.py test \
--url=sqlite:///test.db \
--repository=keystone/common/sql/migrate_repo/

This command references to a SQLite database (test.db) to be used. Depending on the migration, this command alone does not make assertions as to the integrity of your data during migration.

Writing Tests

To add tests covering all drivers, update the base test class (test_backend.py, test_legacy_compat.py, and test_keystoneclient.py).

To add new drivers, subclass the test_backend.py (look towards test_backend_sql.py or test_backend_kvs.py for examples) and update the configuration of the test class in setUp().

Further Testing

devstack is the best way to quickly deploy keystone with the rest of the OpenStack universe and should be critical step in your development workflow!

You may also be interested in either the OpenStack Continuous Integration Project or the OpenStack Integration Testing Project.

Building the Documentation

The documentation is all generated with Sphinx from within the docs directory. To generate the full set of HTML documentation:

cd docs make autodoc make html make man

the results are in the docs/build/html and docs/build/man directories respectively.