I guess maybe it would be nice to have a service instance as ADCM entity: the ability to deploy multiple instances of the same service on the same cluster, with different settings.
For example: I am planning to use adcm to deploy postgresql clusters built on pacemaker / corosync. In this case, the cluster is the corosync setup, and the service is postgresql as a set of pacemaker cluster resources (pgsql + vIP). And I would like to run N DBMS in the one cluster, with the ability to dynamically add and remove them. The template for such a set of resources, as well as the logic for adding them to the cluster, are the same, but the settings (PGDATA, port, etc.) are different.
I guess maybe it would be nice to have a service instance as ADCM entity: the ability to deploy multiple instances of the same service on the same cluster, with different settings.
For example: I am planning to use adcm to deploy postgresql clusters built on pacemaker / corosync. In this case, the cluster is the corosync setup, and the service is postgresql as a set of pacemaker cluster resources (pgsql + vIP). And I would like to run N DBMS in the one cluster, with the ability to dynamically add and remove them. The template for such a set of resources, as well as the logic for adding them to the cluster, are the same, but the settings (PGDATA, port, etc.) are different.