lp:~bigdata-dev/charms/xenial/rsyslog-forwarder-ha/trunk

Created by Kevin W Monroe on 2016-09-29 and last modified on 2016-10-27
Get this branch:
bzr branch lp:~bigdata-dev/charms/xenial/rsyslog-forwarder-ha/trunk
Members of Juju Big Data Development can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Juju Big Data Development
Status:
Development

Recent revisions

25. By Kevin W Monroe on 2016-10-27

remove sitepackages=True (it is not needed, and can cause conflicts if user has py2 flake8 installed)

24. By Kevin W Monroe on 2016-10-26

use explicit charm name in amulet test (bundletester confused rsyslog with rsyslog-fwrd without this)

23. By Kevin W Monroe on 2016-10-26

use our xenial rsyslog in the test; better metadata tags

22. By Kevin W Monroe on 2016-10-26

rework unit test for py3 and check that the rsyslogd process is actually running

21. By Kevin W Monroe on 2016-10-26

adjust test targets and setup for py3

20. By Kevin W Monroe on 2016-10-26

sync latest charmhelpers

19. By Kevin W Monroe on 2016-09-29

return (dont die) if a syslog aggregator relation already exists. this can happen if multiple principal charms are colocated on the same machine. in this case, rsyslogd will already be configured on the machine, so just log the event and move on.

18. By Kevin W Monroe on 2016-09-26

simplify deployment test and move to xenial

17. By Tim Kuhlman on 2016-09-02

[kuhlmant,r=jsing] Update configuration to avoid duplicated kernel logs

16. By Cory Johns on 2016-06-10

[kwmonroe, r=johnsca] Update test to use trusty version of Postgres

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:charms/rsyslog-forwarder-ha
This branch contains Public information 
Everyone can see this information.