upgrade from icehouse to juno [closed]

asked 2015-09-26 13:43:17 -0600

Marco Marino gravatar image

Dear all, I have to upgrade my openstack environment from icehouse to juno and this post contains plenty of questions. Please, don’t tell me that exists an openstack guide for upgrade from icehouse to juno, because the guide is a base but I need more precise answers. My actual configuration is: 2 controller nodes in HA with mysql, rabbitmq, keystone, glance, nova, neutron-server. No cinder, no swift….. 1 network node with neutron-openvswitch-agent, metadata-agent, dhcp-agent and l3-agent. I’m using neutron with gre for the network part 12 compute nodes with nova-compute and neutron-openvswitch-agent

My OS is centos 6 for all servers and since juno is not supported in epel6, I have to upgrade my OS to centos 7. CONTROLLER UPGRADE: As suggested in the guide, I have to upgrade controller first. My idea is to install a completely new controller (“temp” controller) with centos 7 and icehouse, then import the database from production and perform an upgrade on this new server to juno (following the official guide). At this point, I could shut down my old icehouse controllers and change the ip of the new juno server. My first question is: since I install the new controller using the same management network of the icehouse controllers, having 2 rabbitmq-server on the same management network could be a problem? I’m thinking to multicast packets…. Should I install my new controller on a separate network and change the ip only when the icehouse controller is powered off? What are the problems related to an openstack environment without controller from the vm point of view? I’m thinking to the dhcp lease time inside vms. What happens if lease time expires and the controller is down (more precisely rabbitmq and neutron-server are down)? Vms succeed in ip renewal?

NETWORK UPGRADE: For network node I will install a completely new Centos7 server with juno. Then, using the controller and neutron cli, I have to change the l3-router associated agent and dhcp associated agent. I tested this in a virtualized environment and works well! Downtime of vms is really short (about 2 or 3 seconds if made with a script). I need your opinion here…. This could be a useful guide for other people.

COMPUTE UPGRADE: For compute my idea is to install a new compute node with centos 7 and juno. Then, with a “manual” script, i migrate instances from one icehouse node to the new node with juno upgrading the database. I tested this script, and if anyone is interested please send me an email. This step has downtime for instances because I have to scp the disk file from one compute node to another.

Finally, when all compute nodes are migrated, I can reinstall my 2 controllers in HA with pacemaker/corosync and I will be an happy openstack administrator :) Please, give me some suggestions. I upgrade openstack since grizzly and this is a complicated task! Thanks

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2016-06-21 14:07:54.096075


The version of OpenStack that this is opened against has been declared EOL as per http://releases.openstack.org/ Please open a new issue if you are still seeing this problem with a more recent, supported version of OpenStack. Thanks.

rbowen gravatar imagerbowen ( 2016-06-21 14:07:49 -0600 )edit