Quick win - juju check

[David Cheney]

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 <tim.penhey at canonical.com> 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 at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev