Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 9. Updating composable services and parameters
You must complete some composable service configuration to prepare for the overcloud upgrade.
9.1. Updating composable services in custom roles_data files
This section contains information about new and deprecated composable services.
-
If you use the default
roles_datafile, these services are included automatically. -
If you use a custom
roles_datafile, add the new services and remove the deprecated services for each relevant role.
If any overcloud nodes in your deployment are dedicated Object Storage (swift) nodes, you must copy the default roles_data.yaml file and edit ObjectStorage to remove the following line: deprecated_server_resource_name: 'SwiftStorage'
Controller nodes
The following services have been deprecated for Controller nodes. Remove them from your Controller role.
| Service | Reason |
|---|---|
|
| The OpenStack Telemetry services are deprecated in favour of Service Telemetry Framework (STF) for metrics and monitoring. The legacy telemetry services are only available in RHOSP 16.1 to help facilitate the transition to STF and will be removed in a future version of RHOSP. Note If you use auto scaling, do not remove these services from your Controller nodes. |
|
| The OpenStack Telemetry services are deprecated in favour of Service Telemetry Framework (STF) for metrics and monitoring. The legacy telemetry services are only available in RHOSP 16.1 to help facilitate the transition to STF and will be removed in a future version of RHOSP. Note If you use CloudForms, do not remove these services from your Controller nodes. |
|
| These services are no longer supported. Remove these services from your Controller nodes. |
|
| Congress is no longer supported. |
|
| This service is no longer supported due to OpenStack Platform Image Service (glance) API v2. |
|
| Deprecated plug-ins for OpenStack Networking (neutron). |
|
| OpenStack Networking (neutron) Load Balancing as a Service deprecated in favour of Octavia. |
|
| This service is removed. |
|
|
Deprecated in favor of |
|
| OpenDaylight is no longer supported. |
|
| This service has been substituted for two new services:
|
|
| Skydive is no longer supported. |
|
| Tacker is no longer supported. |
The following services are new for Controller nodes. Add them to your Controller role.
| Service | Reason |
|---|---|
|
| Tasks to enable Ceph Dashboard service. |
|
| New backends for Block Storage (cinder). |
|
| Run the commands to automatically pull and prepare container images relevant to the services in your overcloud. |
|
| Services for DNS-as-a-Service (designate). |
|
| Service for Bare Metal Introspection for the overcloud. |
|
| The networking agent for OpenStack Bare Metal (ironic). |
|
| Service for OpenStack Networking (neutron) agent for Mellanox InfiniBand. |
|
| Service for installing the Red Hat OpenStack Platform command line tools. |
|
|
Replacement services for the |
|
| Service for the Placement API. |
Compute Nodes
The following services have been deprecated for Compute nodes. Remove them from your Compute role.
| Service | Reason |
|---|---|
|
| OpenDaylight is no longer supported. |
|
| Skydive is no longer supported. |
The following services are new for Compute nodes. Add them to your Compute role.
| Service | Reason |
|---|---|
|
| Service to configure host aggregate and availability zone in OpenStack Compute (nova). |
All Nodes
The following services have been deprecated for all nodes. Remove them from all roles.
| Service | Reason |
|---|---|
|
| Replaced with Podman. |
|
|
Deprecated in favour of |
|
|
Deprecated in favour of |
|
| Deprecated service. |
|
|
Deprecated in favour of |
The following services are new for all nodes. Add them to all roles.
| Service | Reason |
|---|---|
|
| Service to set Kernel arguments, Tuned profiles, and CPU isolation. |
|
| Service to configure Collectd. |
|
| Provides a Multipathd service, which is disabled by default |
|
| Service to install and enable Podman. |
|
| Service to install and enable Relax-and-Recover (ReaR) backup and restore tools. |
|
| Service to configure centralized log collection. |
|
| Service to enable time synchronization method, which is Chronyd by default. |
9.2. Updating composable services in custom environment files
If you have any custom environment files with resource_registry sections, check the resource_registry sections for changes in composable service template mappings. The composable service files for Red Hat OpenStack Platform 16.1 reside in a new location within /usr/share/openstack-tripleo-heat-templates/:
| Red Hat OpenStack Platform 13 | Red Hat OpenStack Platform 16.1 |
|---|---|
|
|
|
The deployment directory contains a set of sub-directories to group composable services. For example, the keystone sub-directory contains composable service templates for OpenStack Identity (keystone).
To remap composable services in custom environment files, check the template location for the current service mapping and edit the mapping to the new location. This procedure uses ceph-mgr.yaml as an example.
This procedure acts as guidance only for remapping composable services. If you are unsure of any mapping, contact Red Hat and request advice on the correct mapping.
Procedure
Search for custom environment files that use composable services. You usually store custom environment files in the
/home/stack/templatesdirectory:$ cd ~/templates/ $ grep "OS::TripleO::Services" *In this scenario, one of the files shows an outdated mapping:
OS::TripleO::Services::CephMgr: /usr/share/openstack-tripleo-heat-templates/docker/services/ceph-ansible/ceph-mgr.yamlIdentify the new
ceph-mgr.yamllocation in/usr/share/openstack-tripleo-heat-templates/. This file is now located in the `deployment/ceph-ansible' directory:$ find /usr/share/openstack-tripleo-heat-templates/ -name ceph-mgr.yaml /usr/share/openstack-tripleo-heat-templates/deployment/ceph-ansible/ceph-mgr.yamlEdit the service in the custom environment file:
resource_registry: OS::TripleO::Services::CephMgr: /usr/share/openstack-tripleo-heat-templates/deployment/ceph-ansible/ceph-mgr.yamlSave the file.
9.3. Configuring access to the undercloud registry
To configure access to the undercloud registry, add the control plane host name of the undercloud and the IP address of the undercloud on the provisioning network to the DockerInsecureRegistryAddress parameter. Place this parameter in the containers-prepare-parameter.yaml file to ensure that the parameter is included in future overcloud deployments.
Procedure
-
Log in to the undercloud as the
stackuser. Obtain the control plane host name on the undercloud:
$ sudo hiera container_image_prepare_node_names ["undercloud.ctlplane.localdomain"]Edit the
containers-prepare-parameter.yamlfile and add theDockerInsecureRegistryAddressparameter with a YAML list that contains the control plane host name of the undercloud and the IP address of the undercloud on the provisioning network:parameter_defaults: DockerInsecureRegistryAddress: - undercloud.ctlplane.localdomain:8787 - 192.168.24.1:8787 ...You must also append the port number of the overcloud registry to the host name and IP address values. The port number is
8787.
9.4. Deprecated and removed filters for the NovaSchedulerDefaultFilters parameter
If your environment uses a custom NovaSchedulerDefaultFilters parameter, edit the parameter to remove the following deprecated and removed filters:
| Filter | Status |
|---|---|
|
| Deprecated |
|
| Deprecated |
|
| Deprecated |
|
| Removed |
|
| Removed |
|
| Removed |
|
| Removed |
|
| Removed |
|
| Removed |
|
| Deprecated |
Avoid using filters marked Deprecated. Red Hat OpenStack Platform 16.1 still includes deprecated filters but future versions of Red Hat OpenStack Platform will not include these filters.
9.5. Setting the Compute name format
Red Hat OpenStack Platform 13 uses %stackname%-compute-%index% as the default naming format for Compute nodes. Red Hat OpenStack Platform 16.1 uses %stackname%-novacompute-%index% as the default naming format for Compute nodes. Change the default naming format to retain the original Red Hat OpenStack Platform 13 naming format. If you do not use the original naming format, director configures new OpenStack Compute (nova) agents with the new naming format and keeps the existing OpenStack Compute (nova) agents with the old naming format as orphaned services.
Procedure
-
Log in to the undercloud as the
stackuser. Set the Compute naming format:
If you use a custom
roles_datafile, edit the customroles_datafile and set theHostnameFormatDefaultparameter for theComputerole:- name: Compute … HostnameFormatDefault: '%stackname%-compute-%index%' …Save the custom
roles_datafile.If you use the default
roles_datafile inopenstack-tripleo-heat-templates, set the naming format in an environment file. Edit the environment file with your node counts and flavors, which is usually namednode-info.yaml. Add theComputeHostnameFormatparameter to theparameter_defaultssection:parameter_defaults: … ComputeHostnameFormat: '%stackname%-compute-%index%' …Save the
node-info.yamlfile.
9.6. Configuring the instance serial number
In Red Hat OpenStack Platform 13, the serial number for instances stored in the virtual BIOS of the host machine is based on the serial number of the host.
In Red Hat OpenStack Platform 16.1, the serial number for instances stored in the virtual BIOS of the host machine is based on the UUID of the instance by default.
If you want to retain the behaviour of your Red Hat OpenStack Platform 13 deployment when you upgrade to Red Hat OpenStack Platform 16.1, you must configure [libvirt]sysinfo_serial.
Procedure
-
Log in to the undercloud as the
stackuser. Source the
stackrcfile:[stack@director ~]$ source ~/stackrc- Open an environment file.
Add the following configuration to your environment file to specify that the instance serial number is based on the serial number of the host:
parameter_defaults: <Role>ExtraConfig: nova::config::nova_config: libvirt/sysinfo_serial: value: auto- Save the updates to your environment file, and add the file to your overcloud upgrade and deployment commands.
9.7. Updating your SSL/TLS configuration
Remove the NodeTLSData resource from the resource_registry to update your SSL/TLS configuration.
Procedure
-
Log in to the undercloud as the
stackuser. Source the
stackrcfile:$ source ~/stackrc-
Edit your custom overcloud SSL/TLS public endpoint file, which is usually named
~/templates/enable-tls.yaml. Remove the
NodeTLSDataresource from the `resource_registry:resource_registry: OS::TripleO::NodeTLSData: /usr/share/openstack-tripleo-heat-templates/puppet/extraconfig/tls/tls-cert-inject.yaml …The overcloud deployment uses a new service in HAProxy to determine if SSL/TLS is enabled.
NoteIf this is the only resource in the
resource_registrysection of theenable-tls.yamlfile, remove the completeresource_registrysection.- Save the SSL/TLS public endpoint file file.
9.8. Updating post configuration templates
If you use the OS::TripleO::NodeExtraConfigPost resource to register and run a post-configuration template, you must add the EndpointMap parameter to the template.
Procedure
- Edit the post-configuration template.
Under the
parameterssection, add theEndpointMapparameter and its sub-parameters:parameters: servers: type: json nameserver_ip: type: string DeployIdentifier: type: string EndpointMap: default: {} type: json- Save the template.
9.9. Considerations when retaining legacy telemetry services
In Red Hat OpenStack Platform (RHOSP) 16.1, the OpenStack Telemetry components are deprecated in favor of the Service Telemetry Framework (STF), therefore the legacy telemetry components are not enabled after the upgrade.
If you use auto scaling or CloudForms services, you must retain the legacy telemetry services.
To retain legacy RHOSP 13 telemetry services, include the /usr/share/openstack-tripleo-heat-templates/environments/enable-legacy-telemetry.yaml environment file when you run the openstack overcloud upgrade prepare and openstack overcloud upgrade converge commands.
You must also include the enable-legacy-telemetry.yaml environment file every time you update the overcloud after the upgrade.
The legacy telemetry services are only available to help facilitate the transition to STF and will be removed in a future version of RHOSP.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}