LEFT | RIGHT |
1 Implicit relations | 1 Implicit relations |
2 =================== | 2 =================== |
3 | 3 |
4 Implicit relations allow for interested services to gather | 4 Implicit relations allow for interested services to gather |
5 lifecycle-oriented events and data about other services without | 5 lifecycle-oriented events and data about other services without |
6 expecting or requiring any modifications on the part of the author of | 6 expecting or requiring any modifications on the part of the author of |
7 the other service's charm. | 7 the other service's charm. |
8 | 8 |
9 Implicit relationships are named in the reserved the juju-* | 9 Implicit relationships are named in the reserved the juju-* |
10 namespace. Both the relation name and interface names provided by juju | 10 namespace. Both the relation name and interface names provided by juju |
(...skipping 41 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
52 | 52 |
53 The admin then issues the following :: | 53 The admin then issues the following :: |
54 | 54 |
55 juju add-relation wordpress rsyslog | 55 juju add-relation wordpress rsyslog |
56 | 56 |
57 If the wordpress charm author doesn't define the `logging-directory` | 57 If the wordpress charm author doesn't define the `logging-directory` |
58 interface juju will use the less-specific (in the sense that it likely | 58 interface juju will use the less-specific (in the sense that it likely |
59 provides less information) `juju-info` interface. juju always attempts | 59 provides less information) `juju-info` interface. juju always attempts |
60 to match user provided relations outside the `juju-*` namespace before | 60 to match user provided relations outside the `juju-*` namespace before |
61 looking for possible relationship matches in the `juju-*` namespace. | 61 looking for possible relationship matches in the `juju-*` namespace. |
LEFT | RIGHT |