openstack/openstack-manuals
Code Issues Proposed changes

Arch Design: Do not abbreviate OS in headings

Browse Source 
Use 'operating system' in a consistent way in titles and remove the only
two usages of OS.

Change-Id: I5cbb6b6223820eedfdb8042dce14b2f439fc7d1c
This commit is contained in:
Andreas Jaeger 2014-07-25 17:24:36 +02:00
parent 133a5288d6
commit 7183f743a7
2 changed files with 29 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/arch-design/compute_focus/section_architecture_compute_focus.xml
View File

@ -535,28 +535,22 @@
</para>
</section>
<section xml:id="os-and-hypervisor-arch">
<title>OS and hypervisor</title>
<para>The selection of OS and hypervisor has a significant impact
on
the end point design. Selecting a particular operating
system and
hypervisor could affect server hardware selection.
For example, a
selected combination needs to be supported on
the selected hardware.
Ensuring the storage hardware selection
and topology supports the
selected operating system and
hypervisor combination should also be
considered.
Additionally, make sure that the networking hardware
selection
and topology will work with the chosen operating system and
hypervisor combination. For example, if the design uses Link
Aggregation Control Protocol (LACP), the hypervisor needs to
support
it.
</para>
<title>Operating system and hypervisor</title>
<para>
The selection of operating system (OS) and hypervisor has
a significant impact on the end point design. Selecting a
particular operating system and hypervisor could affect
server hardware selection. For example, a selected
combination needs to be supported on the selected
hardware. Ensuring the storage hardware selection and
topology supports the selected operating system and
hypervisor combination should also be considered.
Additionally, make sure that the networking hardware
selection and topology will work with the chosen operating
system and hypervisor combination. For example, if the
design uses Link Aggregation Control Protocol (LACP), the
hypervisor needs to support it.
</para>
<para>Some areas that could be impacted by the selection of OS and
hypervisor include:
</para>

25
doc/arch-design/generalpurpose/section_architecture_general_purpose.xml
View File

@ -520,18 +520,19 @@
</itemizedlist>
</section>
<section xml:id="os-and-hypervisor">
<title>OS and hypervisor</title>
<para>The selection of OS and hypervisor has a tremendous impact
on the overall design. Selecting a particular operating system
and hypervisor can also directly affect server hardware
selection. It is recommended to make sure the storage hardware
selection and topology support the selected operating system
and hypervisor combination. Finally, it is important to ensure
that the networking hardware selection and topology will work
with the chosen operating system and hypervisor combination.
For example, if the design uses Link Aggregation Control
Protocol (LACP), the OS and hypervisor both need to support
it.</para>
<title>Operating system and hypervisor</title>
<para>
The selection of operating system (OS) and hypervisor has a
tremendous impact on the overall design. Selecting a particular
operating system and hypervisor can also directly affect server
hardware selection. It is recommended to make sure the storage
hardware selection and topology support the selected operating
system and hypervisor combination. Finally, it is important to
ensure that the networking hardware selection and topology will
work with the chosen operating system and hypervisor
combination. For example, if the design uses Link Aggregation
Control Protocol (LACP), the OS and hypervisor both need to
support it.</para>
<para>Some areas that could be impacted by the selection of OS and
hypervisor include:</para>
<itemizedlist>