Here I only use the KXCOMPUTE1 node configuration as an example, the configuration of the other nodes is basically the same, except that the declared management IP is different. COMPUTE Nodes# Yum install openstack-nova-compute sysfsutils Modifying a configuration filevi/etc/nova/nova.conf [DEFAULT]Vcpu_pin_set = 4-31resume_guests_state_on_host_boot=truerpc_backend = Rabbitauth_strategy = Keystonemy_ip = 10.120.42.11 State_path=/home/local/nova Network_api_class = Nova.network.neutronv2.api.APISecurity_group_api = Neutronlinuxnet_interface_driver = Nova.network.linux_net.NeutronLinuxBridgeInterfaceDriverfirewall_driver = Nova.virt.firewall.NoopFirewallDriver verbose = True [Keystone_authtoken]Auth_uri = http://kxcontroller:5000Auth_url = http://kxcontroller:35357auth_plugin = passwordproject_domain_id = Defaultuser_domain_id = Defaultproject_name = Serviceusername = NovaPassword = Nova [VNC]enabled = TrueVncserver_listen = 0.0.0.0vncserver_proxyclient_address = $my _ipNovncproxy_base_url = http://kxcontroller:6080/vnc_auto.html [Glance]host = Kxcontroller [Oslo_concurrency]Lock_path =/var/lib/nova/tmp [Oslo_messaging_rabbit]Rabbit_host=kxcontrollerRabbit_userid = OpenStackRabbit_password = OpenStack [Neutron]url = http://kxcontroller:9696Auth_url = http://kxcontroller:35357auth_plugin = passwordproject_domain_id = Defaultuser_domain_id = Defaultregion_name = Regiontwoproject_name = Serviceusername = NeutronPassword = Neutron The above purple configuration is to wait with neutron when added, but here I put it in advance to do the global maintenance, if you are new environment, this purple configuration to install the neutron package and then add Create an Instance store directory, and Empowermkdir-p/home/local/novacp-r/var/lib/nova/*/home/local/nova/chown-r Nova:nova/home/local/nova start the service and join the bootsystemctl enable Libvirtd.service Openstack-nova-compute.servicesystemctl Restart Libvirtd.service openstack-nova-compute.service Log on to one of the Kxcontroller to verify: Source admin-openrc.sh # Nova Endpoints There are 9 endpoints services # Nova image-list to create a zone state example, on Kxcontroller of 1 nodes, it is important to note that when the Enterprise server resources are low, it is not recommended to classify compute nodes, because once the virtual machine is categorized and run, the virtual machine is migrated, resized, and can only be carried out within the original zone zone and cannot span the zone. Source admin-openrc.shView StatusNova Service-listNeutron agent-listNova Aggregate-listNova Availability-zone-listdefines the zone name, which defines 2Nova aggregate-create aggregate_prd_dm prd_dm_zoneNova aggregate-create aggregate_prd_um prd_um_zoneNova Host-list Nova aggregate-add-host aggregate_prd_um kxcompute1Nova aggregate-add-host aggregate_prd_um kxcompute2Nova aggregate-add-host aggregate_prd_um kxcompute3Nova aggregate-add-host aggregate_prd_um kxcompute4 Nova aggregate-add-host aggregate_prd_dm kxcompute5Nova aggregate-add-host aggregate_prd_dm kxcompute6Nova aggregate-add-host aggregate_prd_dm Kxcompute7Nova aggregate-add-host aggregate_prd_dm Kxcompute8Nova aggregate-add-host aggregate_prd_dm kxcompute9 Validation Nova Service-list+----+------------------+---------------+-------------+---------+-------+----------------------------+----- ------------+| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |+----+------------------+---------------+-------------+---------+-------+----------------------------+----- ------------+| 2 | nova-cert | kxcontroller2 | internal | enabled | up | 2016-11-08t11:30:37.000000 |- || 5 | nova-conductor | kxcontroller2 | internal | enabled | up | 2016-11-08t11:30:34.000000 |- || nova-consoleauth | kxcontroller2 | internal | enabled | up | 2016-11-08t11:30:33.000000 |- || | nova-scheduler | kxcontroller2 | internal | enabled | up | 2016-11-08t11:30:33.000000 |- || | nova-scheduler | kxcontroller1 | internal | enabled | up | 2016-11-08t11:30:35.000000 |- || nova-cert | kxcontroller1 | internal | enabled | up | 2016-11-08t11:30:38.000000 |- || | nova-consoleauth | kxcontroller1 | internal | enabled | up | 2016-11-08t11:30:35.000000 |- || nova-conductor | kxcontroller1 | internal | enabled | up | 2016-11-08t11:30:39.000000 |- || | nova-compute | kxcompute4 | prd_um_zone | enabled | up | 2016-11-08t11:30:37.000000 |- || nova-compute | kxcompute3 | prd_um_zone | enabled | up | 2016-11-08t11:30:36.000000 |- || nova-compute | kxcompute1 | prd_um_zone | enabled | up | 2016-11-08t11:30:37.000000 |- || | nova-compute | kxcompute2 | prd_um_zone | enabled | up | 2016-11-08t11:30:36.000000 |- || nova-compute | kxcompute6 | prd_dm_zone | enabled | up | 2016-11-08t11:30:37.000000 |- || nova-compute | kxcompute5 | prd_dm_zone | enabled | up | 2016-11-08t11:30:36.000000 |- || | nova-compute | kxcompute7 | prd_dm_zone | enabled | up | 2016-11-08t11:30:35.000000 |- || nova-compute | kxcompute8 | prd_dm_zone | enabled | up | 2016-11-08t11:30:35.000000 |- || | nova-compute | kxcompute9 | prd_dm_zone | enabled | up | 2016-11-08t11:30:36.000000 |- |+----+------------------+---------------+-------------+---------+-------+----------------------------+----- ------------+
SME OpenStack Private Cloud Deployment "11.1 Compute nova-compute node configuration (ke xing environment)"
