> - would you find it helpful to have common* statuses?
> - or, would you find it more helpful to have statuses unique to each
entity type?
I'm still very much a beginner when it comes to developing charms, but from
my perspective, it would be most useful to have common statuses, so that
knowledge
Hi,
I'm working on a fix for a bug, where we list dying/dead models in the
output of "juju list-models". While working on this, it became clear to me
that we need a way to convey the status of models to users: whether they're
available for use, being destroyed, or archived for post-mortem analysis
Woohoo!
On Tue, Apr 12, 2016 at 2:33 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> # juju-core 1.25.5
>
> A stable release of Juju, juju-core 1.25.5, is now available.
> This release replaces version 1.25.3
>
>
> ## Getting Juju
>
> juju-core 1.25.5 is available for Xenial and backp
# juju-core 1.25.5
A stable release of Juju, juju-core 1.25.5, is now available.
This release replaces version 1.25.3
## Getting Juju
juju-core 1.25.5 is available for Xenial and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Windows, Centos
Hi again,
I investigated this issue a little further and I found out that with
YARN there is no longer a single job tracker to run jobs; instead,
each job has its own ApplicationMaster that takes care of execution
flow.
I was not able to build Apache Giraph using the flags suggested for
Hadoop Yar
