Python bindings and CLI for Sahara.
Go to file
Vitaly Gridnev 8c288becd1 remove old cli commands
master branch is now open for ocata development, so we
can start removing old cli commands from saharaclient
code.

Change-Id: I67543120309e838239fe73b8dd2713368b8538a9
2016-10-01 15:51:11 +00:00
doc Fix doc build if git is absent 2016-08-31 16:01:53 +02:00
releasenotes remove old cli commands 2016-10-01 15:51:11 +00:00
saharaclient remove old cli commands 2016-10-01 15:51:11 +00:00
tools Merge "print statment has become a function in py3" 2016-06-27 22:08:46 +00:00
.coveragerc remove old cli commands 2016-10-01 15:51:11 +00:00
.gitignore Add releasenotes to sahara client 2015-12-08 10:51:06 -08:00
.gitreview Update .gitreview to point on updated repo 2014-03-12 16:57:56 +04:00
.testr.conf Restructure tests directory in preparation for cli integration tests 2014-04-22 10:24:17 -04:00
CONTRIBUTING.rst Add CONTRIBUTING.rst 2015-04-07 10:20:27 +00:00
HACKING.rst Change client doc references to sahara 2014-03-13 13:47:53 -04:00
LICENSE Python Savanna Client initial implementation 2013-08-02 23:03:47 +04:00
MANIFEST.in Python Savanna Client initial implementation 2013-08-02 23:03:47 +04:00
README.rst Improve readme contents 2015-10-16 09:07:17 +08:00
requirements.txt remove old cli commands 2016-10-01 15:51:11 +00:00
run_tests.sh Change packaging references to python-saharaclient 2014-03-13 22:24:51 +00:00
setup.cfg remove old cli commands 2016-10-01 15:51:11 +00:00
setup.py Updated from global requirements 2015-09-24 01:07:32 +00:00
test-requirements.txt Remove discover from test-requirements 2016-07-22 04:10:35 +00:00
tox.ini remove old cli commands 2016-10-01 15:51:11 +00:00

README.rst

Python bindings to the OpenStack Sahara API

Latest Version

Downloads

This is a client for the OpenStack Sahara API. There's a Python API (the saharaclient module), and a command-line script (sahara). Each implements the OpenStack Sahara API. You can find documentation for both Python bindings and CLI in Docs.

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