gardlt 7b26e59422 feat(cli): using-click-framework

- using click framework
- added api client
- allow interactions between code and service endpoints
- documention on the command line
- updated gitignore

Change-Id: Ibe359025f5b35606d876c29fa88e04048f276cc8

2017-11-02 20:59:57 +00:00

1.3 KiB

Raw Blame History

Configuring Armada

Armada uses an INI-like standard oslo_config file. A sample file can be generated via tox

$ tox -e genconfig
$ tox -e genpolicy

Customize your configuration based on the information below

Keystone Integration

Armada requires a service account to use for validating API tokens

Note

If you do not have a keystone already deploy, then armada can deploy a keystone services:

$ armada apply keystone-manifest.yaml

$ openstack domain create 'ucp'
$ openstack project create --domain 'ucp' 'service'
$ openstack user create --domain ucp --project service --project-domain 'ucp' --password armada armada
$ openstack role add --project-domain ucp --user-domain ucp --user armada --project service admin

# OR

$ ./tools/keystone-account.sh

The service account must then be included in the armada.conf

[keystone_authtoken]
auth_type = password
auth_uri = https://<keystone-api>:5000/
auth_url = https://<keystone-api>:35357/
auth_version = 3
delay_auth_decision = true
password = armada
project_domain_name = ucp
project_name = service
user_domain_name = ucp
user_name = armada

1.3 KiB Raw Blame History

Configuring Armada

Keystone Integration

1.3 KiB

Raw Blame History