-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revist address_root != "observatory" #327
Conversation
Also changed OCSAgent to fail if any startup subscriptions fail.
... even when looping on failed connections to influxdb.
This SCF param actually wasn't used anywhere, except optionally in the ocs-agent-cli (which now simply defaults to {address_root}.registry and can still be overridden). The command-line argument remains, but is doc'ed as deprecated and has no effect on anything.
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! However now we have to deal with users configuring the crossbar server, which we avoided originally, bundling a sensible default in the crossbar Docker image we provide (with the observatory.
URI.) I think our documentation on this needs some updating.
... in response to requests for "generate_crossbar_config" and "start crossbar". Also update erroneous docs for the former.
Now the crossbar config can be bind-mounted in, or else some envvars are used to generate one from a template before crossbar is started.
Also the SCF docs warn about updating the crossbar config.
Thanks -- I think I've addressed all your suggestions now. The connection error now presents a more detailed error message, with advice if possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, I've made some modifications to the documentation. Will merge when checks pass.
Description
The
address_root
has always been set toobservatory
in OCS installations. But this prefix is configurable in the SCF, and for the most part wasn't hard-coded anywhere in ocs (nor socs).I have removed a small number of hard-coded occurrences of
observatory.
. These were in the feed subscription wildcards the registry, aggregator and influxdbpublisher.The address_root was intended to be user configurable; I consider this to be a bugfix.
Some additional changes along the way:
Motivation and Context
At the observatory we'll have a few very similar systems, e.g. sat1 and sat2, running as independent OCS instances. In some situations (influxdb and grafana, primarily) we will have data from all systems available, and so the feeds can't have the exact same names. That means we either need to carefully include "sat1" / "sat2" in every instance-id ... e.g. "observatory.sat1_acu", "observatory.sat2_acu" OR take advantage of the configurable prefix and have the agent addresses be "sat1.acu", "sat2.acu".
How Has This Been Tested?
I ran an OCS setup on a single host, with all the affected agents, plus a fake data agent. Confirmed I could see the data appear in grafana and that data was showing up in aggregator output files. All tests/ pass.
Types of changes
Checklist: