Added
- breaking change a9s KeyValue: We consider KeyValue8 as
stable
now. You have to set the following properties:- keyvalue_service.services.a9s-keyvalue8.name
- keyvalue_service.services.a9s-keyvalue8.guid
- keyvalue_service.services.a9s-keyvalue8.description
- keyvalue_service.services.a9s-keyvalue8.label
- keyvalue_service.services.a9s-keyvalue8.version
- keyvalue_service.services.a9s-keyvalue8.bindable
- keyvalue_service.services.a9s-keyvalue8.requires
- keyvalue_service.services.a9s-keyvalue8.tags
- keyvalue_service.services.a9s-keyvalue8.documentation_url
- keyvalue_service.services.a9s-keyvalue8.metadata
- keyvalue_service.services.a9s-keyvalue8.dashboard_client.id
- keyvalue_service.services.a9s-keyvalue8.plans
- keyvalue_service.services.a9s-keyvalue8.plans-to-test
- keyvalue_service.services.a9s-keyvalue8.planupdates-to-test
- a9s MariaDB: Add a9s-parachute2 BOSH release. For more information, see a9s Parachute v2.
- a9s MariaDB: Add plugins for a9s-parachute2 to the MariaDB BOSH releases.
- a9s Messaging: Add the WebSTOMP and WebMQTT plugins to a9s Messaging 4.0.
- docs: Application Developer: all services: Extend the Graphite Metrics documentation with a chapter about the a9s Parachute metrics. For more information, see Graphite Metrics - a9s Parachute Metrics.
- docs: Application Developer: a9s Messaging: Update documentation regarding the WebSTOMP and WebMQTT plugins. For more information, see Using a9s Messaging.
- docs: Platform Operator: a9s-pg: Add admonition recommending the execution of the
ANALYZE
command after migrating the running a9s-pg to a higher version, as this will ensure a better execution by updating the database's statistics. For more information, see a9s-pg Major Upgrade - Run the Upgrade. - docs: Platform Operator: a9s Messaging: Update the required ports for the a9s Messaging 4.0 Data Service. For more information, see a9s Platform Required Ports
- docs: Platform Operator: a9s Parachute: Add a page describing the a9s Parachute metrics. For more information, see a9s Parachute Metrics.
- docs: Platform Operator: a9s Parachute: Add documentation for a9s Parachute v2. For more information, see a9s Parachute v2.
Changed
- all services:
- bpm 1.4.8
- nginx v1.27.3
- routing 0.326.0
- all services: a9s DS API Gateway:
- KrakenD to v2.8.0
- krakend-custom-plugins to v2.8.0
- all services: a9s Service Broker: Adapt all delayed jobs to properly release their connections after termination.
- all services: a9s Service Broker: Fix mixed up
guid_at_tenant
anddeployment_name
in theinstance-information
script. - all services: a9s Service Dashboard: Update internal dependencies.
- all services: a9s Logstash: Integrate a9s Parachute metrics. For more information, see a9s Parachute Metrics.
- all services: a9s Smoke Tests: Extend
prometheus_streaming
tests with tests for a9s Parachute metrics. - all services: a9s Template Uploader Errand: Add a9s-parachute2 to the templates for a9s MariaDB 10.11.
- all services: a9s Template Uploader Errand: Extend the Logstash configuration with new configuration values for a9s Parachute metrics in the Service Instance templates. For more information, see Graphite Metrics - a9s Parachute Metrics.
- a9s KeyValue:
- a9s KeyValue 8:
- logstash v8.17.0
- a9s KeyValue 8:
- a9s KeyValue: Change Logstash to use
.txt
as the file extension for its logs. - a9s KeyValue: Update the
config/keyvalue.yml.example
to include more Service Plans. - a9s LogMe2: Change OpenSearch to use
.txt
as the file extension for its logs. - a9s Messaging:
- a9s Messaging 3.12:
- erlang to v25.3.2.16
- a9s Messaging 3.13:
- erlang to v26.2.5.6
- a9s Messaging 4.0:
- erlang to v26.2.5.6
- rabbitmq to v4.0.5
- logstash to v8.17.0
- a9s Messaging 3.12:
- a9s Messaging: Change Logstash to use
.txt
as the file extension for its logs. - a9s MongoDB:
- mongodb70sspl:
- mongodb to v7.0.16
- mongosh to v2.3.6
- mongodb70sspl:
- a9s PostgreSQL:
- a9s PostgreSQL:
- CMake to v3.31.3
- a9s PostgreSQL:
- a9s Prometheus: Update
graphite_mapping.conf
with the matching rules for the values of the a9s Parachute metrics. - a9s Prometheus:
prometheus2
:- grafana to v10.4.10
- a9s Search:
- logstash to v8.17.0
- a9s Search: Change Logstash to use
.txt
as the file extension for its logs. - a9s Search: Change OpenSearch to use
.txt
as the file extension for its logs. - docs: all services: Add Trademark to all mentions of Redis®* in documentation.
- docs: Application Developer: all services: Extend the list of cross reference links to include all a9s Data Services. For more information, see Graphite Metrics - Other Metrics.
- docs: Application Developer: a9s KeyValue: Add a caution admonition explaining the potential compatibility issues between a9s KeyValue and the Redis® client Libraries. For more information, see Using a9s KeyValue.
- docs: Application Developer: a9s Messaging: Add a caution admonition explaining syslog usage for RabbitMQ < 4.0. For more information, see a9s Messaging Syslog - Add a syslog Endpoint.
- docs: Application Developer: a9s PostgreSQL: Add admonition describing the restrictions of the CREATEROLE permission. For more information, see Using a9s PostgreSQL.
- docs: Application Developer: a9s Service Dashboard: Update examples and screenshots. For more information, see Using a9s Service Dashboard.
- docs: Platform Operator: all services: Add cross reference links to a9s Backup Monit and a9s Parachute metrics. For more information, see Metrics - Other Metrics.
- docs: Platform Operator: all services: Update a9s-pg Manual Logical Backup Recovery page to reflect the correct instruction for PostgreSQL v11 as well as v15. For more information, see: a9s-pg Manual Logical Backup Recovery - Recover Backup.
- docs: Platform Operator: all services: Fix typos and rephrase instructions for a better readability in a9s-pg Manual Logical Backup Recovery page. For more information, see: a9s-pg Manual Logical Backup Recovery.
- docs: Platform Operator: a9s Messaging: Update the a9s Messaging Vendor EOL dates. For more information, see a9s Platform Operator - Sunrise Sunset.
- docs: Platform Operator: a9s Parachute: Restructure the contents of the a9s Parachute documentation. For more information, see a9s Parachute.
- docs: Platform Operator: a9s PostgreSQL: Add admonition describing the restrictions of the CREATEROLE permission. For more information, see a9s PostgreSQL SPI Configuration.
- BOSH stemcell: all services: Update Jammy stemcell to version
1.682
for internal tests of all supported services.
Unsupported
a9s PostgreSQL: End of Support: Terminate support for the following deprecated a9s Data Service version:
- a9s PostgreSQL v11: PostgreSQL 11 is end-of-life by their vendor since November 2023
The creation of new a9s Data Service Instances for this deprecated version is now disabled by default in the a9s Data Service Bundle and we no longer provide regular support for this version. The corresponding documentation has been removed.
Although we will not intentionally break running Service Instances of this unsupported version, it cannot be guaranteed that they still work as expected after an update to this release.
a9s Prometheus: End of Support: Terminate support for the following deprecated a9s Data Service versions:
- a9s Prometheus Grafana 5: Grafana 5 is end-of-life by their vendor since May 2020
- a9s Prometheus Grafana 8: Grafana 8 is end-of-life by their vendor since June 2023
The creation of new a9s Data Service Instances for these deprecated versions is now disabled by default in the a9s Data Service Bundle and we no longer provide regular support for these versions. The corresponding documentation has been removed.
Although we will not intentionally break running Service Instances of these unsupported versions, it cannot be guaranteed that they still work as expected after an update to this release.
a9s Redis: End of Support: Terminate support for the following deprecated a9s Data Service version:
- a9s Redis v6.2: Redis 6.2 is end-of-life by their vendor since September 2023
The creation of new a9s Data Service Instances for this deprecated version is now disabled by default in the a9s Data Service Bundle and we no longer provide regular support for this version. The corresponding documentation has been removed.
Although we will not intentionally break running Service Instances of this unsupported version, it cannot be guaranteed that they still work as expected after an update to this release.
Removed
- docs: Platform Operator: a9s PostgreSQL: Remove a9s PostgreSQL 11 from the "a9s Data Service Release Lifecycle Table" page. For more information, see a9s Platform Operator Sunrise Sunset - a9s Data Services Life-Cycle Stages.
- docs: Platform Operator: a9s Redis: Remove a9s Redis 6.2 from the "a9s Data Service Release Lifecycle Table" page. For more information, see a9s Platform Operator Sunrise Sunset - a9s Data Services Life-Cycle Stages.
Fixed
- a9s KeyValue: Ensure Logstash uses the default Log4j2 config file from the vendor as the base configuration. This
change allows BOSH's
logrotate
and Log4j2 to properly rotate their assigned logs, instead of overlapping each other. - a9s LogMe2: Ensure OpenSearch uses the default Log4j2 config file from the vendor as the base configuration. This
change allows BOSH's
logrotate
and Log4j2 to properly rotate their assigned logs, instead of overlapping each other. - a9s Messaging: Ensure Logstash uses the default Log4j2 config file from the vendor as the base configuration. This
change allows BOSH's
logrotate
and Log4j2 to properly rotate their assigned logs, instead of overlapping each other. - a9s Messaging: Fix syslog configuration incompatibility between Logstash v6 and Logstash v8.
- a9s PostgreSQL: a9s PostgreSQL 15: Ensure that the lock directory (
/var/vcap/store/postgresql15-locks
) permissions are reset during updates. - a9s Search: Ensure Logstash uses the default Log4j2 config file from the vendor as the base configuration. This change
allows BOSH's
logrotate
and Log4j2 to properly rotate their assigned logs, instead of overlapping each other. - a9s Search: Ensure OpenSearch uses the default Log4j2 config file from the vendor as the base configuration. This
change allows BOSH's
logrotate
and Log4j2 to properly rotate their assigned logs, instead of overlapping each other.
Security
- a9s Service Dashboard: Fix CVEs:
- CVE-2024-21538
- CVE-2024-45296
- CVE-2024-45590
- CVE-2024-52798
Upcoming
a9s Messaging: Deprecation: Prepare for the upcoming deprecation phase, planned for the release v59.0.0 (expected end of March 2025), of the following a9s Data Service versions:
- a9s Messaging v3.12: RabbitMQ 3.12 is end-of-life by their vendor since June 2024
- a9s Messaging v3.13: RabbitMQ 3.13 is end-of-life by their vendor since Sept 2024
Please ensure that you organize the migration of your existing Service Instances to a more up-to-date version of the same a9s Data Service:
- for a9s Messaging v3.12: a9s Messaging v4.0 is available as GA version.
- for a9s Messaging v3.13: a9s Messaging v4.0 is available as GA version.
The deprecation phase is planned to last until v62.0.0 (expected end of June 2025), in which the unsupport phase of the deprecated versions will start. The creation of new a9s Data Service Instances for these particular versions will then be disabled by default in the a9s Data Service Bundle and we will not provide regular support for these versions. The corresponding documentation will also be removed. Therefore, we strongly recommend that you start your migrations to a supported GA version as soon as possible and complete them until the end of the deprecation phase. For more information, see a9s Platform Operator - Sunrise Sunset.
To inquire about extended support for a deprecated version, please get in contact with our sales department at sales@anynines.com.
a9s MySQL: End of Support: Terminate support, starting from anynines deployment v59.0.0 (expected end of March 2025), for the following deprecated a9s Data Service version:
- a9s MySQL v10.4: MySQL 10.4 is end-of-life by their vendor since June 2024
The creation of new a9s Data Service Instances for this deprecated version will be disabled by default in the a9s Data Service Bundle and we will not provide regular support for this version. The corresponding documentation will also be removed.
Although we will not intentionally break running Service Instances of this unsupported version, it cannot be guaranteed that they still work as expected after an update to v59.0.0.