Open Stack

Seconding what Matt said.  You are also going to need to spend some time at the kilo code level to do the flavor migrations.  As that was a requirement from kilo -> liberty.  I also know that you needed to be on kilo.1 (or .2) to go to liberty to fix a bug in Numa Node pinning (iirc).

I would also look at the upgrade requirements for every version between icehouse and liberty and you are also going to need to perform those actions.


___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: Matt Fischer <matt at mattfischer.com<mailto:matt at mattfischer.com>>
Date: Monday, January 11, 2016 at 8:29 AM
To: Liam Haworth <liam.haworth at bluereef.com.au<mailto:liam.haworth at bluereef.com.au>>
Cc: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>
Subject: Re: [Openstack-operators] [nova] Recovering instances from old system

Personally, I'd just try to load the instance images like you said. If you try to load Icehouse records onto Liberty code its not going to work. Typically you'd do the upgrade one step at a time with database migrations done at every step.

On Sun, Jan 10, 2016 at 9:58 PM, Liam Haworth <liam.haworth at bluereef.com.au<mailto:liam.haworth at bluereef.com.au>> wrote:
Hey Abel,

When I say 'wiped everything clean" I mean that we made backups of the databases and configuration on all hosts before reinstalling Ubuntu 14.04 LTS on top to start with a clean slate, we did this because we decided to make the change to the LinuxBridge agent from the OpenVSwitch agent plus we where upgrading from Icehouse to Liberty, this along with a major restructure with how our network is laid out.

Really I'm just looking for some input on if I should attempt to extract the records of the instance backed up from the database and manually insert them or if I should take the instance dicks and load them in as images and spin them backup from there.

Hopefully I made a bit more sense this time, sorry.

On Sat, 9 Jan 2016 at 03:26 Abel Lopez <alopgeek at gmail.com<mailto:alopgeek at gmail.com>> wrote:
I would expect that if you have the databases in place, and they went through the proper migrations, that your instances would still be there.
You can check the nova database instances table using the uuid.

How exactly did you 'wipe everything clean'?

On Jan 7, 2016, at 5:35 PM, Liam Haworth <liam.haworth at bluereef.com.au<mailto:liam.haworth at bluereef.com.au>> wrote:

Hey guys,

I just recently rebuilt the OpenStack infrastructure at my work to upgrade from Juno to Liberty, before wiping everything clean I made dumps of all the databases and the instances where persisted though the upgrade via NFS.

Now that I have the infrastructure up and going again I was wondering what would be the best way to import the instances back in, I understand I may need to change some fields in the database dumps to change project ids and such but I just wanted to get some input on if this is a good idea or if there is a better way to do this?

Kind regards,
--
Liam Haworth | Junior Software Engineer | www.bluereef.com.au<http://www.bluereef.com.au/>
_________________________________________________________________
T: +61 3 9898 8000 | F: +61 3 9898 8055


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

--
Liam Haworth | Junior Software Engineer | www.bluereef.com.au<http://www.bluereef.com.au/>
_________________________________________________________________
T: +61 3 9898 8000 | F: +61 3 9898 8055



_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto: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/20160111/799bbc8a/attachment.html>