The upgrade of the central database, a9s-pg, has completed and the API and related services are available again.
Posted Sep 19, 2024 - 16:23 CEST
Update
The upgrade of the central database, a9s-pg, begins around 14:30 and the maintenance downtime takes approximately 60 minutes starting once reaching the point of switching the cluster to the new version.
During the downtime, the following components are affected * CloudFoundry API and all related functionality like app and service instance management (create, update, delete) * Backup Service * App-Autoscaler
Apps and service instances continue to run in their current configuration.
Posted Sep 19, 2024 - 14:14 CEST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Sep 18, 2024 - 09:00 CEST
Scheduled
Dear Customer,
we are going to update the a9s platform during the scheduled timeframe.
Runtime: Upgrade of a9s-pg
There is a major change to the a9s-pg deployment. PostgreSQL gets an upgrade from v11 to v15. For more information, see a9s-pg Major Upgrade
Important
The in-place major version upgrade procedure has an inherent downtime. Creation, update and deletion of new or existing a9s Data Services instances during an a9s-pg upgrade will be unavailable for a certain period of time.
Cloud Native Buildpacks Lifecycle From CF community:
"Cloud Foundry recently introduced Cloud Native Buildpacks (CNBs), also known as v3 buildpacks. The Cloud Foundry Foundation already has an implementation of Cloud Native Buildpacks via the Paketo project, however these CNBs can't currently be used in CF. You can read more here .This RFC introduces a new optional lifecycle to Cloud Foundry which enables users to build their applications using Cloud Native Buildpacks."
Our test:
We tested it in our environment with spring-music app. When downloaded make sure to edit manifest.yml of an spring-music app as an example from here: Cloud Native Buildpacks Lifecycle adding this lines to manifest.yml of an spring-music app (after doing so , we need to cf push app).
a9s Messaging: End of Support: Terminate support, starting from anynines deployment v55.0.0 (expected end of November), for the following deprecated a9s Data Service versions: a9s Messaging 3.7 a9s Messaging 3.8
a9s PostgreSQL
Starting from anynines deployment v55.0.0 (expected end of November), for the following deprecated a9s Data Service version: a9s PostgreSQL 11
a9s Redis
a9s Redis: End of Support: Terminate support, starting from anynines deployment v55.0.0 (expected end of November), for the following deprecated a9s Data Service version: a9s Redis 5.0
The creation of new a9s Data Service instances for the deprecated versions will be disabled by default in the a9s data service bundle and we will not provide regular support for this versions. The corresponding documentation will also be removed.
To inquire about extended support for a deprecated version, please get in contact with our sales department at sales@anynines.com. Updated a9s Data Services Maintenance Policy
This document describes the a9s Data Services' release policies a9s Data Services Maintenance Policy
Information for Application Developer a9s MariaDB Adding new cluster-related metrics Some metrics may change between the MariaDB versions, therefore they might differ or not be available based on the MariaDB version that is currently running on the service instance. In order to be sure please check following documentation: MariaDB metric group
The update procedure is structured into 3 stages:
Stage 1: Update of the Runtime Stage 2: Update of the a9s Data Service Framework Stage 3: Update of all existing a9s Data Service instances
The stages have the following impact:
Stage 1: - Restart of all applications. For slow starting applications with a single instance configuration this might introduce a downtime of up to 5 minutes in addition to application startup time. - Restart of the API. Single requests to the API might fail but subsequent requests shall pass.
Stage 2: - Creation, update and deletion of new or existing a9s Data Services instances will be unavailable for up to 5 minutes. - The availability of existing a9s Data Service instances will not be affected by this.
Stage 3: - All a9s Data Service instances will be restarted which causes single instances to be not available for up to 5 minutes. - You may see your app reconnecting to the master node while the service instance gets updated.
We'll provide an update as soon as we finish the respective stage.
Best regards, The anynines Team
Posted Sep 13, 2024 - 11:07 CEST
This scheduled maintenance affected: API, Customer Panel, Services, and Website.