Control Center 1.8.0
This page describes the changes in Control Center since release 1.7.0.
Beginning with version 1.4.0, Docker images for Control Center are no longer available on Docker Hub. The images are included in self-installing archive files that are available for download from Zenoss. Likewise, the RPM packages that are required for installations and upgrades are no longer available from Zenoss repositories on the internet, and must be downloaded. However, the Docker images and RPM packages for previous releases are still available from Docker Hub and Zenoss repositories, respectively.
Beginning 1 December 2017, downloads for Zenoss Service Dynamics customers are available on delivery.zenoss.io.
For more information about Control Center operating environments, see Tested operating environments.
This release includes the following internal security and reliability updates:
- The Elasticsearch internal service is updated to release 7.7.1.
- The Zookeeper internal service is updated to release 3.5.5.
servicedbinary is now built with Go 1.14.
- The Go client library for Docker is updated.
In addition, Docker CE is updated to release 19.03.
Finally, this release includes a new configuration variable, SERVICED_LOGSTASH_STDOUT.
This update removes the historical data of Control Center gauges from
serviced internal HBase database. Resource Manager users are not
affected because the data is copied to the Resource Manager database.
This update reserves the 1001:1001 user/group IDs for Elasticsearch. If they're already in use for another user/group, you may wish to change them to a new user/group ID before the update. Not changing them does not affect Control Center.
|Update documentation with Zookeeper security procedures
|Include supported OS versions and platforms in release notes
|The X-Content-Type-Options is not set to 'nosniff'
|Graphs display N/A after changing SERVICED_MUX_PORT
|Unable to start services after SERVICED_RPC_PORT is changed
|The serviced CLI does not return non-zero status codes on certain failures
|Available and used memory are calculated incorrectly
|Zookeeper nodes are vulnerable to attack because ACLs are not enabled
|The Elasticsearch internal service consumes CPU and memory resources, stop responding to requests
|Permissions on files for internal services cause failed security scans
|The IDs of deleted images are not removed from Elasticsearch
The self-signed security certificate that is included in Control Center has expired. Workaround:
|VIP zookeeper data can get in to an inconsistent state