Difference between revisions of "Centralized Management"
From AMTech WikiDocs
| Line 4: | Line 4: | ||
* 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. | ||
* Platform will allow modifying properties in a set of instances of the same type (allowing some sort of centralized management). Selection will be done based on search criteria | * Platform will allow modifying properties in a set of instances of the same type (allowing some sort of centralized management). Selection will be done based on search criteria | ||
| + | * If the bridge instance 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 | ||
Revision as of 14:07, 19 July 2017
Centralized and specific configuration for managing the bridges and its instances
- Properties configured in the template are used the first time 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.
- Platform will allow modifying properties in a set of instances of the same type (allowing some sort of centralized management). Selection will be done based on search criteria
- If the bridge instance 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
