OpenStack stein installation (5) nova on controller 01/18 Update SLTechnology News&Howtos

OpenStack stein installation (5) nova on controller

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

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

uses OpenStack computing to host and manage cloud computing systems. OpenStack computing is an important part of Infrastructure as a Service (IaaS) system. The main module is implemented in Python.

OpenStack computing interacts with the OpenStack identity for authentication, OpenStack placement for resource directory tracking and selection, OpenStack image services for disk and server images, and OpenStack dashboards for user and administrative interfaces. Image access is limited by projects and users; the quota for each project is limited (for example, the number of instances). OpenStack computing can scale horizontally on standard hardware and download the image to start the instance.

OpenStack calculations include the following components:

Nova-api service

Accept and respond to end user compute API calls. The service supports OpenStack computing API. It enforces some policies and initiates most orchestration activities, such as running an instance. Nova-api-metadata service

Accept metadata requests from the instance. When using the nova-network installation to run in multi-host mode, the nova-api-metadata service is typically used. Nova-compute service

A working daemon that creates and terminates virtual machine instances through the hypervisor api. For example: XenAPI for XenServer/XCPlibvirt for KVM or QEMUVMwareAPI for VMware

The processing is quite complicated. Basically, the daemon accepts the operations in 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

Get a virtual machine instance request from the queue and determine which compute server host it is running on. Nova-conductor module

Coordinate the interaction between nova-compute services and databases. It eliminates the direct access of nova-compute services to cloud databases. The nova-conductor module scales horizontally. However, do not deploy it on the node where the nova-compute service is running. Nova-consoleauth daemon

The user authorization token provided to the console agent. See nova-novncproxy and nova-xvpvncproxy. For the console agent to work, you must run this service. You can run both types of proxies against a single nova-consoleauth service in a cluster configuration. Nova-novncproxy daemon

Provides a proxy for accessing a running instance over a VNC connection. Support for browser-based novnc clients. Nova-spicehtml5proxy daemon

Provides a proxy for accessing a running instance over a SPICE connection. Support for browser-based HTML5 clients. Nova-xvpvncproxy daemon

Provides a proxy for accessing a running instance over a VNC connection. Support for openstack-specific Java clients. The queue

A central hub used to pass messages between daemons. It is usually implemented in RabbitMQ, but you can also implement SQL database with another AMQP message queue.

Stores most of the build-time and runtime state of the cloud infrastructure, including: Available instance typesInstances in useAvailable networksProjects

In theory, OpenStack computing can support any database supported by SQLAlchemy. The common databases for testing and development are SQLite3, MySQL, MariaDB, and PostgreSQL.

Preparatory work

We need to build the library, account and api endpoint before installing.

Perform the following steps on the database server: ○ uses root to connect to the database server: $mysql-u root-p root123 ○ to establish nova_api, nova and nova_cell0 databases: MariaDB [(none)] > CREATE DATABASE nova_api; MariaDB [(none)] > CREATE DATABASE nova; MariaDB [(none)] > CREATE DATABASE nova_cell0 ○ gives the account nova the right to operate on the library: MariaDB [(none)] > GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'%' IDENTIFIED BY' nova123'; MariaDB [(none)] > GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' IDENTIFIED BY' nova123'; MariaDB [(none)] > GRANT ALL PRIVILEGES ON nova_cell0.* TO 'nova'@'%' IDENTIFIED BY' nova123' load admin's access credentials and execute the administrator command: $. Admin-openrc

Establish the credentials for the computing service:

○ establishes nova user: $openstack user create-- domain default-- password-prompt nova User Password:nova123 Repeat User Password:nova123 +-- +-- + | Field | Value | +-+-+ | domain_id | default | | enabled | True | | id | | 8a7dbf5279404537b1c7b86c033620fe | | name | nova | | options | {} | | password_expires_at | None | +-- | -+ ○ add admin role to user nova: $openstack role add-- project service-- user nova admin Note: this command does not output ○ to establish a nova service entity: $openstack service create-- name nova-- description "OpenStack Compute" compute + -+ | Field | Value | +-+-+ | description | OpenStack Compute | | enabled | True | | id | 060d59eac51b4594815603d75a00aba2 | | name | nova | | type | compute | +-+-+ |

Create the Compute API service endpoints:

Edit the / etc/nova/nova.conf file to complete the following requirements:

○ is in the [DEFAULT] area, full of compute and metadata API: [DEFAULT] #. Enabled_apis = osapi_compute,metadata ○ at [api_database] and [database] sections, configure database access: [api_database] #... Connection = mysql+pymysql://nova:nova123@dbs.flex.net/nova_api [database] #... Connection = mysql+pymysql://nova:nova123@dbs.flex.net/nova ○ in the [DEFAULT] area, configure RabbitMQ message queuing access: [DEFAULT] #... Transport_url = rabbit://openstack:openstack123@dbs.flex.net ○ in the [api] and [keystone_authtoken] areas, configure the access authentication service: [api] #... Auth_strategy = keystone [keystone_authtoken] #... Auth_url = http://stack.flex.net:5000/v3 memcached_servers = dbs.flext.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 dropped in the [keystone_authtoken] area. ○ in the [DEFAULT] area, configure the IP of the management interface: [DEFAULT] #. My_ip = 192.168.207.2 # here is the management IP address of the control node ○ in the [DEFAULT] area, the supported network: [DEFAULT] #. Use_neutron = true firewall_driver = nova.virt.firewall.NoopFirewallDriver default, the compute node uses 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] zone, use the IP of the management interface as the vnc proxy: [vnc] enabled = true #. Server_listen = $my_ip server_proxyclient_address = $my_ip ○ in the [glance] area, configure the location of the image service api: [glance] #... Api_servers= http://stack.flex.net:9292 ○ in the [oslo_concurrency] area, configure the locked path: [oslo_concurrency] #... Lock_path = / var/lib/nova/tmp ○ in the [placement] area, configure to access the placement service: [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 = placement123 Note: comment or remove other options dropped in the [placement] area ○ due to a bug, you must allow access to placement API Add the following configuration to / etc/httpd/conf.d/00-nova-placement-api.conf: = 2.4 > Require all granted Order allow Deny Allow from all ○ Restart the httpd service: # systemctl restart httpdPopulate the nova-api database:# su-s / bin/sh-c "nova-manage api_db sync" novaRegister the cell0 database:# su-s / bin/sh-c "nova-manage cell_v2 map_cell0" novaCreate the cell1 cell:# su-s / bin/sh-c "nova-manage cell_v2 create_cell-name=cell1-verbose" nova109e1d4b-536a-40d0-83c6-5f121b82b650Populate the nova database : # su-s / bin/sh-c "nova-manage db sync" novaVerify nova cell0 and cell1 are registered correctly:# su-s / bin/sh-c "nova-manage cell_v2 list_cells" nova+-+--+ | Name | UUID | + -+ | cell1 | 109e1d4b-536a-40d0-83c6-5f121b82b650 | | cell0 | 00000000-0000-0000-0000-000000000000 | +-+-+ Ancheng installation ○ Allow the service to start automatically and start the service when the system boots: # systemctl enable openstack-nova-api.service\ openstack-nova-scheduler.service\ openstack-nova-conductor.service\ openstack-nova-novncproxy.service # systemctl start openstack-nova-api.service\ openstack-nova-scheduler.service\ openstack-nova-conductor.service\ openstack-nova-novncproxy.service

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.