Files

vponomaryov a05a48b59c Add info about functional tests run to docs

Make doc with tests description up-to-date and provide there information
that describes how to run functional tests.

Partially implements bp functional-tests

Change-Id: Iad6b1d97a9c43dd24c2c6837bb71739a6f09bb1e

2015-01-14 15:41:28 +00:00

1.9 KiB

Raw Blame History

Python bindings to the OpenStack Manila API

This is a client for OpenStack Manila API. There's a Python API <api> (the manilaclient module), and a command-line script <shell> (installed as manila). Each implements the entire OpenStack Manila API.

You'll need credentials for an OpenStack cloud that implements the Manila API in order to use the manila client.

Contents:

shell api

Contributing

Code is hosted at git.openstack.org. Submit bugs to the python-manilaclient project on Launchpad. Submit code to the openstack/python-manilaclient project using Gerrit.

Testing

Manilaclient has two types of tests - 'unit' and 'functional'.

The preferred way to run tests is using tox.

See Consistent Testing Interface for more details.

Functional tests

Functional CLI tests require several things to be able to run: - Deployed and working manila service. - Configured config file.

Config file is used to get information like 'auth_url', 'username', 'tenant_name' and 'password'. To get config sample need to run following 'tox' job: $ tox -e genconfig This will create file 'etc/manilaclient/manilaclient.conf.sample' with all available config opts. Then rename it removing ".sample" and set values for opts there. After it, tests can be run using following tox job: $ tox -e functional

Indices and tables

genindex
modindex
search

Release Notes

No releases.

1.9 KiB Raw Blame History