Difference between revisions of "Data"
(→Guiding principles) |
(→Conceptual Communications Model) |
||
| Line 8: | Line 8: | ||
== Conceptual Communications Model == |
== Conceptual Communications Model == |
||
{| class="wikitable" |
{| class="wikitable" |
||
| − | |Node message (Req) |
+ | |!Node message (Req) |
|Data Response (Rep) |
|Data Response (Rep) |
||
|Node Action |
|Node Action |
||
Revision as of 22:07, 26 December 2015
Data is under development, so subject to change (quite much hopefully).
Nodes interact with Data according to a protocol. We suggest we comply with the AMQP standard. https://www.amqp.org
Contents
Guiding principles
- Precedence Analysis
- Desired state is assumend
- Data holds the Universal Truth
Data presents nodes on request with node taylored views on the Universal Truth, thus supplying the nodes with the the information they require. This is the normal situation in which Data provides updates on the views. Data may respond that it needs additional information. Nodes may find Data needs to be updated with information they hold.
Conceptual Communications Model
| !Node message (Req) | Data Response (Rep) | Node Action |
| Request View ---> | Reply with view data ---> | Process view info |
| Request for Information ---> | Prepare Information Feed |
Feeds
Nodes send out feeds on request. This request is triggered by a Data response to an information request. The node assumes the requested information to be available from Data, but Data can decide to ask for more information before being able to supply the requested information.
Schemas
Views
CMDB
Icinga
Nagios
hostgroups, fqdn, service
Return to: Cfengine
