openstack/openstack-manuals
Code Issues Proposed changes

Merge "Add missing new lines at end of file"

Browse Source
This commit is contained in:
Jenkins 2014-07-24 18:37:34 +00:00 committed by Gerrit Code Review
commit 817f8da627
22 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design/ch_references.xml
View File

@ -74,4 +74,4 @@
program aimed at installing, upgrading and operating OpenStack
clouds using OpenStack's own cloud facilities as the
foundation.</para>
</chapter>
</chapter>

2
doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml
View File

@ -114,4 +114,4 @@
compute-focused OpenStack design architecture, increasing the
CPU overcommit ratio increases the potential for noisy
neighbor issues and is not recommended.</para></section>
</section>
</section>

2
doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml
View File

@ -141,4 +141,4 @@
is similar to the requirements for the general-purpose cloud.
More details on operational requirements can be found in the
general-purpose design section.</para></section>
</section>
</section>

2
doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml
View File

@ -140,4 +140,4 @@
<para>For a deeper discussion on many of these topics, refer to
the OpenStack Operations Guide at
http://docs.openstack.org/ops.</para></section>
</section>
</section>

2
doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml
View File

@ -172,4 +172,4 @@
appropriate choice.</para>
</listitem>
</itemizedlist></section>
</section>
</section>

2
doc/arch-design/hybrid/section_operational_considerations_hybrid.xml
View File

@ -96,4 +96,4 @@
however, provide agility for these situations by allowing the
migration of workloads to alternative clouds in response to
cloud-specific issues.</para></section>
</section>
</section>

2
doc/arch-design/introduction/section_how_this_book_is_organized.xml
View File

@ -94,4 +94,4 @@
</itemizedlist>
<para>A Glossary covers the terms and phrases used in the
book.</para>
</section>
</section>

2
doc/arch-design/introduction/section_intended_audience.xml
View File

@ -14,4 +14,4 @@
and principles, experience in enterprise system design, Linux
and virtualization experience, and a basic understanding of
networking principles and protocols.</para>
</section>
</section>

2
doc/arch-design/introduction/section_introduction_to_openstack_architecture_design_guide.xml
View File

@ -30,4 +30,4 @@
advice to help an organization to design and build a
well-architected OpenStack cloud that will fit its unique
requirements.</para>
</section>
</section>

2
doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml
View File

@ -124,4 +124,4 @@
/>
</imageobject>
</mediaobject></section>
</section>
</section>

2
doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml
View File

@ -170,4 +170,4 @@
massively scalable OpenStack cloud.</para>
</listitem>
</itemizedlist></section>
</section>
</section>

2
doc/arch-design/multi_site/section_operational_considerations_multi_site.xml
View File

@ -175,4 +175,4 @@
instances in another. Documenting specific examples will help
users understand how to operate the cloud, thereby reducing
calls and tickets filed with the help desk.</para></section>
</section>
</section>

2
doc/arch-design/multi_site/section_tech_considerations_multi_site.xml
View File

@ -193,4 +193,4 @@
requires an equally balanced number of nodes across sites, the
same heat template can be used to cover each site with small
alterations to only the region name.</para></section>
</section>
</section>

2
doc/arch-design/multi_site/section_user_requirements_multi_site.xml
View File

@ -210,4 +210,4 @@
continuous operation. Authentication server locality is also
something that might be needed as well and should be planned
for.</para></section>
</section>
</section>

2
doc/arch-design/network_focus/section_operational_considerations_network_focus.xml
View File

@ -69,4 +69,4 @@
that fails over to one link overwhelms that link and then
moves to the subsequent links until the all network traffic
stops.</para>
</section>
</section>

2
doc/arch-design/specialized/section_introduction_specialized.xml
View File

@ -46,4 +46,4 @@
environment.</para>
</listitem>
</itemizedlist>
</section>
</section>

2
doc/arch-design/specialized/section_networking_specialized.xml
View File

@ -31,4 +31,4 @@
system. Avoid using layer 3 plug-ins as they will divide the
broadcast domain and prevent router adjacencies from
forming.</para></section>
</section>
</section>

2
doc/arch-design/storage_focus/section_architecture_storage_focus.xml
View File

@ -564,4 +564,4 @@
components might require it depending on the specific
implementation.</para>
</listitem>
</itemizedlist></section></section>
</itemizedlist></section></section>

2
doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml
View File

@ -286,4 +286,4 @@
nodes will be required. For this reason, the network
architecture used for access to storage nodes and proxy
servers should make use of a design which is scalable.</para></section>
</section>
</section>

2
doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml
View File

@ -86,4 +86,4 @@
industry standard core. One way of accomplishing this might be
through the use of different back ends serving different use
cases.</para>
</section>
</section>

2
doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml
View File

@ -92,4 +92,4 @@
transit and at rest.</para>
</listitem>
</itemizedlist></section>
</section>
</section>

2
doc/common/section_compute_config-firewalls.xml
View File

@ -45,4 +45,4 @@
</procedure>
<para>The <systemitem>iptables</systemitem> firewall now enables incoming connections to the
Compute services. Repeat this process for each Compute service node.</para>
</section>
</section>