Update openstack_architecture_model.md

Fix formatting
This commit is contained in:
Oleg 2013-10-21 09:40:10 +00:00
parent d1f5ce80ae
commit 6ff7430718

View File

@ -1,54 +1,64 @@
== Architecture Data Model == Architecture Data Model
=== Overview === =======================
Overview
--------
We want to introduce unified data structure which contains all information We want to introduce unified data structure which contains all information
necessary to inspect, analyze, describe and visualize OpenStack architecture. necessary to inspect, analyze, describe and visualize OpenStack architecture.
Architecture data model serves multiple actual and potential use cases. Architecture data model serves multiple actual and potential use cases.
==== Diagnostics ==== Diagnostics
-----------
Architecture data model provides necessary data for the configuration analysis Architecture data model provides necessary data for the configuration analysis
and diagnostics tool ('''Rubick'''). and diagnostics tool ('''Rubick''').
==== Deployment ==== Deployment
----------
Arhictecture data model must include all information necessary to deployment Arhictecture data model must include all information necessary to deployment
systems (e.g. **Fuel** or **TripleO**). We will implement simple conversion systems (e.g. **Fuel** or **TripleO**). We will implement simple conversion
tools which will allow to configure these deployment systems and effectively tools which will allow to configure these deployment systems and effectively
support 'portable' clouds. support 'portable' clouds.
==== Benchmarking ==== Benchmarking
------------
This model could be reused by '''Rally''' project to compare benchmarking This model could be reused by '''Rally''' project to compare benchmarking
results for different architectures. Definitions of architectures must be results for different architectures. Definitions of architectures must be
comparable and portable, which is exactly what architecture model aimed to comparable and portable, which is exactly what architecture model aimed to
solve. solve.
==== Upgrade ==== Upgrade
-------
Upgrade system could potentially utilize the model just in the way the Upgrade system could potentially utilize the model just in the way the
Deployment systems do. In addition, existing clouds could be inspected and Deployment systems do. In addition, existing clouds could be inspected and
described for subsequent upgrade using this model. described for subsequent upgrade using this model.
==== Support ==== Tech Support
------------
The model suits as base for questionaire to assess existing installations for The model suits as base for questionaire to assess existing installations for
support contract pricing purposes. support contract pricing purposes.
==== Hardening ==== Hardening
---------
The model could be used to perform automated/guided hardening of OpenStack The model could be used to perform automated/guided hardening of OpenStack
architecture and configuration. This is achieved through use of 'best practice' architecture and configuration. This is achieved through use of 'best practice'
rulesets for the inspection of cloud. rulesets for the inspection of cloud.
==== Expert system ==== Expert system
-------------
The model could be used as a part of production rules system capable of The model could be used as a part of production rules system capable of
automated reporting and handling of operational errors, based on combination of automated reporting and handling of operational errors, based on combination of
'base' status of the cloud, logging messages and notifications. 'base' status of the cloud, logging messages and notifications.
=== Data Format === Data Format
-----------
This section proposes data model format which allows to describe an OpenStack This section proposes data model format which allows to describe an OpenStack
installation. The model includes data regarding physical infrastructure, logical installation. The model includes data regarding physical infrastructure, logical