Page History

...

• This documents expects that your cloud is deployed with the latest newton tag(vN.1.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 ocata modules/tags
2. Run apt-get dist-upgrade
   1. If it fails, verify that /etc/mysql/my.cnf.fallback exists. If it doesnt, create it with the content "!includedir /etc/mysql/conf.d/"
   2. Keystone often have to be reinstalled; so "apt-get purge keystone" followed by a puppet-run fixes a lot
3. Run puppet again
4. Perform the DB sync
   1. keystone-manage db_sync
5. Restart keystone services

...

1. Run puppet with the ocata modules/tags
2. Run apt-get dist-upgrade
3. Run puppet again
4. Perform the DB sync
   1. novaheat-manage db syncnova-manage api_db sync
5. Restart heat services

...

1. Run puppet with the ocata modules/tags
2. Run apt-get dist-upgrade
3. Run puppet again

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. Stop puppet on all controllers, and stop all openstack services
2. Select one controller to be the first one to go:
   
   1. Run puppet with the ocata modules/tags
   2. Perform a dist-upgrade
   3. Sync databases
      1. keystone-manage db_sync
      2. cinder-manage db sync
      3. glance-manage db syncneutron-db-manage upgrade head
      4. nova-manage db sync
      5. nova-manage api_db sync
   4. Run puppet again
   5. Restart all services.
   6. Verify successful upgrade
3. Upgrade the next two controllers, without step c: sync databases.

Compute-nodes

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

...