Page History

...

• This documents expects that your cloud is deployed with the latest newton ocata tag(vO.0.0) of the ntnuopenstack repository.
• Your cloud is designed with one of the two architecturesarchitecture:
  
  • Each openstack project have their own VM(s) for their servicesAll openstack services is deployed on 3 physical controllers
• You have a recent mysql backup in case things go south.

...

1. Run puppet with the pike modules/tags
2. Run apt-get dist-upgrade
3. Run puppet with the pike modules/tags
4. Run cinder db sync
5. restart cinder services

Glance

1. Run puppet with the pike 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 ocata pike 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 ocata pike modules/tags
2. Run apt-get dist-upgrade
3. restart neutron services

Nova

On the API node:

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

   1. nova-manage api_db sync

   2. nova-manage db sync

4. Clean old services from the databse

   1. MariaDB [nova]> select host, version, topic, last_seen_up from services;
      1. Make sure that services with a version < 16 is not any services planned to be used.

   2. MariaDB [nova]> delete from services where version = 9;

   3. MariaDB [nova]> delete from services where version = 15;

5. Restart services

On the services node:

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

Heat

On the API node:

1. Run puppet with the pike 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 pike modules/tags

...

2. Run puppet with the pike modules/tags

Controller based architecture

On the controller-based architecture there is a lot less control of order etc. We are thus recommending the following approach:

...

1. apt-get dist-upgrade
2. Restart heat-engine

Horizon

...

1. Run puppet with the pike modules/tags
2. Perform a dist-upgrade
3. Sync databases
4. keystone-manage db_sync
5. cinder-manage db sync
6. glance-manage db syncneutron-db-manage upgrade head
7. nova-manage db sync
nova-manage api_db syncrun apt-get dist-upgrade
8. Run puppet again
9. Restart all services.
10. Verify successful upgrade
11. Upgrade the next two controllers, without step c: sync databases.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/tagsThis puppet-run will fail, but it will manage to do enough...
2. Perform a dist-upgrade
3. Run puppet again
4. Restart openstack services

...