Difference between revisions of "Centralized Management"
From AMTech WikiDocs
| Line 4: | Line 4: | ||
** When a bridge starts, a clone of the template is performed to generate the instances. If the bridge has been previously cloned, then the existing instances are reused | ** When a bridge starts, a clone of the template is performed to generate the instances. If the bridge has been previously cloned, then the existing instances are reused | ||
* Bridge will react to CRUD observations for the cloned instances only, not the templates. | * Bridge will react to CRUD observations for the cloned instances only, not the templates. | ||
| − | * Properties can be redefined in a set of instances at the same time using the option of Group Edition (see [[Group_Edition | Editing | + | * Properties can be redefined in a set of instances at the same time using the option of Group Edition (see [[Group_Edition | Editing a group of things]]). This allows achieving some sort of centralized management when the instances have been already cloned |
* If the bridge is deleted but the instances associated to it remain in the system, the clone will raise an error of ResourceAlreadyExist for the instances. They must be deleted along with the bridge | * If the bridge is deleted but the instances associated to it remain in the system, the clone will raise an error of ResourceAlreadyExist for the instances. They must be deleted along with the bridge | ||
Latest revision as of 13:58, 18 June 2018
Leveraging the concepts of templates, clones, and the edition of properties in each of them, both, a centralized and specific configuration can be defined for bridges and its instances.
- Properties configured in the template are copied to all the clones generated when the bridge starts, allowing a centralized configuration. From that moment on, properties configured in the instances are not overwritten, allowing specific configuration.
- When a bridge starts, a clone of the template is performed to generate the instances. If the bridge has been previously cloned, then the existing instances are reused
- Bridge will react to CRUD observations for the cloned instances only, not the templates.
- Properties can be redefined in a set of instances at the same time using the option of Group Edition (see Editing a group of things). This allows achieving some sort of centralized management when the instances have been already cloned
- If the bridge is deleted but the instances associated to it remain in the system, the clone will raise an error of ResourceAlreadyExist for the instances. They must be deleted along with the bridge
