- Issued:
- 2021-02-23
- Updated:
- 2021-02-23
RHEA-2021:0649 - Product Enhancement Advisory
Synopsis
Release of components for Service Telemetry Framework 1.2 - Operator Container
Type/Severity
Product Enhancement Advisory
Topic
Release of the distribution component and the service-telemetry-operator-container component for the Service Telemetry Framework 1.2 - Operator Container
Description
Service Telemetry Framework (STF) provides automated collection of measurements and data from remote clients, such as Red Hat OpenStack Platform or third-party nodes. STF then transmits the information to a centralized, receiving Red Hat OpenShift Container Platform (OCP) deployment for storage, retrieval, and monitoring.
Release of Service Telemetry Framework 1.2 provides these changes:
Changes to the distribution component:
When you use Service Telemetry Framework (STF) 1.2 with Red Hat OpenStack Platform (RHOSP) 16.1.3 or later, you can now monitor OpenStack services, such as Horizon, Ceph, Nova, and Ceilometer. An example implementation of this is shown in the STF dashboards provided at https://github.com/infrawatch/dashboards/blob/master/deploy/rhos-cloud-dashboard.yaml within the Service Resource Usage panel. (BZ#1763711)
Changes to the service-telemetry-operator-container component:
Previously, invalid storage templates resulted in the inability to set custom storageClass parameter for OpenShift Container Platform (OCP). With this release, the ability to set custom storage parameters means that you can use STF with non-default storageClasses in OCP, such as OpenShift Container Storage (OCS). (BZ#1901609)
Service Telemetry Framework 1.2 provides a new parameter to allow specification of the retention period for metrics storage in the metrics storage backend, Prometheus. The default value remains at 24h (24 hours) but you can edit the value in the ServiceTelemetry manifest through the backends.metrics.prometheus.storage.retention parameter. (BZ#1915948)
Previously, a Service Telemetry Framework (STF) deployment enabled the AMQ Interconnect web interface by default with no ability to turn it off, which increased the attack surface of an STF instance unnecessarily.
Now the AMQ Interconnect web interface is disabled by default. It can be enabled by an administrator by using a new configuration option. (BZ#1915944)
Solution
The Service Telemetry Framework container image provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog (see References).
Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally.
Affected Products
- Red Hat OpenStack 1 x86_64
Fixes
- BZ - 1763711 - [CLOUDOPS] STF Metric Request - Component Metrics in STF Dashboards
- BZ - 1901609 - storageResources settings for Prometheus and Alertmanager have no effect
- BZ - 1915944 - Don't expose Interconnect web console by default
- BZ - 1915948 - Add retention parameter for backends.metrics.prometheus.storage
- BZ - 1924355 - Service Telemetry Operator fails to retrieve ElasticSearch BasicAuth information from Secret
CVEs
(none)
References
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.