f7c04df5ec
Questions: * The implementation is now KeyCloak specific in part of using realms as a substition for Keystone projects (multitenancy). Based on a realm name (in fact, project name) we build a url where we send auth requests. Can we move away from KeyCloak specifics and provide a pure OpenID Connect implementation? TODO: * Reusing existing token * Refreshin a token NOTE: This addition now looks slightly hacky because we try to put all possible auth parameters into Client initializer. Ideally, authentication method should be pluggable similar to the new Keystone approach with separation sessions and authentication methods (see keystoneauth project). This separation can be addressed only in Mistral future versions because all changes in API/CLI v2 have to be backwards compatible. API/CLI v3 must address this architectural issue. Change-Id: I845b2bfbc1877e6f4b0c1a523d136e01c3742865
Mistral client
Python client for Mistral REST API. Includes python library for Mistral API and Command Line Interface (CLI) library.
Installation
First of all, clone the repo and go to the repo directory:
git clone git://git.openstack.org/openstack/python-mistralclient.git
cd python-mistralclient
Then just run:
pip install -e .
or
python setup.py install
Running Mistral client
If Mistral authentication is enabled, provide the information about OpenStack auth to environment variables. Type:
export OS_AUTH_URL=http://<Keystone_host>:5000/v2.0
export OS_USERNAME=admin
export OS_TENANT_NAME=tenant
export OS_PASSWORD=secret
export OS_MISTRAL_URL=http://<Mistral host>:8989/v2 (optional, by default URL=http://localhost:8989/v2)
and in the case that you are authenticating against keystone over https:
export OS_CACERT=<path_to_ca_cert>
Note: In client, we can use both Keystone auth versions - v2.0 and v3. But server supports only v3.
To make sure Mistral client works, type:
mistral workbook-list
You can see the list of available commands typing:
mistral --help