rsyslog configuration worker

Andrew Wilkins andrew.wilkins at canonical.com
Mon Feb 24 07:50:10 UTC 2014


On Mon, Feb 24, 2014 at 3:46 PM, Ian Booth <ian.booth at canonical.com> wrote:

> >
> > It doesn't necessarily have to be a worker, just something that runs once
> > at machine agent startup: wait for environ config, write rsyslog config,
> > restart rsyslog.
> >
>
> That's actually how the upgrade happens now - the machine agent is the
> process
> which invokes the upgrade operations with a context containing a state API
> connection ie the upgrades are only run once a state server worker is
> running
> and the API (and hence environment) is available. So we could do whatever
> rsyslog config changes are needed to support TLS as part of the standard
> upgrade
> process. Unless I'm misunderstanding something.


Yep, I'm suggesting we do that, but not as an upgrade step. Just do it at
agent startup time, all the time. Then the bits in environs/cloudinit can
be deleted.

As said before, though, upgrading to TLS is out of the question due to
inability to either use old certs or generate new ones within the
environment.


> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140224/2bc1468b/attachment-0001.html>


More information about the Juju-dev mailing list