Adds note about possible mismatch between keystoneclient params
related to --token and --endpoint params used with keystone client commands. Rebase against master to pick up that note. Adds link to pip install instructions in the CLI guide to the note. Change-Id: Iee15faa11c92a0ad216e71bd7510b8d4659fe885
This commit is contained in:
@@ -100,15 +100,29 @@
|
||||
linkend="setting-up-tenants-users-and-roles-manually">manual
|
||||
steps</link> or <link linkend="scripted-keystone-setup">use a
|
||||
script</link>. </para>
|
||||
<note>
|
||||
<para>The parameters --os-token and --os-endpoint are valid for
|
||||
the keystoneclient available after October 2012. Use --token
|
||||
and --endpoint with the keystoneclient released with the
|
||||
Folsom packaging. This install guide documents installing the
|
||||
client from packages, but you can use the client from another
|
||||
computer with the <link
|
||||
xlink:href="http://docs.openstack.org/cli/quick-start/content/install_openstack_keystone_cli.html"
|
||||
>CLI Guide instructions for pip install</link>.</para>
|
||||
</note>
|
||||
<section xml:id="setting-up-tenants-users-and-roles-manually">
|
||||
<title>Setting up tenants, users, and roles - manually</title>
|
||||
<para>You need to minimally define a tenant, user, and role to
|
||||
link the tenant and user as the most basic set of details to
|
||||
get other services authenticating and authorizing with the
|
||||
Identity service. </para>
|
||||
<note><title>Scripted method available</title><para>These are the manual, unscripted steps using the keystone
|
||||
client. A scripted method is
|
||||
available at <link linkend="scripted-keystone-setup">Setting up tenants, users, and roles - scripted</link>. </para></note>
|
||||
<note>
|
||||
<title>Scripted method available</title>
|
||||
<para>These are the manual, unscripted steps using the
|
||||
keystone client. A scripted method is available at <link
|
||||
linkend="scripted-keystone-setup">Setting up tenants,
|
||||
users, and roles - scripted</link>. </para>
|
||||
</note>
|
||||
<para>First, create a default tenant, we'll name it
|
||||
<literal>demo</literal> in this example.</para>
|
||||
<screen><prompt>$</prompt> <userinput>keystone --os-token 012345SECRET99TOKEN012345 --os-endpoint http://192.168.206.130:35357/v2.0 tenant-create --name demo --description "Default Tenant"</userinput></screen>
|
||||
@@ -131,7 +145,9 @@
|
||||
| name | admin |
|
||||
| tenantId | b5815b046cfe47bb891a7b64119e7f80 |
|
||||
+----------+----------------------------------+</programlisting>
|
||||
<para>Create an administrative role based on keystone's default <literal>policy.json</literal> file, <literal>admin</literal>.</para>
|
||||
<para>Create an administrative role based on keystone's default
|
||||
<literal>policy.json</literal> file,
|
||||
<literal>admin</literal>.</para>
|
||||
<screen><prompt>$</prompt> <userinput>keystone --os-token 012345SECRET99TOKEN012345 --os-endpoint http://192.168.206.130:35357/v2.0 role-create --name admin</userinput></screen>
|
||||
<programlisting> +----------+----------------------------------+
|
||||
| Property | Value |
|
||||
|
||||
Reference in New Issue
Block a user