Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Ian Booth
On 23/05/17 06:39, Stuart Bishop wrote: > On 22 May 2017 at 20:02, roger peppe wrote: > >> not to show in the status history. Given that the motivation behind >> the proposal is to reduce load on the database and on controllers, I > > One of the motivations was to reduce load. Another motivat

GUI Props

2017-05-22 Thread James Beedy
The latest Juju GUI release is a huge step in the right direction! Amongst the great improvements, the account page is really the start to something great! Massive props and many thanks to all who have put in hard work and long hours to bring the GUI to where it is today. Looking forward, I'm wond

Re: Scale testing analysis

2017-05-22 Thread John Meinel
> > ... > > We have most of the responsive nature of Juju is driven off the watchers. > These watchers watch the mongo oplog for document changes. What happened > was that there were so many mongo operations, the capped collection of the > oplog was completely replaced between our polled watcher

Scale testing analysis

2017-05-22 Thread Tim Penhey
Hi folks, We had another scale test today to analyse why the controller CPU usage didn't fall away as expected when the models were removed. I'll be filing a bunch of bugs from the analysis process, but there is one bug that is, I believe, the culprit for the high CPU usage. Interestingly e

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Stuart Bishop
On 22 May 2017 at 20:02, roger peppe wrote: > not to show in the status history. Given that the motivation behind > the proposal is to reduce load on the database and on controllers, I One of the motivations was to reduce load. Another motivation, that I'm more interested in, was to make the st

JUJU_UNIT_NAME no longer set in env

2017-05-22 Thread James Beedy
Juju 2.1.2 I'm getting this "JUJU_UNIT_NAME not in env" error on legacy-non-reactive xenial charm using service_name() from hookenv. http://paste.ubuntu.com/24626263/ Did we remove this? ~James -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread roger peppe
Another optimisation possibility might be to send less status updates. For example, the uniter could wait until the hook has been executing for some period of time (e.g. 100ms) before sending the "executing" status. If the hook finishes within that period, it would send a bulk update with two updat

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread roger peppe
On 22 May 2017 at 09:55, Ian Booth wrote: > On 22/05/17 18:23, roger peppe wrote: >> I think it's slightly unfortunate that update-status exists at all - >> it doesn't really need to, >> AFAICS, as a charm can always do the polling itself if needed; for example: >> >> while :; do >> s

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Alex Kavanagh
>From a 'principle of least surprise', I think that this proposal is probably a bad idea. The main driver is to (I guess) reduce the volume of 'chat' between the controller and 100's or 1000's of charms, and the effect this has on the status log. However, my 'guess' is also probably wrong as it w

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Stuart Bishop
On 22 May 2017 at 14:36, Tim Penhey wrote: > On 20/05/17 19:48, Merlijn Sebrechts wrote: >> >> On May 20, 2017 09:05, "John Meinel" > > wrote: >> >> I would actually prefer if it shows up in 'juju status' but that we >> suppress it from 'juju status-log' by d

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Ian Booth
On 22/05/17 18:23, roger peppe wrote: > I think it's slightly unfortunate that update-status exists at all - > it doesn't really need to, > AFAICS, as a charm can always do the polling itself if needed; for example: > > while :; do > sleep 30 > juju-run $UNIT 'status-set cu

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread roger peppe
I think it's slightly unfortunate that update-status exists at all - it doesn't really need to, AFAICS, as a charm can always do the polling itself if needed; for example: while :; do sleep 30 juju-run $UNIT 'status-set current-status "this is what is happening"' done &

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread roger peppe
I think it's slightly unfortunate that update-status exists at all - it doesn't really need to, AFAICS, as a charm can always do the polling itself if needed; for example: while :; do sleep 30 juju-run $UNIT 'status-set current-status "this is what is happening"' done &

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Tim Penhey
On 20/05/17 19:48, Merlijn Sebrechts wrote: On May 20, 2017 09:05, "John Meinel" > wrote: I would actually prefer if it shows up in 'juju status' but that we suppress it from 'juju status-log' by default. This is still very strange behavior. Why should th

Re: PROPOSAL: stop recording 'executing update-status hook'

2017-05-22 Thread Tim Penhey
On 19/05/17 19:21, roger peppe wrote: On 19 May 2017 at 03:13, Tim Penhey 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) eac