> "running on the same containers as mysql need to join the relation with mysql"
Yes, and, being generic, Juju doesn't tie "container scope of a relation" to "charms placed in the same system container". So, in practice, this will work for both "in-container" and outside container cases with subordinate and principal charms simply residing on the same logical machine.
Just wanted to go through all cases because there are 3 terms here related to "scope" and "container" words in one way or another which makes it confusing:
Jason,
> "running on the same containers as mysql need to join the relation with mysql"
Yes, and, being generic, Juju doesn't tie "container scope of a relation" to "charms placed in the same system container". So, in practice, this will work for both "in-container" and outside container cases with subordinate and principal charms simply residing on the same logical machine.
Just wanted to go through all cases because there are 3 terms here related to "scope" and "container" words in one way or another which makes it confusing:
1. scope (as in reactive charm library "communication scopes" https:/ /jujucharms. com/docs/ 2.2/developer- layers- interfaces# communication- scopes) /jujucharms. com/docs/ 2.2/authors- subordinate- applications# terms)
2. (container) scope (as in Juju relation scope https:/
3. container (lxd)