Re: Quick win - juju check
> > ... > > My favourite is as always 'juju wait', but that might not turn out to > be trivial. > > While not on our "trivial" set, it is concretely on our TODO for 16.10. John =:-> -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Quick win - juju check
On 24 May 2016 at 11:14, Tim Penhey wrote: > We talked quite a bit in Vancouver about quick wins. Things we could get > into Juju that are simple to write that add quick value. For trivial, quick wins consider: 'juju do --wait', from https://bugs.launchpad.net/juju-core/+bug/1445066 (hey, you filed that bug). Adding a common option for the *-set and other hook environment tools to get their data from stdin, rather than the command line, from https://bugs.launchpad.net/juju-core/+bug/1274460 My favourite is as always 'juju wait', but that might not turn out to be trivial. -- Stuart Bishop -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Quick win - juju check
On Tue, May 24, 2016 at 12:14 PM Tim Penhey wrote: > Hi folks, > > We talked quite a bit in Vancouver about quick wins. Things we could get > into Juju that are simple to write that add quick value. > > There was also talk about "juju check". > > The idea of this command is to surface things that should really be > looked at. > > I was thinking that we could get something in place, and iterate, rather > than going for a gold plated command to start with. > > Using the migration export command, we could easily do cross-entity checks. > > The things that leap to mind are: > * machines that only host units that don't have any units > * applications (nee services) that have no units > * machines that have been pending for more than X minutes > * perhaps surfacing anything that is in an error state? > > Thoughts? > Some more background: https://github.com/juju/juju/pull/4897 Tim > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Quick win - juju check
Does this need to be coded inside juju? Could it be a plugin? This sort of data feels like the kind of thing the juju deployer already consumes so the hooks (albeit exposed as blobs of JSON) may exist already. On Tue, May 24, 2016 at 2:14 PM, Tim Penhey wrote: > Hi folks, > > We talked quite a bit in Vancouver about quick wins. Things we could get > into Juju that are simple to write that add quick value. > > There was also talk about "juju check". > > The idea of this command is to surface things that should really be looked > at. > > I was thinking that we could get something in place, and iterate, rather > than going for a gold plated command to start with. > > Using the migration export command, we could easily do cross-entity checks. > > The things that leap to mind are: > * machines that only host units that don't have any units > * applications (nee services) that have no units > * machines that have been pending for more than X minutes > * perhaps surfacing anything that is in an error state? > > Thoughts? > > Tim > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Quick win - juju check
Hi folks, We talked quite a bit in Vancouver about quick wins. Things we could get into Juju that are simple to write that add quick value. There was also talk about "juju check". The idea of this command is to surface things that should really be looked at. I was thinking that we could get something in place, and iterate, rather than going for a gold plated command to start with. Using the migration export command, we could easily do cross-entity checks. The things that leap to mind are: * machines that only host units that don't have any units * applications (nee services) that have no units * machines that have been pending for more than X minutes * perhaps surfacing anything that is in an error state? Thoughts? Tim -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
