Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to install Compute service in openstack-mitaka

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

Share

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

This article is about how to install Compute services in openstack-mitaka. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Overview of Computing Services

Users OpenStack computing to host and manage cloud computing systems. OpenStack computing is an important part of basic as an Architecture Service (IaaS) system. The main module is implemented in Pthon.

OpenStack computing interacts with OpenStack authentication; OpenStack Image provides disk and server mirroring services; and OpenStack dashboard provides interface interaction for users. Access to images is limited by projects and users; quotas are limited by each project (such as the number of CVM instances). OpenStack computing can scale out the standard hardware and download the image to the launched CVM instance.

OpenStack computing consists of the following aspects and components:

Nova-api service

Accept and respond to end-user computing API calls. The service supports OpenStack computing API,Amazon EC2 API and a specific administrative API that performs administrative operations for privileged users. It enforces some policies and initiates most business process activities, such as running an instance.

Nova-api-metadata service

Accept metadata requests from CVM instances. When your OpenStack environment is installed in nova-network 's multi-node mode, nova-api-metadata services usually need to be used. For more details, please see the Metadata service manual.

Nova-compute service

A working daemon creates and terminates a virtual machine instance through the hypervisor API. For example:

L XenAPI for XenServer/XCP

L libvirt for KVM or QEMU

L VMwareAPI for Vmware

The treatment is quite complicated. Basically, the daemon accepts operations from the queue and executes a series of system commands, such as starting an instance of KVM and updating its status in the database.

Nova-scheduler service

Take a virtual machine instance request from the queue and make sure it is running on a computing server host.

Nova-conductor module

Mediate the interaction between nova-compute computing services and databases. It eliminates direct access to cloud databases made up of nova-compute services. The Noa-conductor module scales horizontally. However, do not deploy it on the node where the nova-compute service is running. For more information, Configuration Reference Guide.

Nova-cert module

A server daemon provides X509 certificate services for the Nova Cert service. Used to generate euca-bundle-image certificates. It is only used in EC2 API usage.

Nova-network worker daemon

Similar to the nova-compute service, it accepts network tasks from queues and operates the network. Perform tasks, such as setting up the Gela interface or changing Iptables rules.

Nova-consoleauth daemon

Provides an authorization token for the user console agent. Learn about See nova-novncproxy and nova-xvpvncproxy. This service must run in the work of the control agent. You can run two types of agents in a cluster configuration that configures a single nova-consoleauth service. For more information, see About nova-consoleauth.

Nova-novncproxy daemon

Provides proxies for accessing running CVM instances through VNC connections. Support for browser-based VNC clients.

Nova-spicehtml5proxy daemon

Provides proxies for accessing running CVM instances through SPICE connections. Support for browser-based HTML clients.

Nova-xvpvncproxy daemon

Provides proxies for accessing running CVM instances through VNC connections. Support is based on specific OpenStack java clients.

Nova-cert daemon

X509 certificate

Nova client

Allows the user to submit commands as an administrative or end user.

The queue

A central hub for message delivery before the daemon. It is usually implemented in RabbitMQ, but it can also be implemented in another AMQP message queue, such as ZeroMQ.

SQL database

Provides most compile-time and run-time state storage for cloud infrastructure, including:

L available instance types

L is using an instance

L available network

L project

In theory, OpenStack can support task databases supported by SQL-Alchemy. Common SQLite3 databases are used for testing and development work, MySQL, and PostgreSQL.

Install and configure the control node

The following steps describe how to install and configure computing services on the control node.

precondition

Before you can start installing and configuring mirroring services, you need to create a database, service credentials, and API endpoints.

1. Complete the database creation in the following steps:

Log in to the database with root account

Mysql-u root-p

L create nova_api and nova databases

CREATE DATABASE nova_api;CREATE DATABASE nova

L authorize the database

GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'localhost' IDENTIFIED BY' nova';GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'%' IDENTIFIED BY' nova';GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'localhost' IDENTIFIED BY' nova';GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' IDENTIFIED BY' nova'

L exit the database

two。 Load admin credential

. Admin-openrc

3. Create service credential

L create nova user

Openstack user create-domain default-password-prompt nova

L add admin roles to nova users

Openstack role add-project service-user nova admin

L create nova service entity

Openstack service create-name nova-description "OpenStack Compute" compute

4. Create nova service API endpoints

Openstack endpoint create-- region RegionOne compute public http://controller:8774/v2.1/%\(tenant_id\)s

Openstack endpoint create-- region RegionOne compute internal http://controller:8774/v2.1/%\(tenant_id\)s

Openstack endpoint create-- region RegionOne compute admin http://controller:8774/v2.1/%\(tenant_id\)s

Install and configure components

1. Install the package

Yum install openstack-nova-api openstack-nova-conductor openstack-nova-console openstack-nova-novncproxy openstack-nova-scheduler

two。 Edit the / etc/nova/nova.conf file to complete the following steps

L in [DEFAULT], configure to enable only computing and metadata API:

[DEFAULT]... enabled_apis = osapi_compute,metadata

L configure database access in the [api_database] and [database] sections

[api_database]... connection = mysql+pymysql://nova:nova@controller/nova_api

[database]... connection = mysql+pymysql://nova:nova@controller/nova

Configure RabbitMQ message queuing access in the [DEFAULT] and [oso_messaging_rabbit] sections

[DEFAULT]... rpc_backend = rabbit

[oslo_messaging_rabbit]... rabbit_host = controllerrabbit_userid = openstackrabbit_password = xxxxxxxx

Configure Identity service database access in [DEFAULT] and [keystone_authtoken]

[DEFAULT]... auth_strategy = keystone

[keystone_authtoken]... auth_uri = http://controller:5000auth_url = http://controller:35357memcached_servers = controller:11211auth_type = passwordproject_domain_name = defaultuser_domain_name = defaultproject_name = serviceusername = novapassword = nova

In the [DEFAULT] section, configure my_ip as the management interface IP address of the controller node

[DEFAULT]... My_ip = 192.168.213.81

L in the [DEFAULT] section, enable support for network services

[DEFAULT]... use_neutron = Truefirewall_driver = nova.virt.firewall.NoopFirewallDriver

In the [vnc] section, configure the VNC agent to use the controller node management interface IP address

[vnc]... vncserver_listen = $my_ipvncserver_proxyclient_address = $my_ip

L in the [glance] section, configure the location of the image service API

[glance]... api_servers = http://controller:9292

L in the [oslo_concurrency] section, configure the location of the image service API

[oslo_concurrency]... lock_path = / var/lib/nova/tmp

3. Populate the Compute database synchronously

# su-s / bin/sh-c "nova-manage api_db sync" nova# su-s / bin/sh-c "nova-manage db sync" nova

If you enter the following deprecation information, you can ignore

Complete the installation

1. Start the compute service and configure boot self-startup

Systemctl enable openstack-nova-api.service openstack-nova-consoleauth.service openstack-nova-scheduler.service openstack-nova-conductor.service openstack-nova-novncproxy.servicesystemctl start openstack-nova-api.service openstack-nova-consoleauth.service openstack-nova-scheduler.service openstack-nova-conductor.service openstack-nova-novncproxy.service installation and configuration of compute nodes

This section describes how to install and configure computing services on a compute node. The service supports several hypervisors to deploy instances or VMs. For simplicity, this configuration uses the QEMU hypervisor with KVM extension on the compute node, which should support hardware-accelerated virtual machines. On legacy hardware, this configuration uses a common QEMU hypervisor. You can follow these instructions to make minor changes to expand your environment and additional computing nodes horizontally.

Install and configure components

1. Install the package

Yum install openstack-nova-compute

two。 Edit the / etc/nova/nova.conf file to complete the following steps

In the [DEFAULT] and [oslo_messaging_rabbit] sections, configure RabbitMQ message queuing access:

[DEFAULT]... rpc_backend = rabbit

[oslo_messaging_rabbit]... rabbit_host = controllerrabbit_userid = openstackrabbit_password = RABBIT_PASS

Change RABBIT_PASS to the correct password

L configure access to Identity service in the [default] and [keystone_authtoken] sections

[DEFAULT]... auth_strategy = keystone

[keystone_authtoken]... auth_uri = http://controller:5000auth_url = http://controller:35357memcached_servers = controller:11211auth_type = passwordproject_domain_name = defaultuser_domain_name = defaultproject_name = serviceusername = novapassword = nova

L in the [default] section, configure my_ip

[DEFAULT]... my_ip = MANAGEMENT_INTERFACE_IP_ADDRESS

Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network interface of the compute node

L in the [default] section, open network service support

[DEFAULT]... use_neutron = Truefirewall_driver = nova.virt.firewall.NoopFirewallDriver

In the [vnc] section, configure access to the remote console

[vnc]... enabled = Truevncserver_listen = 0.0.0.0vncserver_proxyclient_address = $my_ipnovncproxy_base_url = http://controller:6080/vnc_auto.html

The server component listens for all IP addresses, while the proxy component listens for only the IP address of the management interface of the compute node. Base URL means that you can use a Web browser to access the location of the remote console of the instance on the compute node.

L in the [glance] section, configure the location of Image service API

[glance]... api_servers = http://controller:9292

L in the [oslo_concurrency] section, configure lock path

[oslo_concurrency]... lock_path = / var/lib/nova/tmp complete installation

1. Test whether the compute node supports hardware acceleration of virtual machines

Egrep-c'(vmx | svm)'/ proc/cpuinfo

If the return value of the command is greater than or equal to 1, your compute node supports hardware acceleration, which usually does not require additional configuration. If the command return value is 0 and your compute node does not support hardware acceleration, you must change the libvirt from KVM to QEMU.

L edit the / etc/nova/nova.conf file and modify the [libvirt] section as follows

[libvirt]... virt_type = qemu

two。 Start the service and set the boot self-boot

Systemctl enable libvirtd.service openstack-nova-compute.servicesystemctl start libvirtd.service openstack-nova-compute.service authentication operation

Execute the following command on the controller node

1. Load admin credential

. Admin-openrc

two。 Exemplify service components to verify the successful roll-out and registration of each process

Openstack compute service list

Note: the input should list the three service components started at the control node and one service component started at the compute node.

Thank you for reading! This is the end of the article on "how to install Compute Services in openstack-mitaka". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

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.

Views: 0

*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.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report