OpenStack Networking (Neutron) Client
Go to file
Akihiro Motoki 66b03a8167 Add reno for release notes management
In addition to the convention of releasenotes/source directory
which used in most OpenStack project, we have the release notes
in our developer documents.

Change-Id: Ied07af5ee5c8929e639e17a34b559cebfe419dc4
2015-11-24 07:39:23 +09:00
doc/source Add reno for release notes management 2015-11-24 07:39:23 +09:00
neutronclient Add reno for release notes management 2015-11-24 07:39:23 +09:00
releasenotes Add reno for release notes management 2015-11-24 07:39:23 +09:00
tools Fixes indentation for bash completion script 2015-06-12 20:41:47 +00:00
.coveragerc update coveragerc file 2014-01-27 16:56:49 +02:00
.gitignore Add reno for release notes management 2015-11-24 07:39:23 +09: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 Add allowed-address-pairs to port-update 2015-10-01 11:07:35 +09:00
requirements.txt Use os-client-config and keystoneauth1 in shell 2015-10-28 08:01:13 +09:00
setup.cfg Add Python 3 classifiers 2015-01-07 09:47:21 +01:00
setup.py Updated from global requirements 2015-09-17 12:16:54 +00:00
test-requirements.txt Add reno for release notes management 2015-11-24 07:39:23 +09:00
tox.ini Add reno for release notes management 2015-11-24 07:39:23 +09: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.