openstack/openstack-manuals
Code Issues Proposed changes

changes to section_operational_considerations_general_purpose

Browse Source 
platorms should be platforms
added re-spawning hyphen

Change-Id: I40c74918b2b70f3ce018c5eeb617146ac8b1b5af
This commit is contained in:
Shilla Saebi 2014-12-22 15:59:25 -05:00 committed by Anne Gentle
parent b662901f6e
commit 1073499632
1 changed files with 2 additions and 2 deletions

4
doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml

@ -54,7 +54,7 @@
</section>
<section xml:id="monitoring-general-purpose">
<title>Monitoring</title>
<para>OpenStack clouds require appropriate monitoring platorms to
<para>OpenStack clouds require appropriate monitoring platforms to
ensure errors are caught and managed appropriately. Specific
metrics that are critically important to monitor include:</para>
<itemizedlist>
@ -95,7 +95,7 @@
for high availability (HA) can have cost ramifications.</para>
<para>For example, if a compute host failed, this would be an operational
consideration; requiring the restoration of instances from a
snapshot or respawning an instance. The overall application design
snapshot or re-spawning an instance. The overall application design
is impacted, general purpose clouds should not need to provide
abilities to migrate instances from one host to another. Additional
considerations need to be made around supporting instance migration if