openstack/openstack-manuals
Code Issues Proposed changes

Merge "made change to section_architecture_compute_focus"

Browse Source
This commit is contained in:
Jenkins 2015-01-31 13:14:26 +00:00 committed by Gerrit Code Review
commit 228a22f490
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -514,10 +514,10 @@
constrain the functionality of other components. If a design opts to
include the Orchestration module but excludes the Telemetry module, then
the design will not be able to take advantage of Orchestration's auto
scaling functionality (which relies on information from Telemetry). Due
scaling functionality (which relies on information from Telemetry). This is due
to the fact that you can use Orchestration to spin up a large number of
instances to perform the compute-intensive processing, including
Orchestration in a compute-focused architecture design is strongly
instances to perform the compute-intensive processing. This includes
Orchestration in a compute-focused architecture design, which is strongly
recommended.</para>
</section>
<section xml:id="supplemental-software">
@ -590,7 +590,7 @@
to any database that is supported by the SQLAlchemy Python drivers,
however most common database deployments make use of MySQL or some
variation of it. We recommend that the database which provides
back-end service within a general purpose cloud be made highly
back-end services within a general-purpose cloud, be made highly
available using an available technology which can accomplish that
goal. Some of the more common software solutions used include Galera,
MariaDB and MySQL with multi-master replication.</para>