Roboconf Domains

Currently, all the applications are managed by a same DM.
A DM should be managed by a single team. When several departments would like to share infrastructures but manage their own applications, it is possible to use Roboconf domains.

To make things simple, a Roboconf domain is defined by a Roboconf DM.
So, to have multiple domains, you should have multiple DMs.

Each domain should…

• … have its own DM.
• … have its own credentials or its own messaging server.
• … have its own credentials for the cloud infrastructure.

When using HTTP messaging, domains are implicit since the DM is the domain.
With RabbitMQ as the messaging server, it is necessary to set the domain property in the net.roboconf.dm.configuration file. It is then possible to have several DMs using the same messaging server (or cluster of messaging servers) without interactions.

And the infrastructure credentials guarantee one DM will not interact with the images and virtual machines from another user. This approach allows several topologies (here pictured with 2 virtualized infrastructures). Obviously, here, messaging could also be read as clustered messaging.

Classic / Basic Architecture

Each DM with its own Messaging

Shared Messaging

Hybrid Domains