Merge lp:~adeuring/charms/precise/juju-reports/config-cloud-health-script into lp:~juju-qa/charms/precise/juju-reports/trunk
Status: | Merged |
---|---|
Merged at revision: | 47 |
Proposed branch: | lp:~adeuring/charms/precise/juju-reports/config-cloud-health-script |
Merge into: | lp:~juju-qa/charms/precise/juju-reports/trunk |
Diff against target: |
55 lines (+13/-2) 3 files modified
config.yaml (+6/-0) hooks/common.py (+6/-2) templates/crontab.tmpl (+1/-0) |
To merge this branch: | bzr merge lp:~adeuring/charms/precise/juju-reports/config-cloud-health-script |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Aaron Bentley (community) | Approve | ||
Review via email: mp+241280@code.launchpad.net |
Description of the change
Updates for the script "cloud-heath":
- New entry in the crontab template
- new config parameter "cloud-
I am not 100% sure what the best time to start the script is: The cloud health builds are started at *:45 and run typically less than 5 minutes; azure tests need typically up to 10 or 12 minutes.
Builds from most jobs can occasionally run for more than 20 minutes, meaning that the most build (that will likely be a failure) will not be noticed for another hour. OTOH, waiting longer just for the rare longer running jobs does not make much sense either.
Another option would be to start the script three or four times per hour, for example, at minutes 15, 35, 55.
Thanks for testing. Looks good to me.