On 18 October 2017 at 02:21, John Meinel wrote:
> Ah, I guess that telegraf is actually gathering extra data from mysql or
> postgres about database specific stats, and thus it should have a container
> scoped relation because it wants to explicitly sit with postgres and collect
> general machine
John,
I think having relation scope to depend on both sides and take
min(scope_left, scope_right) is the right approach. After all, it doesn't
restrict other applications from using the same relation (with the same
unique interface name) in a different scope.
I described use-cases here in a gener
Ah, I guess that telegraf is actually gathering extra data from mysql or
postgres about database specific stats, and thus it should have a container
scoped relation because it wants to explicitly sit with postgres and
collect general machine information, as well as collect postgres specific
informa
Why is the subordinate container scoped? The specific scope of container is
that you only see the single instance that you share a machine with.
Typically subordinates will use something like the juju-info relation
because all they really care about is to be colocated on the same machine.
I can't
Hi.
A server declares a relation with standard scope. Lets use PostgreSQL
for example, which declares the following in metadata.yaml:
provides:
db:
interface: pgsql
A client happens to be a subordinate, and declares its end of the
relation as container scoped. So in its metadata.yaml:
req
