stackforge/rubick
Code Issues Proposed changes

[doc] Modify Summary section in project proposal document

Browse Source 
Add description of checks of system status as rules of diagnostic system
This commit is contained in:
Oleg Gelbukh 2013-10-16 13:48:10 +00:00
parent 1a0f1cb99f
commit 4a6163c2d1
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/openstack_diagnostics_proposal.rst
View File

@ -15,10 +15,20 @@ OpenStack cloud operators usually rely on deploymnet tools to configure all the
platform components correctly and efficiently upfront. However, after initial platform components correctly and efficiently upfront. However, after initial
deployment platform configurations and operational conditions start to change. deployment platform configurations and operational conditions start to change.
These changes could break consistency and integration of cloud platform and its These changes could break consistency and integration of cloud platform and its
components. components, and ultimately cause cloud service failures of different kinds.
Cloud operator must quickly and efficiently identify and respond to the root
cause of such failures. To do so, he must check if his OpenStack configuration
is sane and consistent. These checks could be thought of as rules of diagnostic
production system.
Currently OpenStack ecosystem does not provide tools which specifically help to
diagnose platform configuration. We propose a project which will help operators
to diagnose their OpenStack platform and reduce response time to known and
unknown failures.
Mission Mission
--------- -------
Diagnostics' mission is to **provide OpenStack cloud operators with tools which Diagnostics' mission is to **provide OpenStack cloud operators with tools which
minimize time and effort needed to identify and fix errors in operations minimize time and effort needed to identify and fix errors in operations