Remove extra whitespace
Fixes output of tools/validate.py --force (except training-guide and generated files) Change-Id: I720846d97ab150915b26fb56926f0971d1808a2a
This commit is contained in:
@@ -50,7 +50,7 @@
|
||||
<itemizedlist spacing="compact">
|
||||
<listitem>
|
||||
<para>Moves object storage monitoring section to this guide.</para></listitem>
|
||||
<listitem><para>Removes redundant object storage info.</para></listitem>
|
||||
<listitem><para>Removes redundant object storage info.</para></listitem>
|
||||
</itemizedlist>
|
||||
</revdescription>
|
||||
</revision>
|
||||
|
@@ -1,8 +1,8 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<chapter xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
version="5.0"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
version="5.0"
|
||||
xml:id="ch_admin-openstack-object-storage">
|
||||
<title>Object Storage</title>
|
||||
<para>OpenStack Object Storage is a scalable object storage system—it is not a file system in
|
||||
|
@@ -1,8 +1,8 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
version="5.0"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
version="5.0"
|
||||
xml:id="ch_introduction-to-openstack-object-storage-monitoring">
|
||||
<title>OpenStack Object Storage Monitoring</title>
|
||||
<?dbhtml stop-chunking?>
|
||||
|
@@ -808,11 +808,11 @@ neutron lb-vip-create --name myvip --protocol-port 80 --protocol HTTP --subnet-i
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Create a port with a specific allowed-address-pairs:</para>
|
||||
<screen><prompt>$</prompt><userinput> neutron port-create net1 --allowed-address-pairs type=dict list=true mac_address=<mac_address>,ip_address=<ip_cidr></userinput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>neutron port-create net1 --allowed-address-pairs type=dict list=true mac_address=<mac_address>,ip_address=<ip_cidr></userinput></screen>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Update a port adding allowed-address-pairs:</para>
|
||||
<screen><prompt>$</prompt><userinput> neutron port-update <subnet-uuid> --allowed-address-pairs type=dict list=true mac_address=<mac_address>,ip_address=<ip_cidr></userinput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>neutron port-update <subnet-uuid> --allowed-address-pairs type=dict list=true mac_address=<mac_address>,ip_address=<ip_cidr></userinput></screen>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<note><para>Setting an allowed-address-pair that matches the
|
||||
|
@@ -65,7 +65,7 @@ log_dir =/var/log/neutron</programlisting>
|
||||
<title>Notification Options</title>
|
||||
<para>You can send notifications when creating, updating, or deleting OpenStack Networking
|
||||
resources. To support a DHCP agent, you must set up an <literal>rpc_notifier</literal>
|
||||
driver. </para>
|
||||
driver.</para>
|
||||
<para>To configure notifications, update settings in the
|
||||
<filename>/etc/neutron/neutron.conf</filename> file. For example:</para>
|
||||
<programlisting language="ini">============ Notification System Options =====================
|
||||
@@ -231,8 +231,8 @@ quota_security_group_rule = 100</programlisting>
|
||||
enable per-tenant quota, you need to set <literal>quota_driver</literal> in
|
||||
<literal>neutron.conf</literal>. For example:</para>
|
||||
<programlisting language="ini">quota_driver = neutron.db.quota_db.DbQuotaDriver</programlisting>
|
||||
<para> When per-tenant quota is enabled, the output of the following commands contain
|
||||
<literal>quotas</literal>. </para>
|
||||
<para>When per-tenant quota is enabled, the output of the following commands contain
|
||||
<literal>quotas</literal>.</para>
|
||||
<screen><prompt>$</prompt> <userinput>neutron ext-list -c alias -c name</userinput>
|
||||
<computeroutput>+-----------------+--------------------------+
|
||||
| alias | name |
|
||||
@@ -264,7 +264,7 @@ quota_security_group_rule = 100</programlisting>
|
||||
Linux Bridge, and Nicira NVP are known to work but new versions of other plugins may
|
||||
bring additional functionality - consult the documentation for each plugin.
|
||||
</para></note>
|
||||
<para> There are four CLI commands to manage per-tenant quotas: <itemizedlist>
|
||||
<para>There are four CLI commands to manage per-tenant quotas:<itemizedlist>
|
||||
<listitem>
|
||||
<para><command>neutron quota-delete</command> - Delete defined quotas of a given
|
||||
tenant.</para>
|
||||
@@ -281,7 +281,7 @@ quota_security_group_rule = 100</programlisting>
|
||||
</listitem>
|
||||
</itemizedlist>Only users with 'admin' role can change a quota value. Note that the default
|
||||
set of quotas are enforced for all tenants by default, so there is no
|
||||
<literal>quota-create</literal> command. </para>
|
||||
<literal>quota-create</literal> command.</para>
|
||||
<para>
|
||||
<literal>quota-list</literal> displays a list of tenants for which per-tenant quota is enabled.
|
||||
The tenants who have the default set of quota limits are not listed.
|
||||
|
@@ -49,7 +49,7 @@
|
||||
running, and no service restart is required. That is to say,
|
||||
every time the policy file is updated, the policies will be
|
||||
automatically reloaded. Currently the only way of updating
|
||||
such policies is to edit the policy file. </para>
|
||||
such policies is to edit the policy file.</para>
|
||||
<para>In this section, the terms "policy" and "rule" both refer to
|
||||
objects that are specified in the same way in the policy file;
|
||||
there are no syntax differences between a rule and a policy. A
|
||||
|
@@ -37,7 +37,7 @@
|
||||
<glossterm>access control list</glossterm>
|
||||
<glossdef>
|
||||
<para>A list of permissions attached to an object. An ACL specifies which users or system processes have access to objects. It also
|
||||
defines which operations can be performed on specified objects.
|
||||
defines which operations can be performed on specified objects.
|
||||
Each entry in a typical ACL specifies a subject and an operation. For instance, ACL entry, <code>(Alice, delete)</code>, for a file gives Alice permission to delete the file.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@@ -1001,7 +1001,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>Compute API</glossterm>
|
||||
<glossdef>
|
||||
<para>The <systemitem class="service">nova-api</systemitem>
|
||||
<para>The <systemitem class="service">nova-api</systemitem>
|
||||
daemon that provides
|
||||
access to nova services. Can communicate with
|
||||
other APIs, such as the Amazon EC2 API.</para>
|
||||
@@ -2149,7 +2149,7 @@ daemon that provides
|
||||
<glossentry>
|
||||
<glossterm>HTTPS</glossterm>
|
||||
<glossdef>
|
||||
<para> Hypertext Transfer Protocol Secure (HTTPS) is a
|
||||
<para>Hypertext Transfer Protocol Secure (HTTPS) is a
|
||||
communications protocol for secure communication
|
||||
over a computer network, with especially wide
|
||||
deployment on the Internet. Technically, it is not
|
||||
|
@@ -247,7 +247,7 @@
|
||||
for the user.</para>
|
||||
<para>The dashboard assigns an ID to the user, and the
|
||||
user appears in the <guilabel>Users</guilabel>
|
||||
category. </para>
|
||||
category.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</section>
|
||||
|
@@ -25,7 +25,7 @@
|
||||
</step>
|
||||
<step>
|
||||
<para>Click the <guilabel>Services</guilabel> tab to view
|
||||
services information. </para>
|
||||
services information.</para>
|
||||
<para>The page shows the internal name and the public OpenStack
|
||||
name for the service, the host where the service runs, and
|
||||
whether the service is or is not enabled.</para>
|
||||
|
@@ -88,7 +88,8 @@
|
||||
<para>You can create and manage flavors with the nova
|
||||
<command>flavor-*</command> commands provided by the
|
||||
<filename>python-novaclient</filename> package.</para>
|
||||
<section xml:id="cli_create_flavor"><title>Create flavors</title><procedure>
|
||||
<section xml:id="cli_create_flavor"><title>Create flavors</title>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>List flavors to show the ID and name,
|
||||
the amount of memory, the amount of disk space
|
||||
@@ -96,16 +97,16 @@
|
||||
partition, the swap, and the number of virtual
|
||||
CPUs for each flavor.</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova flavor-list</userinput></screen>
|
||||
</step>
|
||||
</step>
|
||||
<step>
|
||||
<para>If the flavor you want does not exist, you can create a flavor.</para>
|
||||
<para>When you create a flavor, you must specify
|
||||
the flavor name, ID, RAM size, disk size, and the
|
||||
number of VCPUs. </para>
|
||||
number of VCPUs.</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova flavor-create <replaceable>FLAVOR_NAME</replaceable> <replaceable>FLAVOR_ID</replaceable> <replaceable>RAM_IN_MB ROOT_DISK_IN_GB</replaceable> <replaceable>NUMBER_OF_VCPUS</replaceable></userinput></screen>
|
||||
<para>For a list of optional parameters, run the following command:</para> <screen><prompt>$</prompt> <userinput>nova help flavor-create</userinput></screen></step>
|
||||
</procedure></section>
|
||||
<section xml:id="cli_delete_flavor"><title>Delete a flavor</title><procedure>
|
||||
<section xml:id="cli_delete_flavor"><title>Delete a flavor</title><procedure>
|
||||
<step>
|
||||
<para>Delete a specified flavor, as follows:</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova flavor-delete <replaceable>FLAVOR_ID</replaceable></userinput></screen>
|
||||
|
@@ -1,5 +1,5 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section
|
||||
<section
|
||||
xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
||||
|
@@ -17,7 +17,7 @@
|
||||
volume to a running instance or detach a volume and attach it
|
||||
to another instance at any time. You can also create a
|
||||
snapshot from or delete a volume. Only administrative users
|
||||
can create volume types. </para>
|
||||
can create volume types.</para>
|
||||
<section xml:id="dashboard_create_volumes">
|
||||
<title>Create a volume</title>
|
||||
<procedure>
|
||||
|
@@ -1,5 +1,5 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section
|
||||
<section
|
||||
xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
|
Reference in New Issue
Block a user