I don't think the upgrade matters as much as speed. I feel like most users
know to manage updates already, with their own policies, and that the fast
user experience is important.
Even if juju upgrades initially, users will still need to manage updates
after, so I'm not sure how much the initial
Thanks Dave!
A downside to disabling upgrades is that users may have a bad experience if
broken packages get installed and their services don't work. Not sure how
often this would happen.
On Thu, Oct 2, 2014 at 6:19 AM, David Cheney david.che...@canonical.com
wrote:
On Thu, Oct 2, 2014 at
In practice, it almost never happens.
I don't remember seeing anything actually from the archive break a charm on
update -- though the cloud tools pocket did have a breakage about 8 months
ago which did bad things.
--Mark Ramm
On Thu, Oct 2, 2014 at 10:14 AM, Matt Rae matt@canonical.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Why not change the image-stream to 'daily' from 'release' rather than
altering whether or not we update packages on an instance?
The default environment configuration specifies that the image stream
is 'releases' rather than 'daily'. This means
Yesterday during my review queue time, I revisited a MP[1] I had worked on the
previous week. With the information provided by gnuoy, I was able to fully test
the rabbitmq-server against bug #1355848[2] and I am happy to report that the
bug is fixed by this MP and have approved it.
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
In terms of 'upgrading later', Juju is built for not going into the
machines after they are launched. Bare that in mind.
--
José Antonio Rey
On Oct 2, 2014 8:19 AM, David Cheney david.che...@canonical.com wrote:
On Thu, Oct 2, 2014 at 10:55 PM, Matt Rae matt@canonical.com wrote:
I don't
On 02/10/14 15:46, Robert Jennings wrote:
Why not change the image-stream to 'daily' from 'release' rather than
altering whether or not we update packages on an instance?
The default environment configuration specifies that the image stream
is 'releases' rather than 'daily'. This means that
I wanted to throw some insight from a field perspective on juju upgrades
and or updates ~ which I hope is helpful, and in the spirit and in line
with this discussion. Here are my notes :
1) Stable juju versions : Once a customer ends up finding a juju-core,
juju-gui version that works with
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
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
16 matches
Mail list logo
