openstack/openstack-manuals
Code Issues Proposed changes

Don't use — entity

Browse Source 
The rendering is broken with our tools (html and pdf output), and can be esaily
replaced.

Change-Id: Icf2279da8d77a933cd2cc7ad80f0c7ba1098398b
backport: none
This commit is contained in:
Gauvain Pocentek 2014-02-15 17:12:57 +01:00
parent 254befa482
commit 15bc79ea8f
5 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/admin-guide-cloud/section_networking-multi-dhcp-agents.xml
View File

@ -70,7 +70,7 @@
<section xml:id="multi_agent_demo_configuration">
<title>Configuration</title>
<procedure>
<title>controlnode&#151;Neutron Server</title>
<title>controlnode: Neutron Server</title>
<step>
<para>Neutron configuration file
<filename>/etc/neutron/neutron.conf</filename>:</para>
@ -95,7 +95,7 @@ physical_interface_mappings = physnet1:eth0</programlisting>
</step>
</procedure>
<procedure>
<title>HostA and HostB&#151;L2 Agent</title>
<title>HostA and HostB: L2 Agent</title>
<step>
<para>Neutron configuration file
<filename>/etc/neutron/neutron.conf</filename>:</para>
@ -133,7 +133,7 @@ firewall_driver=nova.virt.firewall.NoopFirewallDriver</programlisting>
</step>
</procedure>
<procedure>
<title>HostA and HostB&#151;DHCP Agent</title>
<title>HostA and HostB: DHCP Agent</title>
<step>
<para>Update the DHCP configuration file
<filename>/etc/neutron/dhcp_agent.ini</filename>:</para>

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

@ -12,7 +12,7 @@
system's central hub. The access tier fields the incoming API requests from clients and
moves data in and out of the system. This tier consists of front-end load balancers,
ssl-terminators, and authentication services. It runs the (distributed) brain of the
Object Storage system&#151;the proxy server processes.</para>
Object Storage system: the proxy server processes.</para>
<figure>
<title>Object Storage architecture</title>
<mediaobject>

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

@ -10,29 +10,29 @@
durability, and high concurrency are:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">Proxy servers&#151;</emphasis>Handle all of the incoming
<para><emphasis role="bold">Proxy servers.</emphasis> Handle all of the incoming
API requests.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Rings&#151;</emphasis>Map logical names of data to
<para><emphasis role="bold">Rings.</emphasis> Map logical names of data to
locations on particular disks.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Zones&#151;</emphasis>Isolate data from other zones. A
<para><emphasis role="bold">Zones.</emphasis> Isolate data from other zones. A
failure in one zone doesn’t impact the rest of the cluster because data is
replicated across zones.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Accounts and containers&#151;</emphasis>Each account and
<para><emphasis role="bold">Accounts and containers.</emphasis> Each account and
container are individual databases that are distributed across the cluster. An
account database contains the list of containers in that account. A container
database contains the list of objects in that container.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Objects&#151;</emphasis>The data itself.</para>
<para><emphasis role="bold">Objects.</emphasis> The data itself.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Partitions&#151;</emphasis>A partition stores objects,
<para><emphasis role="bold">Partitions.</emphasis> A partition stores objects,
account databases, and container databases and helps manage locations where data
lives in the cluster.</para>
</listitem>

10
doc/common/section_objectstorage-features.xml
View File

@ -38,7 +38,7 @@
<td rowspan="1" colspan="1"><emphasis role="bold"
>Multi-dimensional scalability</emphasis>
</td>
<td rowspan="1" colspan="1">Scale-out architecture&#151;Scale vertically and
<td rowspan="1" colspan="1">Scale-out architecture: Scale vertically and
horizontally-distributed storage Backs up and archives large amounts of data
with linear performance</td>
</tr>
@ -46,7 +46,7 @@
<td rowspan="1" colspan="1"><emphasis role="bold">Account/container/object
structure</emphasis></td>
<td rowspan="1" colspan="1">No nesting, not a traditional file
system&#151;Optimized for scale, it scales to multiple petabytes and
system: Optimized for scale, it scales to multiple petabytes and
billions of objects</td>
</tr>
<tr>
@ -82,9 +82,9 @@
<td rowspan="1" colspan="1"><emphasis role="bold"
>Built-in management
utilities</emphasis></td>
<td rowspan="1" colspan="1">Account management&#151;Create, add, verify, and
delete users; Container management&#151;Upload, download, and verify;
Monitoring&#151;Capacity, host, network, log trawling, and cluster
<td rowspan="1" colspan="1">Account management: Create, add, verify, and
delete users; Container management: Upload, download, and verify;
Monitoring: Capacity, host, network, log trawling, and cluster
health</td>
</tr>
<tr>

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

@ -58,7 +58,7 @@
construct a builder file that is pretty close to the one you have lost. The
following is what you will need to do.</para>
<warning>
<para>This procedure is a last-resort for emergency circumstances&#151;it
<para>This procedure is a last-resort for emergency circumstances. It
requires knowledge of the swift python code and may not succeed.</para>
</warning>
<para>First, load the ring and a new ringbuilder object in a Python REPL:</para>