OpenStack Networking (Neutron) Client
Go to file
Doug Hellmann d830767711 Update README to work with release tools
The README file needs to have links to the project documentation and bug
tracker in a parsable format in order for some of the release tools
scripts to work (particularly the one that prints the release note
email).

Change-Id: I37e0acc5ed8e1af565359290fa622456901c735e
2015-04-21 15:38:25 +00:00
doc/source Stop using intersphinx 2014-09-13 09:44:00 +02:00
neutronclient Merge "Fix one remaining E125 error and remove it from ignore list" 2015-04-09 19:11:46 +00:00
tools Rename quantumclient to neutronclient 2013-07-03 11:56:44 -04:00
.coveragerc update coveragerc file 2014-01-27 16:56:49 +02:00
.gitignore Updates .gitignore 2013-11-28 22:31:43 +08:00
.gitreview Renamed quantum to neutron in .gitreview 2013-07-06 12:29:37 -04:00
.pylintrc Split quantumclient out. 2012-01-18 09:39:25 +11:00
.testr.conf Add OS_TEST_PATH to testr 2015-03-06 22:51:31 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:40 +00:00
HACKING.rst Make HACKING.rst DRYer 2013-11-11 11:29:58 -08:00
LICENSE Split quantumclient out. 2012-01-18 09:39:25 +11:00
MANIFEST.in Rename README to README.rst 2013-06-01 10:08:50 +02:00
README.rst Update README to work with release tools 2015-04-21 15:38:25 +00:00
neutron_test.sh Improvements in neutron_test sanity tests script 2014-03-31 17:02:36 -03:00
requirements.txt Uncap library requirements for liberty 2015-04-16 18:13:29 +00:00
setup.cfg Add Python 3 classifiers 2015-01-07 09:47:21 +01:00
setup.py Updated from global requirements 2014-04-30 02:46:40 +00:00
test-requirements.txt Uncap library requirements for liberty 2015-04-16 18:13:29 +00:00
tox.ini Fix one remaining E125 error and remove it from ignore list 2015-04-09 15:01:52 +00:00

README.rst

Python bindings to the Neutron API

This is a client library for Neutron built on the Neutron API. It provides a Python API (the neutronclient module) and a command-line tool (neutron).

Development takes place via the usual OpenStack processes as outlined in the developer guide.