Difference between revisions of "Centralized Management"
From AMTech WikiDocs
| Line 1: | Line 1: | ||
[[Centralized and specific configuration for managing the bridges and its instances]] | [[Centralized and specific configuration for managing the bridges and its instances]] | ||
| − | + | * When a bridge starts, a clone of the template is performed. If it is the first time, the bridge and its instances are cloned from the templates (properties configured in the template are copied to the instances). If the bridge has been previously cloned, then the existing instances are reused (properties configured in the instances remain unchanged) | |
| − | + | * Bridge will react to CRUD observations for the cloned instances only, not the templates. | |
| − | + | * Platform will allow modifying properties in a set of instances of the same type (allowing some sort of centralized management) | |
Revision as of 12:59, 18 July 2017
Centralized and specific configuration for managing the bridges and its instances
- When a bridge starts, a clone of the template is performed. If it is the first time, the bridge and its instances are cloned from the templates (properties configured in the template are copied to the instances). If the bridge has been previously cloned, then the existing instances are reused (properties configured in the instances remain unchanged)
- Bridge will react to CRUD observations for the cloned instances only, not the templates.
- Platform will allow modifying properties in a set of instances of the same type (allowing some sort of centralized management)
