You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described web/status shows all the active orchestrator nodes and which one is active.
What is not shown is which db server orchestrator is actually using to store it's data. Providing this information would be useful. It saves connecting to the host(s) by ssh and looking at the json files.
Note: given the name used may be a vip, it might be good to also ask the server it's hostname (@@hostname) and version (@@Version) and thus show the output something like:
Getting the @@hostname and @@Version of the backend server should be out of orchestrator's hands (of course it is likely that orchestrator monitors its very own topology, but that's irrelevant).
Lets please separate what you should know about orchestrator from what you should know about your configuration (puppet/chef) or your internal workings.
As for generally showing the backend database name, I believe this should be OK. Some may have a security concern about that, and we can further protect it by a configuration variable (bool).
sjmudd
pushed a commit
to sjmudd/outbrain-orchestrator
that referenced
this issue
Dec 27, 2016
As described web/status shows all the active orchestrator nodes and which one is active.
What is not shown is which db server orchestrator is actually using to store it's data. Providing this information would be useful. It saves connecting to the host(s) by ssh and looking at the json files.
Note: given the name used may be a vip, it might be good to also ask the server it's hostname (@@hostname) and version (@@Version) and thus show the output something like:
orchestrator database backend: some-vip-address.example.com:3306 (@@hostname_value/@@version_value)
The text was updated successfully, but these errors were encountered: