Fix for keystone example usage
Keystone example usage for keystone auth flags has wrong keyword arguments (flag-like). Keystone accepts token and endpoint on the command line. Valid arguments are --os-token and --os-endpoint. --token should be --os-token --endpoint should be --os-endpoint Also, updating env. varabiles from SERVICE_TOKEN to OS_SERVICE_TOKEN and SERVICE_ENDPOINT to OS_SERVICE_ENDPOINT Change-Id: I24b41c5d7ddfdd7f8a388eb7b7ba1a1b7fa59542 Closes-bug: #1307302
This commit is contained in:
parent
ce57585360
commit
b24c90019f
@ -149,14 +149,14 @@ pipeline = [...] json_body stats_reporting ec2_extension [...] admin_service</pr
|
|||||||
<literal>tenant-create</literal> can be invoked as
|
<literal>tenant-create</literal> can be invoked as
|
||||||
follows:</para>
|
follows:</para>
|
||||||
<programlisting language="bash"><?db-font-size 65%?># Using token auth env variables
|
<programlisting language="bash"><?db-font-size 65%?># Using token auth env variables
|
||||||
export SERVICE_ENDPOINT=http://127.0.0.1:5000/v2.0/
|
export OS_SERVICE_ENDPOINT=http://127.0.0.1:5000/v2.0/
|
||||||
export SERVICE_TOKEN=secrete_token
|
export OS_SERVICE_TOKEN=secrete_token
|
||||||
keystone user-list
|
keystone user-list
|
||||||
keystone tenant-create --name=demo
|
keystone tenant-create --name=demo
|
||||||
|
|
||||||
# Using token auth flags
|
# Using token auth flags
|
||||||
keystone --token=secrete --endpoint=http://127.0.0.1:5000/v2.0/ user-list
|
keystone --os-token=secrete --os-endpoint=http://127.0.0.1:5000/v2.0/ user-list
|
||||||
keystone --token=secrete --endpoint=http://127.0.0.1:5000/v2.0/ tenant-create --name=demo
|
keystone --os-token=secrete --os-endpoint=http://127.0.0.1:5000/v2.0/ tenant-create --name=demo
|
||||||
|
|
||||||
# Using user + password + tenant_name env variables
|
# Using user + password + tenant_name env variables
|
||||||
export OS_USERNAME=admin
|
export OS_USERNAME=admin
|
||||||
|
Loading…
Reference in New Issue
Block a user