In a fairly hack and slash fashion, remove the installation of placement from the nova install docs. Placement will have its own installation docs. Configuring access to placement from the controller and compute nodes is still described. The depends-on is to the patch that provides placement install docs. The output of 'nova-status upgrade check' is updated to reflect the current state of the output of that command; this means it now includes a fair bit more than checking cells v2 and the existence of the placement API. Depends-On: https://review.openstack.org/#/c/628220/ Change-Id: I9e082a9c6d4b6369f1ec6c17bbd3ccc417a5e97b
14 KiB
Install and configure controller node for openSUSE and SUSE Linux Enterprise
This section describes how to install and configure the Compute service, code-named nova, on the controller node.
Prerequisites
Before you install and configure the Compute service, you must create databases, service credentials, and API endpoints.
To create the databases, complete these steps:
Use the database access client to connect to the database server as the
rootuser:$ mysql -u root -pCreate the
nova_api,nova, andnova_cell0databases:MariaDB [(none)]> CREATE DATABASE nova_api; MariaDB [(none)]> CREATE DATABASE nova; MariaDB [(none)]> CREATE DATABASE nova_cell0;Grant proper access to the databases:
MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'localhost' \ IDENTIFIED BY 'NOVA_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova_api.* TO 'nova'@'%' \ IDENTIFIED BY 'NOVA_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'localhost' \ IDENTIFIED BY 'NOVA_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' \ IDENTIFIED BY 'NOVA_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova_cell0.* TO 'nova'@'localhost' \ IDENTIFIED BY 'NOVA_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON nova_cell0.* TO 'nova'@'%' \ IDENTIFIED BY 'NOVA_DBPASS';Replace
NOVA_DBPASSwith a suitable password.Exit the database access client.
Source the
admincredentials to gain access to admin-only CLI commands:$ . admin-openrcCreate the Compute service credentials:
Create the
novauser:$ openstack user create --domain default --password-prompt nova User Password: Repeat User Password: +---------------------+----------------------------------+ | Field | Value | +---------------------+----------------------------------+ | domain_id | default | | enabled | True | | id | 8a7dbf5279404537b1c7b86c033620fe | | name | nova | | options | {} | | password_expires_at | None | +---------------------+----------------------------------+Add the
adminrole to thenovauser:$ openstack role add --project service --user nova adminNote
This command provides no output.
Create the
novaservice 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:
$ openstack endpoint create --region RegionOne \ compute public http://controller:8774/v2.1 +--------------+-------------------------------------------+ | Field | Value | +--------------+-------------------------------------------+ | enabled | True | | id | 3c1caa473bfe4390a11e7177894bcc7b | | interface | public | | region | RegionOne | | region_id | RegionOne | | service_id | 060d59eac51b4594815603d75a00aba2 | | service_name | nova | | service_type | compute | | url | http://controller:8774/v2.1 | +--------------+-------------------------------------------+ $ openstack endpoint create --region RegionOne \ compute internal http://controller:8774/v2.1 +--------------+-------------------------------------------+ | Field | Value | +--------------+-------------------------------------------+ | enabled | True | | id | e3c918de680746a586eac1f2d9bc10ab | | interface | internal | | region | RegionOne | | region_id | RegionOne | | service_id | 060d59eac51b4594815603d75a00aba2 | | service_name | nova | | service_type | compute | | url | http://controller:8774/v2.1 | +--------------+-------------------------------------------+ $ openstack endpoint create --region RegionOne \ compute admin http://controller:8774/v2.1 +--------------+-------------------------------------------+ | Field | Value | +--------------+-------------------------------------------+ | enabled | True | | id | 38f7af91666a47cfb97b4dc790b94424 | | interface | admin | | region | RegionOne | | region_id | RegionOne | | service_id | 060d59eac51b4594815603d75a00aba2 | | service_name | nova | | service_type | compute | | url | http://controller:8774/v2.1 | +--------------+-------------------------------------------+
Install and configure components
Note
As of the Newton release, SUSE OpenStack packages are shipped with
the upstream default configuration files. For example,
/etc/nova/nova.conf has customizations in
/etc/nova/nova.conf.d/010-nova.conf. While the following
instructions modify the default configuration file, adding a new file in
/etc/nova/nova.conf.d achieves the same result.
Install the packages:
Note
nova-consoleauthis deprecated since 18.0.0 (Rocky) and will be removed in an upcoming release. Console proxies should be deployed per cell. If performing a fresh install (not an upgrade), then you likely do not need to install thenova-consoleauthservice. See :oslo.configworkarounds.enable_consoleauthfor details.# zypper install openstack-nova-api openstack-nova-scheduler \ openstack-nova-conductor openstack-nova-consoleauth \ openstack-nova-novncproxy iptablesEdit the
/etc/nova/nova.conffile and complete the following actions:In the
[DEFAULT]section, enable only the compute and metadata APIs:[DEFAULT] # ... enabled_apis = osapi_compute,metadataIn the
[api_database]and[database]sections, configure database access:[api_database] # ... connection = mysql+pymysql://nova:NOVA_DBPASS@controller/nova_api [database] # ... connection = mysql+pymysql://nova:NOVA_DBPASS@controller/novaReplace
NOVA_DBPASSwith the password you chose for the Compute databases.In the
[DEFAULT]section, configureRabbitMQmessage queue access:[DEFAULT] # ... transport_url = rabbit://openstack:RABBIT_PASS@controllerReplace
RABBIT_PASSwith the password you chose for theopenstackaccount inRabbitMQ.In the
[api]and[keystone_authtoken]sections, configure Identity service access:[api] # ... auth_strategy = keystone [keystone_authtoken] # ... auth_url = http://controller:5000/v3 memcached_servers = controller:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = nova password = NOVA_PASSReplace
NOVA_PASSwith the password you chose for thenovauser in the Identity service.Note
Comment out or remove any other options in the
[keystone_authtoken]section.In the
[DEFAULT]section, configure themy_ipoption to use the management interface IP address of the controller node:[DEFAULT] # ... my_ip = 10.0.0.11In the
[DEFAULT]section, enable support for the Networking service:[DEFAULT] # ... use_neutron = true firewall_driver = nova.virt.firewall.NoopFirewallDriverNote
By default, Compute uses an internal firewall driver. Since the Networking service includes a firewall driver, you must disable the Compute firewall driver by using the
nova.virt.firewall.NoopFirewallDriverfirewall driver.Configure the
[neutron]section of /etc/nova/nova.conf. Refer to theNetworking service install guide <install/controller-install-obs.html#configure-the-compute-service-to-use-the-networking-service>for more details.In the
[vnc]section, configure the VNC proxy to use the management interface IP address of the controller node:[vnc] enabled = true # ... server_listen = $my_ip server_proxyclient_address = $my_ipIn the
[glance]section, configure the location of the Image service API:[glance] # ... api_servers = http://controller:9292In the
[oslo_concurrency]section, configure the lock path:[oslo_concurrency] # ... lock_path = /var/run/novaIn the
[placement]section, configure access to the Placement service:[placement] # ... region_name = RegionOne project_domain_name = Default project_name = service auth_type = password user_domain_name = Default auth_url = http://controller:5000/v3 username = placement password = PLACEMENT_PASSReplace
PLACEMENT_PASSwith the password you choose for theplacementservice user created when installingPlacement <install/>. Comment out or remove any other options in the[placement]section.
Populate the
nova-apidatabase:# su -s /bin/sh -c "nova-manage api_db sync" novaNote
Ignore any deprecation messages in this output.
Register the
cell0database:# su -s /bin/sh -c "nova-manage cell_v2 map_cell0" novaCreate the
cell1cell:# su -s /bin/sh -c "nova-manage cell_v2 create_cell --name=cell1 --verbose" nova 109e1d4b-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 | +-------+--------------------------------------+
Finalize installation
Start the Compute services and configure them to start when the system boots:
# systemctl enable openstack-nova-api.service \ openstack-nova-consoleauth.service openstack-nova-scheduler.service \ openstack-nova-conductor.service openstack-nova-novncproxy.service # systemctl start openstack-nova-api.service \ openstack-nova-consoleauth openstack-nova-scheduler.service \ openstack-nova-conductor.service openstack-nova-novncproxy.serviceNote again that the
nova-consoleauthservice may not be necessary here.