On Mon, Oct 13, 2014 at 10:49 PM, Vasiliy Tolstov <[email protected]> wrote:
> 2014-10-13 19:19 GMT+04:00 Marco Ceppi <[email protected]>: > > So there's no current way to determine when an environment is idle in > Juju, > > there's work being done to allow services to illuminate more than just > the > > current states of PENDING, INSTALLED, STARTED, ERROR in Juju which will > help > > illuminate where a service is in it's lifecycle. However, all of that > would > > be gathered from the juju status output. Currently only YAML and JSON are > > supported but in 1.21 new options such as summary, oneline (comparable to > > git log --oneline), and tabular will be available for parsing. > > > Ok, so if i need to check that for example mysql and wordpress > completed and running i need to grep juju status for agent state and > check that it started three times (machine started and wordpress and > mysql), right? > > My current best practice on this is to include a health check in the charm and manually invoke via juju run ie. juju run --service=wordpress "./health" and have the health hook return some structured data (json) to stdout. cheers, Kapil
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
