Go to file

tengqm 65762507f1 Avoid import internal classes from SDK (3)

This is part of a series of changes related to the usage of SDK. In some
test cases, we are importing the resource classes from SDK directly and
even instantiate them. This is bad for unit tests. We should instead
mock those resources for unit tests. When functional tests are added,
the real resource list/dump will be tested instead.

Change-Id: Ie79c742cdc0173ad66975adecf935fb9fec8d209

2017-02-15 04:00:29 -05:00

doc

Remove unnecessary coding format in the head of files

2017-01-04 17:58:42 +08:00

releasenotes

Update reno for stable/ocata

2017-01-26 10:22:38 +00:00

senlinclient

Avoid import internal classes from SDK (3)

2017-02-15 04:00:29 -05:00

tools

Add Constraints support

2016-12-23 03:02:03 +00:00

.gitignore

Add AUTHORS and ChangeLog into gitignore

2016-10-27 00:30:19 +00:00

.gitreview

Update .gitreview for new namespace

2015-10-17 22:37:46 +00:00

.testr.conf

Initial version

2015-01-04 17:59:59 +08:00

babel.cfg

Initial version

2015-01-04 17:59:59 +08:00

CONTRIBUTING.rst

Modify development doc url in CONTRIBUTING.rst

2016-11-18 14:42:54 +08:00

LICENSE

Initial version

2015-01-04 17:59:59 +08:00

README.rst

Show team and repo badges on README

2016-11-25 17:47:54 +01:00

requirements.txt

Updated from global requirements

2017-02-11 17:52:12 +00:00

run_tests.sh

Initial version

2015-01-04 17:59:59 +08:00

setup.cfg

Client support for node replace

2016-12-12 15:40:40 +08:00

setup.py

Updated from global requirements

2015-09-17 12:18:23 +00:00

test-requirements.txt

Updated from global requirements

2017-02-11 17:52:12 +00:00

TODO

Added one TODO item

2015-02-07 12:12:13 +08:00

tox.ini

Merge "Enable coverage report in console output"

2017-02-15 05:38:50 +00:00

README.rst

Team and repository tags

Python bindings to the Senlin Clustering API

This is a client library for Senlin built on the Senlin clustering API. It provides a Python API (the senlinclient module) and a command-line tool (senlin).

Development takes place via the usual OpenStack processes as outlined in the developer guide. The master repository is in Git.