change to section_architecture_general_purpose
changed sevices to services (typo) technicalrequirements - added space loggin changed to logging Logstach should be Logstash Change-Id: I9f2d9c352d92e46c58125ad384222eb2fbfd2dd2
This commit is contained in:
parent
14903f4e5e
commit
06ee449093
@ -394,7 +394,7 @@
|
||||
to be fast performing disks. We recommend that object storage
|
||||
nodes take advantage of the best cost per terabyte available
|
||||
for storage. Contrastingly, disks chosen for block storage
|
||||
sevices should take advantage of performance boosting
|
||||
services should take advantage of performance boosting
|
||||
features that may entail the use of SSDs or flash storage
|
||||
to provide high performance block storage pools. Storage
|
||||
performance of ephemeral disks used for instances should
|
||||
@ -678,7 +678,7 @@
|
||||
Orchestration but excludes Telemetry, then the design will not be able
|
||||
to take advantage of Orchestrations' auto scaling functionality.
|
||||
It is important to research the component interdependencies
|
||||
in conjunction with the technicalrequirements before deciding
|
||||
in conjunction with the technical requirements before deciding
|
||||
on the final architecture.</para>
|
||||
<section xml:id="supplemental-components">
|
||||
<title>Supplemental components</title>
|
||||
@ -743,7 +743,7 @@
|
||||
<para>Requirements for logging, monitoring, and alerting are
|
||||
determined by operational considerations. Each of these
|
||||
sub-categories includes a number of various options. For example,
|
||||
in the loggin sub-category one might consider Logstach, Splunk, instanceware
|
||||
in the logging sub-category one might consider Logstash, Splunk, instanceware
|
||||
Log Insight, or some other log aggregation-consolidation tool. Logs
|
||||
should be stored in a centralized location to make it easier to perform
|
||||
analytics against the data. Log data analytics
|
||||
|
Loading…
Reference in New Issue
Block a user