As mentioned, a peer-relation is the way to go about this. It gives you a hook path for the units to communicate to each other.
John =:-> On Fri, Oct 17, 2014 at 2:44 PM, saurabh <[email protected]> wrote: > > On Friday 17 October 2014 02:51 PM, Simon Davy wrote: > >> On 17 October 2014 10:13, saurabh <[email protected]> wrote: >> >>> Hi All, >>> >>> I need to communicate password from one charm instance to another >>> instance >>> in order to authenticate services. >>> Please suggest me a way to do that. >>> >> Hi Saurabh >> >> I assume by "one charm instance to another" you mean two units in the >> same service? >> >> In which case, having the charm implement the peer relation would >> allow that communication. E.g. if one unit does a relation-set >> password=<secret>, all other units (instances) in the service will be >> able to do "relation-get password" in the peer relation-changed hook. >> >> More info at: https://juju.ubuntu.com/docs/authors-charm-metadata.html# >> peer-relations >> >> If you mean between two instances of different charms, then a normal >> relation will do, of course, >> >> HTH >> > > Hi, > > Yes there will be two units, but the password will be randomly generated > on one of the units so how do I send this randomly generated password to > the another unit? > > Thanks, > > > > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
