Skip to content
Python bindings and CLI for Sahara.
Python
Branch: master
Clone or download
tosky py3: use the train test template and other updates
Use the unified unit test Zuul template for train, according the
community goal. Also, update the setup.cfg classifiers accordingly.

Update the debug test environment. Adding "debug-py36" is enough;
if a distribution supports 3.7, the "debug" tox environment
can be used.

Finally, keep only the most recent environment in the default
set executed when calling tox.

Story: #2005924
Task: #34244

Change-Id: Iad4a6e933ad416eb67a2f144540fe79e97938bec
Latest commit 3107b45 Jul 11, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc Update sphinx from current requirements Jun 25, 2019
releasenotes Py3: fix the OSC download job binary command May 31, 2019
saharaclient Py3: fix the OSC download job binary command May 31, 2019
.coveragerc remove old cli commands Oct 1, 2016
.gitignore
.gitreview OpenDev Migration Patch Apr 19, 2019
.stestr.conf [ut] replace .testr.conf with .stestr.conf Sep 13, 2017
.zuul.yaml py3: use the train test template and other updates Jul 11, 2019
CONTRIBUTING.rst
HACKING.rst
LICENSE Python Savanna Client initial implementation Aug 2, 2013
README.rst Replace git.openstack.org URLs with opendev.org URLs Apr 20, 2019
lower-constraints.txt
requirements.txt Adding boot from volume to osc Jul 19, 2018
setup.cfg py3: use the train test template and other updates Jul 11, 2019
setup.py Updated from global requirements Mar 3, 2017
test-requirements.txt Switch to using stestr Jun 29, 2018
tox.ini py3: use the train test template and other updates Jul 11, 2019

README.rst

Team and repository tags

Python bindings to the OpenStack Sahara API

Latest Version

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.

You can’t perform that action at this time.