Stopping the blueprint designer, cloud discovery service, and engine

To stop the blueprint designer and its associated services, you must stop the cloud discovery service, the blueprint design server, and the engine Heat services.

About this task

Depending on your system configuration, these components might be on different computers. Be sure to stop the cloud discovery service, the blueprint design server, and the engine Heat services on the correct computers.

Stopping the cloud discovery service

Procedure

Stop the cloud discovery service. On version 6.1.1.1 and later, the cloud discovery service is installed along with the blueprint design server.
  • On version 6.2.1.1 or later, on Linux systems that manage services with the systemd system manager, use the systemctl command:
    systemctl stop ibm-cloud-discovery.service
    Note: If you started the cloud discovery service with the systemctl command, you must use the systemctl command to stop the cloud discovery service.
  • On version 6.2.0.2 or later, run the following commands on the system that hosts the cloud discovery service:
    • On Linux:
      • Using the ps command, find the process IDs of the cloud discovery service:
        ps aux | grep -i -e "cloud" | grep -v "grep"
        For example, the output of the command might look like the following code:
        root      1218  0.0  1.5 319048 29932 ?        Sl   Dec08   0:00 /usr/bin/python /usr/bin/cloud-discovery-service
      • Using the kill command, stop the processes. For example:
        kill 1218
    • On Windows:
      • Using the Task Manager program, find the cloud-discovery-service process.
      • Right-click the cloud-discovery-service process and click End task.
  • On versions 6.1.1.1 through 6.2.0.1, run the following commands on the system that hosts the cloud discovery service:
    • On Linux:
      1. Using the ps command, find the process IDs of the cloud discovery service:
        ps aux | grep -i -e "runserver" 
        For example, the output of the command might look like the following code:
        root     24594  0.0  0.0  15088   744 pts/0    S    12:10   0:00 /opt/ibm-ucd-patterns/opt/udeploy-patterns-cloud-discovery-service/runserver
        root     24595  0.0  1.6 321092 31460 pts/0    Sl   12:10   0:00 /opt/ibm-ucd-patterns/opt/udeploy-patterns-cloud-discovery-service/runserver
        root     24699  0.0  0.0 103252   868 pts/0    S+   12:53   0:00 grep -i -e runserver
        In this case, the process IDs are 24594 and 24595.
      2. Using the kill command, stop the processes. For example:
        kill 24594 24595
    • On Windows:
      • Using the Task Manager program, find the runserver process.
      • Right-click the runserver process and click End task.
  • On versions prior to 6.1.1.1, run the following command on the system that hosts the cloud discovery service. By default, this is the same system that hosts the engine.
    stop everglade 

Stopping the blueprint design server

Procedure

Stop the blueprint design server:
server_installation_directory/bin/server stop
Use the server installation directory for server_installation_directory. The default installation directory is /opt/ibm-ucd-patterns on Linux and C:\Program Files\ibm-ucd-patterns on Windows. By default, the command looks like this code:
/opt/ibm-ucd-patterns/bin/server stop

Stopping the engine Heat services

Procedure

  1. Stop the Heat services.
    • For version 6.2.1.1 and later versions, which are compatible with RHEL 7, run the following commands:
      systemctl stop openstack-heat-engine.service
      systemctl stop openstack-heat-api.service
      systemctl stop openstack-heat-api-cfn.service
      systemctl stop openstack-heat-api-cloudwatch.service
    • For versions before 6.2.1.1, which are compatible with RHEL 6, run 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
  2. If you installed a Keystone server when you installed the engine, start it.
    • For version 6.2.1.1 and later versions, which are compatible with RHEL 7, run the following command:
      systemctl stop openstack-keystone.service
    • For versions before 6.2.1.1, which are compatible with RHEL 6, run the following command:
      service openstack-keystone stop

Feedback