MC control
The Model Control handles model administration. The Model Control service is aware of which models are available, running and (re)starts models when necessary. An instance for a model is started for a particular scenario. Thus, multiple instances of a model may be running. An instance of a model is subscribed to a particular bin. When a model is started through the Model Control service, the Model Control service only causes the model to be started and connected to the IMB hub. The configuration for starting comes from the different collections related to the Model Control service.
MC Controlling collections
- MCNodes: There can be multiple MC Node services that register them selves in the MCNodes collection.
- MCSetups: The setups describe modules that can be started on a node. A setup contains name, version and configuration of a module.
- MCInstances: All running instances of the modules with there configuration and state are in the MCInstances collection. The instances publish their current state by updating fields on the object linked to their id in the MCInstances collection. The requested state of an instance can be set in the MCInstances collection and the instance of the module it self will react on it by terminating when asked to do so. The services controlling it will also monitor the instance and force it to terminate when not reating to the request.
MC control tool
The MC Control tool gives overview of the state of nodes, setups and instances of modules. By selecting a setup an instance of the module defined by the setup can be started. Optionally, startup parameters can be set for the instance before the startup. By selecting an instance it can asked to stopped or forced to stop. this last option only works on instances started by a MC Node service.
The user interface
