OpenStack: Managing Nova Compute Nodes
Jump to navigation
Jump to search
- On server2-a, check OpenStack cloud services are running and registered:
[root@server2-a ~]# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth server2-a.example.com internal enabled :-) 2015-04-29 12:41:44
nova-scheduler server2-a.example.com internal enabled :-) 2015-04-29 12:41:44
nova-conductor server2-a.example.com internal enabled :-) 2015-04-29 12:41:44
nova-compute server2-a.example.com nova enabled :-) 2015-04-29 12:41:44
nova-cert server2-a.example.com internal enabled :-) 2015-04-29 12:41:43- On server2-b
[root@server2-b ~]# yum -y install openstack-nova-compute openstack-utils- On server2-b, backup conf & ini files and copy over replacements:
[root@server2-b ~]# cp /etc/nova/nova.conf /etc/nova/nova.conf.orig
[root@server2-b ~]# cd /etc/nova/
[root@server2-b nova]# scp server2-a:/etc/nova/nova.conf .
[root@server2-b nova]# scp server2-a:/etc/nova/api-paste.ini .- On server2-b, check ownership settings:
[root@server2-b nova]# chown root:nova /etc/nova/nova.conf /etc/nova/api-paste.ini
[root@server2-b nova]# chown -R nova:nova /var/log/nova- On server2-b, update nova.conf:
[root@server2-b nova]# crudini --set /etc/nova/nova.conf DEFAULT my_ip 172.25.2.11
[root@server2-b nova]# crudini --set /etc/nova/nova.conf DEFAULT vncserver_proxyclient_address \$my_ip
[root@server2-b nova]# crudini --set /etc/nova/nova.conf DEFAULT vncserver_listen 0.0.0.0
[root@server2-b nova]# crudini --set /etc/nova/nova.conf DEFAULT glance_host 172.25.2.10- On both server2-a and server2-b, update nova.conf:
crudini --set /etc/nova/nova.conf libvirt virt_type qemu- On server2-b, start services:
[root@server2-b nova]# systemctl start libvirtd
[root@server2-b nova]# systemctl start openstack-nova-compute
[root@server2-b nova]# grep ERROR /var/log/nova/nova-compute.log
[root@server2-b nova]# systemctl enable libvirtd
[root@server2-b nova]# systemctl enable openstack-nova-compute
ln -s '/usr/lib/systemd/system/openstack-nova-compute.service' '/etc/systemd/system/multi-user.target.wants/openstack-nova-compute.service'- On server2-a, check the new node is registered:
[root@server2-a ~]# nova-manage host list
host zone
server2-a.example.com internal
server2-b.example.com nova- On server2-a, check the running services
[root@server2-a ~]# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth server2-a.example.com internal enabled :-) 2015-04-29 12:57:54
nova-scheduler server2-a.example.com internal enabled :-) 2015-04-29 12:57:55
nova-conductor server2-a.example.com internal enabled :-) 2015-04-29 12:57:55
nova-compute server2-a.example.com nova enabled :-) 2015-04-29 12:57:54
nova-cert server2-a.example.com internal enabled :-) 2015-04-29 12:57:53
nova-compute server2-b.example.com nova enabled :-) 2015-04-29 12:57:56- Disable Nova compute services on server2-a:
[root@server2-a ~]# nova-manage service disable --host server2-a.example.com --service nova-compute
Service nova-compute on host server2-a.example.com disabled.- Verify:
[root@server2-a ~]# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth server2-a.example.com internal enabled :-) 2015-04-29 12:59:45
nova-scheduler server2-a.example.com internal enabled :-) 2015-04-29 12:59:45
nova-conductor server2-a.example.com internal enabled :-) 2015-04-29 12:59:45
nova-compute server2-a.example.com nova disabled :-) 2015-04-29 12:59:54
nova-cert server2-a.example.com internal enabled :-) 2015-04-29 12:59:54
nova-compute server2-b.example.com nova enabled :-) 2015-04-29 12:59:46