OpenStack stein installation (VI) nova on compute 01/19 Update SLTechnology News&Howtos

OpenStack stein installation (VI) nova on compute

2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Shulou(Shulou.com)06/02 Report--

Install and configure componentsInstall the packages:# yum install openstack-nova-compute

Edit the / etc/nova/nova.conf file and complete the following actions:

○ In the [DEFAULT] section, enable only the compute and metadata APIs: [DEFAULT] #... Enabled_apis = osapi_compute,metadata ○ In the [DEFAULT] section, configure RabbitMQ message queue access: [DEFAULT] #... Transport_url=rabbit://openstack:openstack123@dbs.flex.net ○ In the [api] and [keystone_authtoken] sections, configure Identity service access:: [api] #... Auth_strategy = keystone [keystone_authtoken] #... Auth_url = http://stack.flex.net:5000/v3 memcached_servers = dbs.flex.net:11211 auth_type = password project_domain_name = Default user_domain_name = Default project_name = service username = nova password = nova123 Note: comment or remove other options ○ In the [DEFAULT] section, configure the my_ip option: [DEFAULT] # in the [keystone_authtoken] area. My_ip = 192.168.205.187 Note: use the IP of the management interface on your computing node. ○ In the [DEFAULT] section, enable support for the Networking service: [DEFAULT] #. Use_neutron = true firewall_driver = nova.virt.firewall.NoopFirewallDriver Note: by default, compute nodes use an internal firewall driver, because the network service includes a firewall driver, you must disable the firewall driver and use nova.virt.firewall.NoopFirewallDriver firewall driver ○ In the [vnc] section, enable and configure remote console access: [vnc] #. Enabled = true server_listen = 0.0.0.0 server_proxyclient_address = $my_ip novncproxy_base_url = the http://stack.flex.net:6080/vnc_auto.html server component listens for all IP addresses, and the proxy component listens for only the management interface IP address of the compute node. The basic URL indicates the location where the remote console of the instance on this compute node can be accessed using a web browser. Note: if the web browser that wants to access the remote console resides on a host that cannot resolve the controller hostname, the controller must be replaced with the management interface IP address of the controller node. ○ In the [glance] section, configure the location of the Image service API: [glance] #... Api_servers = http://stack.flex.net:9292 ○ In the [oslo_concurrency] section, configure the lock path: [oslo_concurrency] #... Lock_path = / var/lib/nova/tmp ○ In the [placement] section, configure the Placement API: [placement] #... Region_name = RegionOne project_domain_name = Default project_name = service auth_type = password user_domain_name = Default auth_url = http://stack.flex.net:5000/v3 username = placement password = placement123Finalize installation

Determine whether your compute node supports hardware acceleration for virtual machines:

$egrep-c'(vmx | svm)'/ proc/cpuinfo if this command returns a value of 1 or greater, your compute node supports hardware acceleration and usually does not require additional configuration. Usually, if your compute node uses a Vmware Workstation virtual machine, you can allow virtuallze Intel VT-x/EPT or AMD-V/RVI to turn on the virtualization setting. If this command returns a value of 0, your compute node does not support hardware acceleration. And you must configure libvirt to use QEMU instead of KVM, and edit the file / etc/nova/nova.conf file as follows: [libvirt] #... virt_type = qemu

Start the Compute service including its dependencies and configure them to start automatically when the system boots:

The error message on controller:5672, the AMQP server is not accessible, which may indicate that the firewall on the controller node is blocking access to port 5672. Configure the firewall to open port 5672 on the controller node and restart the nova-compute service on the compute node. Add the compute node to the cell database

Source the admin credentials to enable admin-only CLI commands, then confirm there are compute hosts in the database:

Discover compute hosts:

# su-s / bin/sh-c "nova-manage cell_v2 discover_hosts-- verbose" novaFound 2 cell mappings.Skipping cell0 since it does not contain hosts.Getting compute nodes from cell 'cell1': ad5a5985-a719-4567-98d8-8d148aaae4bcFound 1 computes in cell: ad5a5985-a719-4567-98d8-8d148aaae4bcChecking host mapping for compute host' compute': fe58ddc1-1d65-4f87-9456-bc040dc106b3Creating host mapping for compute host 'compute': fe58ddc1-1d65-4f87-9456-bc040dc106b3 Note: when you add new compute nodes You must run nova-manage cell_v2 discover_hosts to register the new compute node on the controller. Instead, you can set an appropriate interval in / etc/nova/nova.conf to automatically discover the compute node: [scheduler] discover_hosts_in_cells_interval = 300Verify operation

Verify operation of the Compute service.

Note: Perform these commands on the controller node.

Source the admin credentials to gain access to admin-only CLI commands:$. Admin-openrc

List service components to verify successful launch and registration of each process:

List images in the Image service to verify connectivity with the Image service:

Check the cells and placement API are working successfully and that other necessary prerequisites are in place:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.