RETIRED, Client for Fuel.
Go to file
Sergey Kulanov 438bce600f Align git branches for tests
We need to use stable/mitaka branch both in python-fuelclient
and fuel-web

Switching to full repo cloning since for now we need
checkout to other branches

Change-Id: Ib3018bcda4e9e89a1ca9f80447883896f4db3b8c
Related-bug: #1558589
(cherry picked from commit a2388bc910)
2017-01-31 15:14:38 +03:00
fuelclient Align help message for 'fuel2 sequence list' command 2017-01-25 10:30:10 +02:00
specs Bump version to 10.0 2016-03-27 20:29:43 +00:00
tools Align git branches for tests 2017-01-31 15:14:38 +03:00
.gitignore Support separate jUnit files for environments 2015-08-19 16:50:25 +02:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:36:42 +00:00
.testr.conf Generate user settings file 2015-10-20 14:27:37 +02:00
MAINTAINERS MAINTAINERS 2016-03-17 10:46:50 +02:00
MANIFEST.in Revert "Removes MANIFEST.in as it is not needed explicitely by PBR" 2015-12-21 16:57:15 +00:00
README.rst Show team and repo badges on README 2016-11-25 17:43:16 +01:00
requirements.txt Add common code for node attributes 2016-07-14 17:42:33 +02:00
setup.cfg Remove entry point for nonexistent 'fuel2 tag show' command 2016-11-28 14:28:32 +02:00
setup.py Ensure fuel-client spec compatibility with CentOS 7 2015-12-01 15:51:30 +03:00
test-requirements.txt Add testtools to the test-requirements.txt file 2016-05-24 12:46:31 +03:00
tox.ini Use fuel-web nailgun start/stop scripts 2016-06-14 15:44:43 +03:00

README.rst

Team and repository tags

image

python-fuelclient

python-fuelclient provides a CLI tool and a Python API wrapper for interacting with Fuel.

Project resources

Project status, bugs, and blueprints are tracked on Launchpad:

https://launchpad.net/fuel

Development documentation is hosted here:

https://docs.fuel-infra.org/fuel-dev

User guide can be found here:

http://docs.mirantis.com

Any additional information can be found on the Fuel's project wiki

https://wiki.openstack.org/wiki/Fuel

Anyone wishing to contribute to python-fuelclient should follow the general OpenStack process. A good reference for it can be found here: https://wiki.openstack.org/wiki/How_To_Contribute

http://docs.openstack.org/infra/manual/developers.html