Files
keystone/doc/source/devref/development.environment.rst
Steve Martinelli 41bb06a69e clean up developer docs
* remove online_schema_migration_examples since they overlap
  with a section in the best practices doc

* move developer docs to doc/source/devref and rename where
  appropriate

* moved content in developer.rst around, so the more often used
  functions (releasenotes, docs, sample config and tests are
  near the top).

* general clean up

Change-Id: If00b6535564644ff1f5b78e232edbac5d6e686f0
2016-11-22 23:06:38 -05:00

2.7 KiB

Setting up a Development Environment

This document describes getting the source from keystone's Git Repository and setting the environment up for development purposes.

To install keystone from packaging, refer instead to OpenStack's User Documentation.

Prerequisites

This document assumes you are using an Ubuntu, Fedora, or openSUSE platform and that you have the following tools pre-installed on your system:

  • Python 2.7 and 3.4, as the programming language;
  • git, as the version control tool;

Reminder: If you are successfully using a different platform, or a different version of the above, please document your configuration here!

Getting the latest code

Make a clone of the code from our git repository and enter the directory:

$ git clone https://git.openstack.org/openstack/keystone.git
$ cd keystone

Development environment

For setting up the Python development environment and running tox testing environments, please refer to the Project Team Guide: Python Project Guide, the OpenStack guide on wide standard practices around the use of Python.

That documentation will guide you to configure your development environment and run keystone tests using tox, which uses virtualenv to isolate the Python environment. After running it, notice the existence of a .tox directory.

Verifying keystone is set up

Once set up, you should be able to invoke Python and import the libraries:

$ .tox/py27/bin/python -c "import keystone"

If you can import keystone without a traceback, you should be ready to move on to ../developing.