Scheduler

Deployment based on tagging bees and hives

The Hive server has a built-in scheduler to perform configuration deployment and bee provisioning using tags. Tags can be associated with different entities in BeeOS and then used for queries to determine where a configuration will be sent or where a deployment will be made.

This allows for performing actions on different entities simultaneously without having to perform entity-specific actions.

Configuring

The scheduler uses the tagging established in bees and/or hives to make decisions about where the configuration should be sent. Instead of specifying the identifier of a specific bee to which the configuration should be synchronized, a set of bees can be identified simultaneously by specifying a tag-based query.

The table below shows the tags used for each bee as an example

Bee	Tags
Bee1	north zone, section 1
Bee2	north zone, section 2
Bee3	north zone, section 1, test
Bee4	west zone, section 1
Bee5	west zone, section 2, test

If the tags 'north zone' and 'section 1' are specified, then bees Bee1 and Bee3 would be the ones that the scheduler selects. Then the scheduler looks for to determine whether the selected bee agents are connected to the local hive or to a remote one. A synchronization job is generated and started for each bee. The scheduler monitors the deployment status of the configuration to each of the agents.

Obviously, the bees to which a configuration should be sent must be of the correct type, since a configuration for an OPC/UA bee cannot be sent to an HTTP bee, for example. This is validated by the scheduler before starting synchronization tasks.

Provisioning

El sistema de etiquetas no solo sirve para desplegar configuraciones a las abejas. también se puede ser utilizado para aprovisionar abejas en distintos lugares a la vez.