Completed -
The scheduled maintenance has been completed.
Mar 29, 09:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 24, 09:00 CET
Scheduled -
Dear Customer,
we are going to update the a9s platform during the scheduled timeframe.
Data Services (e.g. removal, deprecation, unsupported, new services)
Upcoming
a9s RabbitMQ
End of support: Starting from anynines deployment v59.0.0 (expected end of March 2025), and it will be included in the next a9s release version v1.66.0 onwards (current is v1.65.0). We are deprecating the following a9s Data Service versions:
a9s Messaging v3.12: (RabbitMQ 3.12 is end-of-life by their vendor since 01 June 2024)
a9s Messaging v3.13: (RabbitMQ 3.13 is end-of-life by their vendor since 18 Sep 2024)
The deprecation phase is planned to last until anynines deployment v62.0.0 (expected end of June 2025), in which the unsupport phase of the deprecated versions will start. (we expect that it will be effective in upcoming a9s release version v1.68.0)
We advise you to organize the migration of existing Service Instances to more up-to-date versions of the same a9s Data Services. Starting from next upcoming a9s release version v1.66.0
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
Mar 14, 12:36 CET