RETIRED, Client for Fuel.
Go to file
Bulat Gaifullin 330b10a052 Add option to get merged facts for environment
Since 9.1 the nailgun returns separated facts for cluster
and nodes, so some client expects that node facts also
contains cluster fact. this patch adds possibility
to get merged facts for each node, by default this flag is true

Change-Id: I29f0cc0090abca2826e273dcbe7ac4249cf7a731
Closes-Bug: 1623854
2016-09-16 15:07:07 +03:00
fuelclient Add option to get merged facts for environment 2016-09-16 15:07:07 +03:00
specs Bump version to 10.0 2016-03-27 20:29:43 +00:00
tools Use fuel-web nailgun start/stop scripts 2016-06-14 15:44:43 +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 Update link to developers' manual 2015-07-01 15:35:23 +02:00
requirements.txt Add common code for node attributes 2016-07-14 17:42:33 +02:00
setup.cfg Add fuel2 commands to operate on extensions 2016-09-14 18:55:31 +03: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

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