From b24c90019fd4528b532242ddb773e79610b3a7e7 Mon Sep 17 00:00:00 2001 From: Priti Desai Date: Mon, 14 Apr 2014 14:48:20 +0000 Subject: [PATCH] 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 --- doc/admin-guide-cloud/ch_identity_mgmt.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/admin-guide-cloud/ch_identity_mgmt.xml b/doc/admin-guide-cloud/ch_identity_mgmt.xml index c9cfb8b83c..6e2006d2e1 100644 --- a/doc/admin-guide-cloud/ch_identity_mgmt.xml +++ b/doc/admin-guide-cloud/ch_identity_mgmt.xml @@ -149,14 +149,14 @@ pipeline = [...] json_body stats_reporting ec2_extension [...] admin_servicetenant-create can be invoked as follows: # Using token auth env variables -export SERVICE_ENDPOINT=http://127.0.0.1:5000/v2.0/ -export SERVICE_TOKEN=secrete_token +export OS_SERVICE_ENDPOINT=http://127.0.0.1:5000/v2.0/ +export OS_SERVICE_TOKEN=secrete_token keystone user-list keystone tenant-create --name=demo # Using token auth flags -keystone --token=secrete --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/ user-list +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 export OS_USERNAME=admin