Installing and configuring compute node components

Once the Compute services have been configured on the controller node, at least one other host must be configured as a compute node. The compute node receives requests from the controller node to host virtual machine instances.

On the compute nodes, install the nova-compute package and related packages. These packages provide virtualization support services to the compute node:

    # apt install nova-compute

Update the Nova configuration file at /etc/nova/nova.conf on the compute nodes with the following Keystone-related settings:

[api]
...
auth_strategy= keystone

[keystone_authtoken]
...
auth_uri = http://controller01:5000
auth_url = http://controller01:35357
memcached_servers = controller01:11211
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
username = nova
password = nova 

Next, update the [DEFAULT] section of the Nova configuration file to configure Nova to use the RabbitMQ message broker:

[DEFAULT]
...
transport_url = rabbit://openstack:rabbit@controller01 

Then, update the Nova configuration file to provide remote console access to instances through a proxy on the controller node. The remote console is accessible through the Horizon dashboard. The IP configured as my_ip should be the respective management IP of each compute node.

Compute01:

[DEFAULT]
...
my_ip = 10.10.0.101

[vnc]
...
vncserver_proxyclient_address = 10.10.0.101
enabled = True
vncserver_listen = 0.0.0.0
novncproxy_base_url = http://controller01:6080/vnc_auto.html 

Compute02:

[DEFAULT]
...
my_ip = 10.10.0.102

[vnc]
...
vncserver_proxyclient_address = 10.10.0.102
enabled = True
vncserver_listen = 0.0.0.0
novncproxy_base_url = http://controller01:6080/vnc_auto.html 

Compute03:

[DEFAULT]
...
my_ip = 10.10.0.103

[vnc]
...
vncserver_proxyclient_address = 10.10.0.103
enabled = True
vncserver_listen = 0.0.0.0
novncproxy_base_url = http://controller01:6080/vnc_auto.html