On 17 March 2016 at 15:41, Ian Booth <[email protected]> wrote:
> 2. https://bugs.launchpad.net/juju-core/+bug/1557918 > > We now have the concept of recording a machine provisioning status. This is > great because it gives observability to what is happening as a node is being > allocated in the cloud. With LXD, this feature has been used to give > visibility > to progress of the image downloads (finally, yay). But what happens is that > the > machine status history gets filled with lots of "Downloading x%" type > messages. > Options to solve bug 2 > > A. > Allow a flag when setting status to say "this status value is transient" and > so > it is recorded in status but not logged in history. > > B. > Do not record machine provisioning status in history. It could be argued this > info is more or less transient and once the machine comes up, we don't care so > much about it anymore. It was introduced to give observability to machine > allocation. > > Any other options? > Opinions on preferred solutions? Option C. Add an explicit --done or --complete flag to status-set. When rendering status, the string gets appended in brackets after the message. The spam does not appear in status-history, as the status is not being changed (just the annotation). status-set --done 95% waiting 'Downloading foo' status-set --done 3/43786 maintenance 'Importing samples' -- Stuart Bishop <[email protected]> -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
