cf-charmers team mailing list archive

[Alexander Lomov <lomov.as@xxxxxxxxx>]

Kapil, the problem is that current RelationContext will retrieve
information only from first unit. The problem occurs when I have service
with multiple units and I need to get information from each of them in
order to establish connection. Such relations can be made with
cf-loggregators and cf-logrouter (loggregator-traffic-controller), service
that connects etcd or other. Here is example of cf-logrouter config that
uses only one cf-loggregator instead of array :
http://bazaar.launchpad.net/~cf-charmers/charms/trusty/cf-logrouter/trunk/view/head:/templates/trafficcontroller.json#L6
.

Thank you,
Alex L.


On 21 May 2014 21:46, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>wrote:

>
> On Wed, May 21, 2014 at 8:18 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>
>> Is it okey that every unit rewrites data for the whole service relation?
>>
>> note sure i understand the question, but relation-set to a previous value
> turns into a no-op in terms of notification to other units.
>
>
>
>>  What if we have several units in service ?
>>
>> I am talking about this code (
>> http://bazaar.launchpad.net/~cf-charmers/charm-helpers/cloud-foundry/view/head:/charmhelpers/core/templating.py#L75
>> ).
>>
>> As far as we moved relation context to we need to take care of it. Also
>> taking information from several units will be useful (sometime required)
>> for cf-loggregator charm.
>>
>> Thank you,
>> Alex L.
>>
>> --
>> Mailing list: https://launchpad.net/~cf-charmers
>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~cf-charmers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>