Orchestrator is aware of the replication environment but not aware of the larger environment in which a server may be running in. This information is thus not exposed to DBAs or sysadmins who may be using orchestrator.
It may be desirable to add certain properties to a server, ignored by orchestrator but store by it s o they can be seen by the user, especially on http interface.
Ideas for such properties or labels may be:
it's "role" or "type" used in other parts of configuration management
using a specific type of storage, e.g. filer storage
testing server
using specific types of hardware
other site specific property values
If we allow orchestrator to store this information it must be able to also remove and display it.
given http space is somewhat limited perhaps add another "dot" with a mouse over which provides a list of properties. that's similar to other usage in the GUI
provide a cli interface to extract properties for an instance
provide a http api interface to extract all properties from all instances
These properties should be persistent across an orchestrator restart.
The aim of adding these properties is so that it's easier to see them in the GUI but also external tooling around the MySQL servers or orchestrator may find it helpful to query orchestrator to get these values.
Orchestrator is aware of the replication environment but not aware of the larger environment in which a server may be running in. This information is thus not exposed to DBAs or sysadmins who may be using orchestrator.
It may be desirable to add certain properties to a server, ignored by orchestrator but store by it s o they can be seen by the user, especially on http interface.
Ideas for such properties or labels may be:
If we allow orchestrator to store this information it must be able to also remove and display it.
These properties should be persistent across an orchestrator restart.
The aim of adding these properties is so that it's easier to see them in the GUI but also external tooling around the MySQL servers or orchestrator may find it helpful to query orchestrator to get these values.