The landing job for juju now uses the pre-push script from the juju
branch before running tests. This means it's running go vet over the
source, and I've fixed a couple of errors on master.
What it doesn't do currently is fail the landing if vet reports
issues, as the script doesn't fail in this
I was wondering what is the largest vm count that has been provisioned and
deployed with juju in testing so far? In other words, what is the
demonstrated scale that juju has proven to handle well so far?
Thanks,
Mike
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or
There's this article which was published a while ago:
https://maas.ubuntu.com/2012/06/04/scaling-a-2000-node-hadoop-cluster-on-ec2ubuntu-with-juju/
Hope this helps,
Charles
On Thu, Oct 2, 2014 at 9:02 AM, Mike Sam mikesam...@gmail.com wrote:
I was wondering what is the largest vm count that
Unfortunately that's not very representative of the current implementation
as it was based on pyjuju while the current implementation is in go and
utilizing mongodb instead of zookeeper.
-kapil
On Thu, Oct 2, 2014 at 9:40 AM, Charles Butler charles.but...@canonical.com
wrote:
There's this
juju-core 1.20.9
A new stable release of Juju, juju-core 1.20.9, is now available.
This release replaces stable 1.20.8.
Getting Juju
juju-core 1.20.9 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Notable
juju-core 1.20.10
A new proposed stable release of Juju, juju-core 1.20.10, is now available.
This release may replace stable 1.20.9 after a period of evaluation. If
no issues are raised about this version, it will released on or after
October 7, 2014.
Getting Juju
juju-core 1.20.10 is
