openstack/openstack-manuals
Code Issues Proposed changes

Merge "Fix five typos on cloud administrator guide"

Browse Source
This commit is contained in:
Jenkins 2015-07-24 14:09:20 +00:00 committed by Gerrit Code Review
commit 76d6867a6f
8 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/admin-guide-cloud-rst/source/blockstorage-driver-filter-weighing.rst
View File

@ -22,7 +22,7 @@ property to determine the best back end, but that is not always perfect.
If a back end has the ability to provide a more accurate back-end
specific value you can use that as part of the weighing. Another example
of when the driver filter and weigher can prove useful is if a back end
exists where there is a hard limit of 1000 volumes. The maxmimum volume
exists where there is a hard limit of 1000 volumes. The maximum volume
size is 500 GB. Once 75% of the total space is occupied the performance
of the back end degrades. The driver filter and weigher can provide a
way for these limits to be checked for.
@ -338,7 +338,7 @@ properties::
goodness_function = "55"
The above is an example of how back-end specific properties can be used
in the fitler and goodness functions. In this example the LVM driver's
in the filter and goodness functions. In this example the LVM driver's
``total\_volumes`` capability is being used to determine which host gets
used during a volume request. In the above example, lvm-1 and lvm-2 will
handle volume requests for all volumes with a size less than 5 GB. The

2
doc/admin-guide-cloud-rst/source/networking_config-plugins.rst
View File

@ -154,7 +154,7 @@ formerly known as Nicira NVP.
when a tenant creates a network. You can get this value from the
Transport Zones page for the NSX-mh manager:
Alternatively the transport zone identfier can be retrieved by query
Alternatively the transport zone identifier can be retrieved by query
the NSX-mh API: ``/ws.v1/transport-zone``
.. code:: ini

2
doc/admin-guide-cloud-rst/source/objectstorage_components.rst
View File

@ -130,7 +130,7 @@ outages of storage servers without losing all replicas of the data.
As mentioned earlier, everything in Object Storage is stored, by
default, three times. Swift will place each replica
"as-uniquely-as-possible" to ensure both high availability and high
durability. This means that when chosing a replica location, Object
durability. This means that when choosing a replica location, Object
Storage chooses a server in an unused zone before an unused server in a
zone that already has a replica of the data.

4
doc/admin-guide-cloud/blockstorage/section_driver_filter_weighing.xml
View File

@ -41,7 +41,7 @@
Another example of when the driver filter and weigher can
prove useful is if a back end exists where there is a hard
limit of 1000 volumes. The maxmimum volume size is
limit of 1000 volumes. The maximum volume size is
500 GB. Once 75% of the total space is occupied the
performance of the back end degrades. The driver filter and
weigher can provide a way for these limits to be checked
@ -498,7 +498,7 @@ goodness_function = "55"</programlisting>
<para>
The above is an example of how back-end specific properties
can be used in the fitler and goodness functions. In this
can be used in the filter and goodness functions. In this
example the LVM driver's 'total_volumes' capability is being
used to determine which host gets used during a volume
request.

2
doc/admin-guide-cloud/networking/section_networking_adv_features.xml
View File

@ -392,7 +392,7 @@
<para>When a port is created in Networking it is associated with a security group. If a
security group is not specified the port is associated with a 'default' security group.
By default, this group drops all ingress traffic and allows all egress. Rules can be
added to this group in order to change the behaviour.</para>
added to this group in order to change the behavior.</para>
<para>To use the Compute security group APIs or use Compute to orchestrate the creation of
ports for instances on specific security groups, you must complete additional
configuration. You must configure the <filename>/etc/nova/nova.conf</filename> file and

2
doc/admin-guide-cloud/networking/section_networking_config-plugins.xml
View File

@ -129,7 +129,7 @@ nsx_controllers = <replaceable>API_ENDPOINT_LIST</replaceable> # comma-separated
<para>The UUID of the NSX-mh transport zone that should be used by default when
a tenant creates a network. You can get this value from the
<guilabel>Transport Zones</guilabel> page for the NSX-mh manager:</para>
<para>Alternatively the transport zone identfier can be retrieved by query the NSX-mh
<para>Alternatively the transport zone identifier can be retrieved by query the NSX-mh
API: <literal>/ws.v1/transport-zone</literal></para>
<programlisting language="ini">default_tz_uuid = <replaceable>TRANSPORT_ZONE_UUID</replaceable></programlisting>
</listitem>

2
doc/common/section_objectstorage-components.xml
View File

@ -119,7 +119,7 @@
losing all replicas of the data.</para>
<para>As mentioned earlier, everything in Object Storage is stored, by default, three
times. Swift will place each replica "as-uniquely-as-possible" to ensure both high
availability and high durability. This means that when chosing a replica location,
availability and high durability. This means that when choosing a replica location,
Object Storage chooses a server in an unused zone before an unused server in a zone that
already has a replica of the data.</para>
<figure>

2
doc/networking-guide/source/intro_os_networking_overview.rst
View File

@ -143,7 +143,7 @@ security group rules. When a port is created in Networking it is associated
with a security group. If a security group is not specified the port is
associated with a 'default' security group. By default, this group drops all
ingress traffic and allows all egress. Rules can be added to this group in
order to change the behaviour.
order to change the behavior.
Extensions
----------