Skip to end of metadata
Go to start of metadata

The following abstract domain model has two target : 

  • provides a simple model to display a map of a running IT.
  • provides a scalabable model. IE : it can be used to describe any IT components you want to map

As you may guess it's not easy (wink). Anyway thanks all the work done by all the IT engineer world wide and with specification like AMQP, SOA and many others we defined one which could meet the bellowing targets...

NOTE: this is a first version of a mapping ADM. Changes may occurs in the future...

The mapping ADM big picture

Bellow is a quick picture of the the final result the mapping ADM will provide through Ariane Taitale map graph render. 

The mapping ADM objects


  • MUST: a cluster has a unique ID
  • MUST: a cluster is a set of containers
  • MUST: in a cluster each containers has a unique ID
  • MUST: a cluster is active/active or active/passive cluster
  • MAY: a cluster know its current main container in realtime


  • MUST: a container is an administrable entity. Thats mean you (as a human IT ops) can connect and authenticate on it
  • MUST: a container contains at least one admistration gate (see bellow) which is the administration interface access
  • MUST: a container contains a set of nodes (see bellow)
  • MUST: in a container each nodes has a unique ID
  • MUST: a container must know its localisation (town, datacenter, room, server, network (vlan, multicast area ...))
  • MAY : a container should know its consistant state (down, up, ...) in real time


  • MUST: a node is an application logical entity dedicated for a specific task (communication, computing, storage ... etc)

  • MUST: a node contains a set of nodes

  • MUST: a node contains a set of endpoints (see bellow)
  • MUST: in a node each endpoints has a unique ID.

  • MUST: a node contains all necessary meta data for its description


  • MUST: a gate is a node which defines a service
  • MUST: a gate can't be a node child... It's always a container child.
  • MUST: a gate contains at least one communication endpoint for remote calls.
  • MAY: a gate must contains all necessary metadata defining the service


  • MUST: a endpoint is a node address URL. This URL is used for nodes to nodes communications (and so containers to containers)
  • MAY: a endpoint know the network stack it's working on (like for example the network card)
  • MUST: a link is defined by two endpoints (source and destination)
  • MUST: a link contains its transport definition
  • MUST: in the case of multicast transport a link only have a source endpoint


  • MUST: a transport is a communication protocol used by the link
  • MUST: a transport can be unidirectional or bidirectional 



  • No labels