Ask Your Question
0

ocata to pike upgrade

asked 2017-09-15 16:17:31 -0500

jep gravatar image

I'd like to attempt an upgrade from Ocata to Pike soon, and I was wondering if anybody here has any experience to share. Any success or failure story, or general advise would be welcome :) My setup is fairly basic: Keystone, Horizon, Neutron, Glance, Nova, Cinder, Swift

edit retag flag offensive close merge delete

Comments

Hi Jep, I have recently managed very easily an upgrade from Mitaka to Newton. My cluster was running on a CentOS and I followed this: http://bit.ly/2ftuyc8 After stopping the services, I have enabled the Newton repos and disabled the Mitaka ones. Then upgraded the packets and restarting the service.

unusualfor gravatar imageunusualfor ( 2017-09-17 17:34:37 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2018-04-30 18:15:19 -0500

Hello everyone, I was able to update successfully.

Here are the steps:

UPDATE OPENSTACK VERSION OCETA FOR PIKE UBUNTU

UPDATE OF THE CONTROLLER Node

1) PAUSE ALL SERVICES service glance-registry stop service glance-api stop service nova-api stop service nova-conductor stop service nova-consoleauth stop service nova-novncproxy stop service nova-scheduler stop service neutron-server stop service neutron-linuxbridge-agent stop service neutron-dhcp-agent stop service neutron-metadata-agent stop service neutron-l3-agent stop service apache2 stop

2) REMOVE THE OCATA REPOSITORY add-apt-repository --remove cloud-archive:ocata

3) ADD THE PIKE REPOSITORY add-apt-repository cloud-archive:pike

4) UPDATE PACKAGES apt-get update apt-get upgrade

5) FORCED OPENSTACK PACKAGE UPDATE apt-get install list of all packages not installed

6) ACCEPT THE INSTALLATION AND SUB-SUBSTITUTION OF THE CONFIGURATION FILES (A COPY OF THE PRESENT CONFIGURATIONS SHALL BE MADE) Choose the option: Y

In my case, the substitute archives were:

/etc/nova/nova.conf /etc/keystone/keystone-paste.ini /etc/keystone/keystone.conf /etc/neutron/l3_agent.ini /etc/neutron/neutron.conf /etc/neutron/plugins/ml2/linuxbridge_agent.ini /etc/neutron/metadata_agent.ini /etc/neutron/dhcp_agent.ini /etc/neutron/plugins/ml2/ml2_conf.ini /etc/glance/glance-registry.conf /etc/glance/glance-api.conf /etc/openstack-dashboard/local_settings.py

Note: The old configuration files have an extension: .dpkg.conf

7) COMPARE THE SUBMITTED FILES OF ITEM 6, WITH THE FILES .dpkg.conf MAKING THE CHANGES NECESSARY

8) UPDATE DATA BANK su -s /bin/sh -c "keystone-manage token_flush" keystone su -s /bin/sh -c "keystone-manage db_sync" keystone su -s /bin/sh -c "glance-manage db_sync" glance su -s /bin/sh -c "nova-manage db sync" nova su -s /bin/sh -c "nova-manage api_db sync" nova su -s /bin/sh -c "neutron-db-manage upgrade heads" neutron su -s /bin/sh -c "nova-manage db online_data_migrations" neutron

9) REMOVING UNNECESSARY PACKAGES apt autoremove

10) RESET SYSTEM reboot

UPDATE NODES COMPUTER

1) PAUSE ALL SERVICES /etc/init.d/nova-compute stop /etc/init.d/neutron-linuxbridge-agent stop /etc/init.d/neutron-linuxbridge-cleanup stop /etc/init.d/ceilometer-agent-compute stop

2) REMOVE THE OCATA REPOSITORY add-apt-repository --remove cloud-archive:ocata

3) ADD THE PIKE REPOSITORY add-apt-repository cloud-archive:pike

4) UPDATE PACKAGES apt-get update apt-get upgrade

5) FORCED OPENSTACK PACKAGE UPDATE apt-get install list of all packages not installed

6) ACCEPT THE INSTALLATION AND SUB-SUBSTITUTION OF THE CONFIGURATION FILES (A COPY OF THE PRESENT CONFIGURATIONS SHALL BE MADE) School option: Y

In my case, the substitute archives were: /etc/libvirt/libvirtd.conf /etc/ceilometer/ceilometer.conf /etc/nova/nova.conf /etc/neutron/neutron.conf /etc/neutron/plugins/ml2/linuxbridge_agent.ini

7) COMPARE THE SUBMITTED FILES OF ITEM 6, WITH THE FILES .dpkg.conf MAKING THE CHANGES NECESSARY

9) REMOVING UNNECESSARY PACKAGES apt autoremove

10) RESET SYSTEM reboot

edit flag offensive delete link more
0

answered 2017-10-06 12:44:08 -0500

jep gravatar image

I finished the upgrade from Ocata to Pike, CentOS7, installed manually. I wanted to share the experience.

The basic upgrade procedure is pretty simple:

yum install centos-release-openstack-pike
yum-config-manager --disable centos-openstack-ocata
yum update

After that, updating the database for each service:

keystone-manage token_flush
keystone-manage db_sync 
glance-manage db_sync
cinder-manage db sync
nova-manage db sync
nova-manage api_db sync
neutron-db-manage upgrade heads
nova-manage db online_data_migrations 
cinder-manage db online_data_migrations

The issues I found after restarting:

1) The Horizon dashboard wouldn't open. You have to add "WSGIApplicationGroup %{GLOBAL}" to the top of /etc/httpd/conf.d/openstack-dashboard.conf to fix it

2) Swift logging in the default installation is going to local2 (old version was local0), so all my swift logs were landing on my /var/log/messages instead of /var/log/swift/swift.log. To fix it, edit /etc/rsyslog.d/openstack-swift.conf and change the rule to local0 instead of local2.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2017-09-15 16:17:31 -0500

Seen: 1,292 times

Last updated: Oct 06 '17