lp:~aluria/charm-telegraf

Owned by Alvaro Uria
Get this repository:
git clone https://git.launchpad.net/~aluria/charm-telegraf
Only Alvaro Uria can upload to this repository. If you are Alvaro Uria please log in for upload directions.

Branches

Name Last Modified Last Commit
lp1775062 2018-06-06 05:26:58 UTC 2018-06-06
Added netifaces package to test_requirements

Author: Thomas Cuthbert
Author Date: 2018-06-06 05:26:58 UTC

Added netifaces package to test_requirements

remote-unit-name 2018-01-31 08:52:47 UTC 2018-01-31
Remove extrachecks to return principal's unitname

Author: Alvaro Uria
Author Date: 2018-01-31 08:52:47 UTC

Remove extrachecks to return principal's unitname

  get_remote_unit_name verified private_ip matching between principal
  unit and telegraf itself. However, this might break in a multi-NIC
  environment and there's no real need to run such check since telegraf
  is a subordinate.

  Possible cases:
  1) Charms that can have more than one relation with telegraf (mysql,
  pgsql, mongodb, etc. see the "requires" section of metadata.yaml).
  Telegraf can run specific plugins + juju-info rel
  Result: No more than a single telegraf unit becomes subordinate, so
  rel['__unit__'] would return the same value for any relation

  2) 2 charms living in the same container/metal, and related to
  telegraf
  Result: Each principal unit, using a diff charm each, will have its
  own relation with telegraf (2 telegraf units will live in the node).
  Each unit will return a different rel['__unit__'], as they have
  different principal units

  3) 1 charm living in a container/metal, and related to telegraf
  Result: telegraf has a single "requires" relation and will return
  rel['__unit__'] of its principal

12 of 2 results
This repository contains Public information 
Everyone can see this information.

Subscribers