User:Rbenali

Interacting with Grizzly Cloud testbed with cURL as ReST Client to API servers
Note 1: User “test1” with password “secrete” has admin role on tenant (i.e. project) “test1” in cloud A (Grizzly controllerA=10.126.72.253) User “demo” with password “secrete” has admin role on tenant (i.e. project) “demo” in cloud B (Grizzly controllerB=10.126.71.253)

Note 2: Keystone v2 in Grizzly release has a default configuration of using PKI for Token generation. Therefore, the Token id returned is a PKI-encrypted long key that is validated without contacting Keystone service which will save some frequent ReST HTTP traffic (with Keystone PKI public key). It is possible to still use the previous way of validating tokens (by contacting Keystone service for each validation). https://wiki.openstack.org/wiki/PKI In /etc/keystone/keystone.conf: token_format = UUID
 * 1) default
 * 2) token_format = PKI