Conversation
There was a problem hiding this comment.
I think all (or most of) the OpenStack CLI code is already available upstream. See i.e. https://github.com/openstack/python-openstackclient/blob/master/functional/tests/identity/v2/test_project.py . Why are not using that code (and extend it if needed)?
There was a problem hiding this comment.
Would it make sense to add checks for SSL,PKI and Tokens instead of using openstack client tests here ?
There was a problem hiding this comment.
The client uses SSL and PKI tokens if that's what was deployed. AFAIR we agreed to not check things like "Feature A was enabled, now check if Feature A is really enabled". That will be done with crowbar_batch. Or am I missunderstanding your question?
|
@mmnelemane can you rebase this? |
494aa8a to
7154238
Compare
7154238 to
fa078dc
Compare
|
https://ci.suse.de/job/openstack-mkcloud/15243/ failed in cct |
|
@bmwiedemann: corrected that. |
Added basic feature tests for keystone with
Access to keystone resource lists(eg: services, projects, users, hosts etc) through openstackclient
create/delete users and project using openstackclient command line interface
Added new openstack.rb function to the cct library to include command for "openstack host list"