openstack/openstack-manuals
Code Issues Proposed changes

Removed instances of 'it is recommended'

Browse Source 
Replaced instances of 'it is recommended' with
'we recommend'

Change-Id: I1e630a3f6b066ca3f3800839f4267c99af7026a7
Closes-bug: #1374813
This commit is contained in:
Alexandra Settle
2014-12-08 15:00:55 +10:00
parent 4258867f0a
commit c76361ceb6
7 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/arch-design/ch_network_focus.xml
View File

@@ -62,8 +62,8 @@
<term>Web portals or web services</term>
<listitem>
<para>Web servers are a common
application for cloud services and it is recommended
to have an understanding of the network requirements.
application for cloud services and we recommend
an understanding of the network requirements.
The network will need to be able to scale out to meet
user demand and deliver webpages with a minimum of
latency. Internal east-west and north-south network

4
doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml
View File

@@ -32,7 +32,7 @@
OpenStack cloud.</para>
<section xml:id="designing-compute-resources-tech-considerations">
<title>Designing compute resources</title>
<para>It is recommended to design compute resources as pools of
<para>We recommend you design compute resources as pools of
resources which will be addressed on-demand. When designing
compute resource pools, a number of factors impact your design
decisions. For example, decisions related to processors,
@@ -41,7 +41,7 @@
necessary to decide whether compute resources will be provided
in a single pool or in multiple pools.</para>
<para>To design for the best use of available resources by
applications running in the cloud, it is recommended to design
applications running in the cloud, we recommend you design
more than one compute resource pool. Each independent resource
pool should be designed to provide service for specific
flavors of instances or groupings of flavors. For the purpose

4
doc/arch-design/multi_site/section_architecture_multi_site.xml
View File

@@ -104,8 +104,8 @@
dependent on a number of factors. One major dependency to consider
is storage. When designing the storage system, the storage mechanism
needs to be determined. Once the storage type is determined, how it
will be accessed is critical. For example, it is recommended that
storage should utilize a dedicated network. Another concern is how
will be accessed is critical. For example, we recommend that
storage should use a dedicated network. Another concern is how
the storage is configured to protect the data. For example, the
recovery point objective (RPO) and the recovery time objective
(RTO). How quickly can the recovery from a fault be completed, will

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

@@ -184,7 +184,7 @@
<listitem>
<para>Ensure determination of the method for resuming
proper operations of a site when it comes back online
after a disaster. It is recommended to architect the
after a disaster. We recommend you architect the
recovery to avoid race conditions.</para>
</listitem>
</itemizedlist></section>

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

@@ -68,7 +68,7 @@
network resource defined in templates to map to tenant
networks and for port creation, as well as allocating floating
IPs. If there is a requirement to define and manage network
resources in using orchestration, it is recommended that the
resources in using orchestration, we recommend that the
design include the Orchestration module to meet the demands of
users.</para>
<section xml:id="design-impacts">

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

@@ -121,7 +121,7 @@
is selected it is important to determine how the
hypervisors will connect to the storage array.
Connectivity can affect latency and thus performance.
It is recommended to check that the network
We recommended you check that the network
characteristics will minimize latency to boost the
overall performance of the design.</para>
</listitem>

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

@@ -104,7 +104,7 @@
solutions in the cloud, design the application to be aware of
the underlying storage subsystem and the features available.
As an example, when creating an application that requires
replication, it is recommended that the application can detect
replication, we recommend that the application be designed to detect
whether replication is a feature natively available in the
storage subsystem. In the event that replication is not
available, the application can be designed to react in a
@@ -128,7 +128,7 @@
are designed to provide fault tolerance at the hardware
level.</para>
<para>In cases where applications require extreme performance out
of block storage devices, it is recommended to deploy high
of block storage devices, we recommend you deploy high
performing storage solutions such as SSD disk drives or flash
storage systems. When considering these solutions, it is
important to consider the availability of software and support
@@ -204,7 +204,7 @@
data stored on the object nodes. Object proxies in each region
should leverage local read and write affinity so that access
to objects is facilitated by local storage resources wherever
possible. It is recommended that upstream load balancing be
possible. We recommend that upstream load balancing be
deployed to ensure that proxy services can be distributed
across the multiple zones and, in some cases, it may be
necessary to make use of third party solutions to aid with