Upgrading engines that you installed with IBM UrbanCode Deploy

To upgrade the engine, stop the related Heat services, install the new version, and restart the services. When you upgrade the engine, you must also upgrade the blueprint design server.

About this task

These steps are for engines that you installed with the IBM® UrbanCode™ Deploy installer in versions before 6.2.1.1. For all other engines, other processes apply:

To upgrade an engine from before 6.2.1.1 to version 6.2.1.1 or later, you must transfer the engine from a Red Hat Enterprise Linux version 6 server to a Red Hat Enterprise Linux version 7 server. See Migrating engines that you installed with IBM UrbanCode Deploy. If you do not want to migrate the engine, but you need access to the updated Heat types, extend your existing engine. See Extending Heat orchestration engines.
If you are upgrading an engine that is version 6.2.1.1 or later, use the instructions in Upgrading engines that you extended.
If you extended an existing engine as described in Extending Heat orchestration engines, use the instructions in Upgrading engines that you extended.

Procedure

Stop the cloud discovery service. See Stopping the blueprint designer, cloud discovery service, and engine.
Check to see whether the program rabbitmq-server is running:
```
service rabbitmq-server status
```
If the program rabbitmq-server is running, stop it:
```
service rabbitmq-server stop
```
Check to see whether the program qpidd is running:
```
service qpidd status
```
If the program qpidd is running, stop it:
```
service qpidd stop
```

Stop the Heat services by running the following commands:

service openstack-heat-engine stop

service openstack-heat-api stop

service openstack-heat-api-cfn stop

service openstack-heat-api-cloudwatch stop

If you installed a Keystone server along with the engine, stop it:
```
service openstack-keystone stop
```
Install the new version of the engine. See Installing engines.

Start the Heat services:

service openstack-heat-engine start

service openstack-heat-api start

service openstack-heat-api-cfn start

service openstack-heat-api-cloudwatch stop

If you installed a Keystone server when you installed the engine, start it by running the following command:
```
service openstack-keystone start
```
Start the cloud discovery service. See Starting the blueprint designer, cloud discovery service, and engine.

What to do next

A new file is in the /etc/heat/ folder. It is named /etc/heat/heat.conf.backup.n, where n is the largest numerical value for the present .backup files. You can still find the previous heat.conf files in this location.

If you installed a Keystone server with your engine, new files are in the /etc/keystone/ and /root/ folders. They are named /etc/keystone/keystone.conf.backup.n and /root/keystonerc.backup.n files, where n is the largest numerical value for the present .backup files. These files contain the new service token value for your Keystone server. You can still find the previous keystone.conf and keystonerc files in those locations. Similarly, the file ~/clientrc file is backed up.

Feedback