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 our Kilo setup rather than a change specifically related to the upgrade, but the upgrade brought it to light. Haven't yet taken the same step with others, we're doing the upgrades one thing at a time and for some (Nova) we'll be jumping through Liberty because of the risk of jumping two steps at a time. On 25 June 2016 at 06:16, Jonathan Proulx <jon at csail.mit.edu> wrote: > 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 possible it's not realy a > technical piece. > > I'm on my 7th version of OpenStack for this cloud now so not my first > redeo as they say, but other than read Liberty and Mitaka release > notes carefully and test like crazy wonder if anyone has seen specific > issues or has specific advice for skiping a step here? > > Thanks, > -Jon > > -- > [1] > https://www.dreamhost.com/blog/2016/06/21/dreamcompute-goes-m-for-mitaka-without-unleashing-the-dragons/ > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160625/5d85fb88/attachment.html>