Stopping and starting nova services

Now that we have configured our OpenStack Compute installation, it’s time to start our services so that they’re running on both of our OpenStack Compute virtual machines (Controller and Compute), ready for us to launch our own private cloud instances.

Getting ready

If you haven’t done so already, ssh to our OpenStack controller and OpenStack Compute virtual machines. If you created these using Vagrant, you can log in to these using the following commands in separate shells:

vagrant ssh controller
vagrant ssh compute-01

This ensures that we can access our virtual machines, as we will need access to spin up instances from your personal computer. Let’s see the OpenStack services that we have running as part of our sandbox environments.

Controller

The following are the services:

• nova-api

• nova-objectstore

• nova-scheduler

• nova-conductor

• nova-cert

• nova-novncproxy

• nova-consoleauth

Compute

The following are the services:

• nova-compute

• nova-api-metadata

• nova-novncproxy

• libvirt-bin...