+1 On Fri, May 19, 2017 at 6:10 AM David Britton <[email protected]> wrote:
> +1 from me: https://bugs.launchpad.net/juju/+bug/1530840 > > :) > > On Thu, May 18, 2017 at 8:13 PM, Tim Penhey <[email protected]> > wrote: > >> Hi folks, >> >> Currently juju will update the status of any hook execution for any unit >> to show that it is busy doing things. This was all well and good until we >> do things based on time. >> >> Every five minutes (or so) each unit will have the update-status hook >> executed to allow the unit to set or update the workload status based on >> what is currently going on with that unit. >> >> Since all hook executions are stored, this means that the show-status-log >> will show the unit jumping from executing update-status to ready and back >> every five minutes. >> >> The proposal is to special case the update-status hook and show in status >> (or the status-log) that the hook is being executed. debug-log will >> continue to show the hook executing if you are looking. >> >> This will reduce noise in the status-log, simplify some of our code >> around dealing with status-log, and reduce load on controllers looking >> after hundreds or thousands of units. >> >> Is anyone opposed to this change? > > >> >> Tim >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > > > > -- > David Britton <[email protected]> > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Ante Karamatić [email protected] Canonical
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
