Glad to help. I reported http://pad.lv/1761288 regarding the ability to
abort/rollback broken upgrades in order to get out of sticky upgrade
situations.
Also hope to see a clean up of the UX and the addition of actual dry-run
capabilities in http://pad.lv/1638714
We're looking forward to
Sandor, thanks for this perspective! It was really helpful to see how
upgrades went for you in real life, and more importantly, that 2.3.x
seems to have gone smoothly. We'll be carefully watching and monitoring
2.3->2.4 upgrades as the release draws nearer.
Nicholas
On 04/01/2018 04:04 AM,
Hi Nicholas,
Thanks for the input. I wrote up a short blog post about our experiences
going from 2.1 to 2.3. Hopefully it provides some feedback and can be
helpful for others in the same position.
http://zeestrataca.com/posts/upgrading-juju/
Regards
--
Sandor Zeestraten
On Thu, Mar 22, 2018 at
Sandor, re:sharing experiences, if you want to frame some scenarios
you've had trouble with, please feel free to share those. Distilling it
down into a repeatable deployment -> upgrade will help us understand and
account for it. As Tim mentioned, tools like juju-upgrader are generally
Sandor, re:sharing experiences, if you want to frame some scenarios
you've had trouble with, please feel free to share those. Distilling it
down into a repeatable deployment -> upgrade will help us understand and
account for it. As Tim mentioned, tools like juju-upgrader are generally
Hi Sandor,
Streamlining upgrades is definitely on the team's road-map. We are aware
of the juju-upgrader plugin, and will be looking to incorporate some of
that functionality into the core codebase.
The core team has worked on better upgrade testing as part of our CI,
which enables more test
Is this shared google doc open for external contributors?
After spending a while upgrading our 2.1.x environments to 2.3.x and
hitting some bugs along the way in staging (see below), I'd agree that the
process needs a bit of love and wouldn't mind sharing some experiences.
Rick mentioned
I think this UX on the upgrade process has obvious problems. Nobody
should have to guess at what to do, in which sequence.
Can I suggest that we have a shared Google doc to mock up a nice
experience starting with the simple command 'juju upgrade' which then
walks people through the process,
Hi Daniel,
The issue here is that you are upgrading the default model, not the
controller model itself.
I think we could make the error messaging more clear, and also have the
command also check the controller version before showing a lot of
baffling output.
What you need to do is upgrade the
