-jlk
- Original message -From: Andrew Laski To: openstack-operators@lists.openstack.orgCc:Subject: Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)Date: Mon, Jun 27, 2016 5:35 AM
On Sun, Jun 26, 2016, at 07:58 PM, Sam Morrison wrote:> I’ve done kilo -> mitak
On Sun, Jun 26, 2016, at 07:58 PM, Sam Morrison wrote:
> I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing
> special I needed to do.
>
> If you’re wanting to do live upgrades with nova you can’t skip a version
> from my understanding.
Correct. Not without doing the work yourse
I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing special I
needed to do.
If you’re wanting to do live upgrades with nova you can’t skip a version from
my understanding.
Sam
> On 25 Jun 2016, at 4:16 AM, Jonathan Proulx wrote:
>
> Hi All,
>
> I about to start testing for
FWIW, I did that with Cinder and it was great except for one DB change we
had to make regarding the server name for volumes -
http://dischord.org/2015/12/22/cinder-multi-backend-with-multiple-ceph-pools/
is a pretty good description of what I saw. I suspect that was just a poor
configuration from
Hi All,
I about to start testing for our Kilo->Mitaka migration.
I seem to recall many (well a few at least) people who were looking to
do a direct Kilo to Mitaka upgrade (skipping Liberty).
Blue Box apparently just did and I read Stefano's blog[1] about it,
and while it gives me hope my plan is
