openstack
/
openstack-manuals
Code Issues Proposed changes

User name fixes 

It's "user name". Also fix markup for them to use systemitem.

Change-Id: I9bb9ac86587686a43cdd9aabd1d975cb7a7c320a
This commit is contained in:
Andreas Jaeger 2014-07-15 21:37:04 +02:00
parent 968f2ddf2a
commit 305f9b9d26
10 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide-cloud/ch_compute.xml
View File

@ -165,7 +165,7 @@
have the <parameter>admin</parameter> role in order to be
able to allocate a public IP address.</para>
<para>A tenant limits users' access to particular images. Each
user is assigned a username and password. Keypairs
user is assigned a user name and password. Keypairs
granting access to an instance are enabled for each user,
but quotas are set, so that each tenant can control
resource consumption across available hardware

6
doc/common/section_cli_nova_baremetal.xml
View File

@ -51,14 +51,14 @@
</itemizedlist>
<section xml:id="cli_nova_baremetal-create">
<title>Create a bare-metal node</title>
<para>When you create a bare-metal node, your PM address, username, and
<para>When you create a bare-metal node, your PM address, user name, and
password should match those that are configured in your hardware's
BIOS/IPMI configuration.</para>
<screen><prompt>$</prompt> <userinput>nova baremetal-node-create --pm_address=PM_ADDRESS --pm_user=PM_USERNAME \
--pm_password=PM_PASSWORD $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff</userinput></screen>
<para>The following example shows the command and results from creating
a node with the PM address <filename>1.2.3.4</filename>, the PM username
<literal>ipmi</literal>, and password <literal>ipmi</literal>.</para>
a node with the PM address <filename>1.2.3.4</filename>, the PM user name
<systemitem class="username">ipmi</systemitem>, and password <literal>ipmi</literal>.</para>
<screen><prompt>$</prompt> <userinput>nova baremetal-node-create --pm_address=1.2.3.4 --pm_user=ipmi \
--pm_password=ipmi $(hostname -f) 1 512 10 aa:bb:cc:dd:ee:ff</userinput>
<computeroutput>+------------------+-------------------+

2
doc/common/section_cli_openrc.xml
View File

@ -93,7 +93,7 @@ export OS_TENANT_ID=<replaceable>tenantIDString</replaceable>
export OS_REGION_NAME=<replaceable>regionName</replaceable></programlisting>
<para>The following example shows the information for
a project called <literal>admin</literal>, where
the OS username is also <literal>admin</literal>,
the OS user name is also <systemitem class="username">admin</systemitem>,
and the identity host is located at
<literal>controller</literal>.</para>
<programlisting language="bash" audience="installer">export OS_USERNAME=admin

2
doc/common/section_keystone_certificates-for-pki.xml
View File

@ -28,7 +28,7 @@
pki_setup</command> command, your best option is to
run as the pki user. If you run nova-manage as root, you
can append --keystone-user and --keystone-group parameters
to set the username and group keystone is going to run
to set the user name and group keystone is going to run
under.</para>
</warning>
<para>The values that specify where to read the certificates are

2
doc/config-reference/block-storage/section_block-storage-overview.xml
View File

@ -58,7 +58,7 @@
actions do not require a particular role, but this can be configured by the system
administrator in the appropriate <filename>policy.json</filename> file that
maintains the rules. A user's access to particular volumes is limited by tenant, but
the username and password are assigned per user. Key pairs granting access to a
the user name and password are assigned per user. Key pairs granting access to a
volume are enabled per user, but quotas to control resource consumption across
available hardware resources are per tenant.</para>
<para>For tenants, quota controls are available to

2
doc/glossary/glossary-terms.xml
View File

@ -789,7 +789,7 @@
<glossdef>
<para>The persistent data store used to save and retrieve information
for a service, such as lists of Object Storage objects, current state
of guest VMs, lists of usernames, and so on. Also, the method that the
of guest VMs, lists of user names, and so on. Also, the method that the
Image Service uses to get and store VM images. Options include Object
Storage, local file system, S3, and HTTP.</para>
</glossdef>

2
doc/high-availability-guide/ha_aa_db/section_ha_aa_db_mysql_galera.xml
View File

@ -55,7 +55,7 @@ Connect as root and grant privileges to that user:
</listitem>
<listitem>
<para>
Remove user accounts with empty usernames because they cause problems:
Remove user accounts with empty user names because they cause problems:
</para>
<screen><prompt>$</prompt> <userinput>mysql -e "SET wsrep_on=OFF; DELETE FROM mysql.user WHERE user='';"</userinput></screen>
</listitem>

4
doc/image-guide/section_ubuntu-example.xml
View File

@ -69,8 +69,8 @@
<simplesect>
<title>Step through the install</title>
<para>Step through the install, using the default options.
When prompted for a username, the default
(<literal>ubuntu</literal>) is fine.</para>
When prompted for a user name, the default
(<systemitem class="username">ubuntu</systemitem>) is fine.</para>
</simplesect>
<simplesect>
<title>Partition the disks</title>

4
doc/install-guide/section_launch-instance-neutron.xml
View File

@ -9,7 +9,7 @@
<title>To generate a keypair</title>
<para>Most cloud images support
<glossterm>public key authentication</glossterm> rather than conventional
username/password authentication. Before launching an instance, you must
user name/password authentication. Before launching an instance, you must
generate a public/private key pair using <command>ssh-keygen</command>
and add the public key to your OpenStack environment.</para>
<step>
@ -167,7 +167,7 @@
<replaceable>controller</replaceable> with the IP address of the
management interface on your controller node.</para>
</note>
<para>The CirrOS image includes conventional username/password
<para>The CirrOS image includes conventional user name/password
authentication and provides these credentials at the login prompt.
After logging into CirrOS, we recommend that you verify network
connectivity using <command>ping</command>.</para>

4
doc/install-guide/section_launch-instance-nova.xml
View File

@ -9,7 +9,7 @@
<title>To generate a keypair</title>
<para>Most cloud images support
<glossterm>public key authentication</glossterm> rather than conventional
username/password authentication. Before launching an instance, you must
user name/password authentication. Before launching an instance, you must
generate a public/private key pair using <command>ssh-keygen</command>
and add the public key to your OpenStack environment.</para>
<step>
@ -172,7 +172,7 @@
<replaceable>controller</replaceable> with the IP address of the
management interface on your controller node.</para>
</note>
<para>The CirrOS image includes conventional username/password
<para>The CirrOS image includes conventional user name/password
authentication and provides these credentials at the login prompt.
After logging into CirrOS, we recommend that you verify network
connectivity using <command>ping</command>.</para>