You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This article summarizes the steps required to upgrade from the newton release to the queens release of openstack.

Prerequisites:

  • This documents expects that your cloud is deployed with the latest newton tag(vP.0.0) of the ntnuopenstack repository.
  • Your cloud is designed with one of the two architectures:
    • Each openstack project have their own VM(s) for their services
  • You have a recent mysql backup in case things go south.
  • If you want to do a rolling upgrade, the following key should be set in hiera long enough in advance that all hosts have had an puppet-run to apply it:

    • nova::upgrade_level_compute: 'pike'

VM-based architecture

If you use the VM based infrastructure you have the luxury of upgrading one service at a time and test that the upgrade works before doing the next service. This allows for ~zero downtime. If the services are redundantly deployed it is also very easy to do a rollback.

The recommended order to upgrade the services are listed below:

Keystone

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade (Which will fail)
  3. Purge the keystone package
  4. Run puppet again
  5. Perform the DB sync
    1. keystone-manage db_sync
  6. Restart apache2

Cinder

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. migrate the database
  4. Delete old cinder-services with the command "cinder-manage service remove <service> <host>"
    1. This applies for all services from the old controllers if they still exists, but also for the old cinder-volume services which are tied to a specific host.
  5. restart cinder services (including apache2!)
  6. Run puppet with the queens modules/tags
  7. restart cinder services (including apache2!)

Glance

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. Update the glance database schema
    1. glance-manage db sync
  4. restart glance services

Neutron

On the API node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. Migrate the database
    1. neutron-db-manage upgrade heads
  4. Restart neutron services

On the network node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. restart neutron services

Nova

On the API node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. Migrate the databases

    1. nova-manage api_db sync

    2. nova-manage db sync

  4. Restart services

On the services node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. Restart services

Heat

On the API node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. heat-manage db_sync
  4. restart heat services

On the engine node:

  1. Run puppet with the queens modules/tags
  2. Run apt-get dist-upgrade
  3. Restart heat-engine

Horizon

  1. Run puppet with the queens modules/tags
  2. run apt-get dist-upgrade
  3. Run puppet again
  4. restart apache2

Compute-nodes

When controllers etc. are upgraded, it is time to do the same on the comute-nodes. Compute nodes are simple to upgrade:

  1. Run puppet with the pike modules/tags
  2. Perform a dist-upgrade
  3. Run puppet again
  4. Restart openstack services
  • No labels