[doc] Add proposal document and update architecture model
This commit is contained in:
parent
d1997d616b
commit
c682a0f2cf
@ -2,16 +2,20 @@
|
|||||||
ARCHITECTURE DATA MODEL
|
ARCHITECTURE DATA MODEL
|
||||||
=======================
|
=======================
|
||||||
|
|
||||||
--------
|
|
||||||
Overview
|
Overview
|
||||||
--------
|
--------
|
||||||
|
|
||||||
Architecture data model produced by Joker could be consumed by configuration
|
We want to introduce unified data structure which contains all information
|
||||||
validator tool (Dark Knight), by architecture graph (Stencil) and others.
|
necessary to inspect, analyze, describe and visualize OpenStack architecture.
|
||||||
|
|
||||||
At some point it should be made convertible into format accepted by deployment
|
This Architecture data model could be consumed and processed by configuration
|
||||||
systems (e.g. Fuel or TripleO) which will allow to effectively 'clone' OpenStack
|
analysis and diagnostics tool (**Dark Knight**) and by architecture visualizer
|
||||||
clouds using different deployment applications.
|
(**Stencil**).
|
||||||
|
|
||||||
|
Arhictecture data model must include all information necessary to deployment
|
||||||
|
systems (e.g. **Fuel** or **TripleO**). We will implement simple conversion tools which
|
||||||
|
will allow to configure these deployment systems and effectively support
|
||||||
|
'portable' clouds.
|
||||||
|
|
||||||
This model could be reused by Rally project to compare benchmarking results for
|
This model could be reused by Rally project to compare benchmarking results for
|
||||||
different architectures.
|
different architectures.
|
||||||
@ -24,11 +28,10 @@ support contract pricing purposes.
|
|||||||
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.
|
architecture and configuration.
|
||||||
|
|
||||||
-----------
|
|
||||||
Data Format
|
Data Format
|
||||||
-----------
|
-----------
|
||||||
|
|
||||||
This section proposes data model format which allows to describe any 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
|
||||||
topology of services and mapping between the two.
|
topology of services and mapping between the two.
|
||||||
|
|
||||||
|
@ -1,6 +1,12 @@
|
|||||||
OPENSTACK DIAGNOSTICS PROPOSAL
|
OPENSTACK DIAGNOSTICS PROPOSAL
|
||||||
==============================
|
==============================
|
||||||
|
|
||||||
|
Project Name
|
||||||
|
------------
|
||||||
|
|
||||||
|
**Official:** OpenStack Diagnostics
|
||||||
|
**Codename:** Dark Knight
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
--------
|
--------
|
||||||
|
|
||||||
@ -40,7 +46,7 @@ TBD
|
|||||||
Scope
|
Scope
|
||||||
-----
|
-----
|
||||||
|
|
||||||
As an MVP1, we create service that includes:
|
As an MVP1, we create a service that includes:
|
||||||
|
|
||||||
1. Rules engine with grammatic analysis capabilities
|
1. Rules engine with grammatic analysis capabilities
|
||||||
1. Extensible implementation of rules
|
1. Extensible implementation of rules
|
||||||
|
Loading…
x
Reference in New Issue
Block a user