Python bindings and CLI for Sahara.
Go to file
OpenStack Proposal Bot 39985d1b67 Updated from global requirements
Change-Id: Ia053ccfefa511fa4c5906ff0e69334fc30220b4b
2015-12-01 06:10:13 +00:00
doc Merge "Adding sphinx extension for CLI docs autogeneration" 2015-11-26 19:07:52 +00:00
saharaclient Merge "Adding ability to provide name or ID of the flavor in CLI" 2015-11-25 17:20:05 +00:00
tools Use pretty-tox for better test output 2015-02-03 08:43:33 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:54:27 +00:00
.gitignore Add *.log to gitignore 2015-11-02 16:17:48 -05: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
openstack-common.conf Remove importutils from openstack-common.conf 2015-02-04 13:38:27 -05:00
requirements.txt Updated from global requirements 2015-12-01 06:10:13 +00:00
run_tests.sh Change packaging references to python-saharaclient 2014-03-13 22:24:51 +00:00
setup.cfg Adding Job Binaries support to CLI 2015-10-29 22:03:38 +00:00
setup.py Updated from global requirements 2015-09-24 01:07:32 +00:00
test-requirements.txt Updated from global requirements 2015-12-01 06:10:13 +00:00
tox.ini Adding sphinx extension for CLI docs autogeneration 2015-11-12 19:56:00 +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.