Go to file

Vladimir Kuklin 7597187095 Add support for dry-run and noop deployment for deploy changes commands

This commit adds an additional options to fuel client to support
dry-run and noop modes of deployment which are really useful for
debugging and day-to day operations and life cycle management of
clusters

Partial-bug: #1569839

Change-Id: I77d0a8257a97a9f40e3cfd1a630c95b7800fe1e6

2016-05-23 15:02:46 +03:00

fuelclient

Add support for dry-run and noop deployment for deploy changes commands

2016-05-23 15:02:46 +03:00

specs

Bump version to 10.0

2016-03-27 20:29:43 +00:00

tools

Use OS command line parameters for credentials

2016-02-12 16:01:47 +01: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

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

Update requirements

2016-03-08 17:54:01 +00:00

run_tests.sh

Tox to manage all test environments on its own

2015-08-19 11:45:24 +02:00

setup.cfg

Add create operation for VIP related commands

2016-05-06 12:09:46 +03:00

setup.py

Ensure fuel-client spec compatibility with CentOS 7

2015-12-01 15:51:30 +03:00

test-requirements.txt

Use common tools to fire up tests

2016-03-10 15:37:54 +01:00

tox.ini

Merge "Introduced command 'env redeploy' in v2 version of fuelclient"

2016-04-04 10:07:37 +00: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