I would generally think to model this as part of the relation data. Since you want the individual units of your charm to connect to different units of Mongo, then it sounds like you want a peer relation in your charm, and each unit could then report what unit of mongo it is connecting to on the peer relation, and the others could try to avoid connecting to the mongo that a peer is connected on.
John =:-> On Mon, May 19, 2014 at 1:40 PM, Tudor Rogoz <ro...@adobe.com> wrote: > Hi all, > > > I just started writing on a new juju charm and I'm not sure how can i > solve a specific problem. > > > The charm that I'm implementing depends on the mongodb charm.What i want > to achieve is to link each unit from my service to a different unit from > the mongodb service.For as i understood juju supports relations on > the service level, and this means that all the units from my service will > connect to each unit from the mongodb service.As an use case for my > needs, if i deploy my service with 5 units and a mongodb service with 3 > units and link them, i want that 3 (random) units from my service to > connect to separate 3 mongodb units. > > I can deploy separate service instances using my charm and link to > separate mongo database services and probably will work, but i want to > accomplish this on units level. > > Any ideas, suggestions? > > > > Thanks a lot, > > Tudor > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
