How To Upgrade Your CoreMedia Content Cloud Version on CMCC-Service
Last updated a month ago
In CMCC-Service, software upgrades require activities by the customers and sometimes CoreMedia support. Learn when that applies and how to do it.
What you'll learn
- Learn how to differentiate between REQUIRED and OPTIONAL to-dos
- Understand the upgrade process in Content Cloud Service for the different CMCC version types.
Prerequisites
- CMCC-Service Account with a Development Sandbox, a Pre-Production and a Production environment.
Time matters
10 minutes
Should I read this?
This guide is for CMCC-Service customers, Developers, Administrators, and Project Managers.
Table of Contents
|
Is this guide relevant for me? This guide is intended for CMCC-Service customers. It describes the specific tasks for upgrading to a newer CMCC version, depending on the upgrade type. Please note: Only CMCC-Service-specific considerations are covered here. For the general concepts of versioning and upgrading, refer to this section. What upgrade types are covered? This guide covers: - AEP upgrades - Major AMP upgrades - Minor AMP upgrades For a detailed overview of CoreMedia’s release types and LTS strategy, see CoreMedia Release Cycle and LTS Strategy. When in doubt, feel free to reach out to your CoreMedia Customer Success Manager. |
1. Introduction
Customers of the CMCC-Service can deploy Minor AMP upgrades of CoreMedia Content Cloud independently, using the provided Self Service in the same way they deploy a customized CMCC Blueprint of the same version.
The new version can be deployed either through the Cloud Manager UI in the Deployment Self Service section (see Figure 1 below) or via the CMCC-S API.
For more information, refer to the CMCC-Service Manual available on your Cloud Manager dashboard.
When something goes wrong, you can always reach out to CoreMedia Support.
Upgrades to new AEP versions (e.g., from 2406.1.1 to 2412.0.0) or Major AMP versions (e.g., from 2406.0.3 to 2406.1.0) are not covered by the Self Service options. These upgrades require changes to the underlying infrastructure, which must be prepared by CoreMedia. In such cases, please contact CoreMedia Support for further assistance.
Figure 1. Deployment Self-Service in the Cloud Manager
2. Upgrading to a Newer Minor AMP Version
Before starting the code migration to the new software release, carefully review the release notes for the target version as well as for all versions between your current and new version. If you are unsure whether a release note affects your CMCC-Service setup, contact CoreMedia Support for clarification.
| Always check both the release notes for the target version and any intermediate versions to avoid missing important changes. |
The general upgrade process is described in this section.
Instructions for code migration are available in Upgrading with Git.
Phases & General Tasks During the Upgrade Process
-
Task 1: After completing the code migration, the first step is to build and deploy the new version on your Development Sandbox. Test all functionality as part of your regular development process. Pay special attention to bug fixes and/or new features provided with the release (in case there are any).
-
Task 2: After successful testing in the Development Sandbox, push the new version of CMCC to the Docker repository of your CMCC-Service account using the push pipeline in your Sandbox. The new release will then be available for deployment to Pre-Production or Production environments.
-
Task 3: Now deploy the new version (Docker container tag) on a Pre-Production environment (typically UAT) for further testing. Use either the Cloud Manager UI or an API call through the CMCC-Service API.
-
Task 4: Complete your defined quality assurance process and formally approve the release for Production use.
-
Task 5: After approval, deploy the new release to your Production environment. You can again use either the Cloud Manager UI or the CMCC-Service API. Keep in mind that Production deployments are rolling deployments on the delivery side, but editorial backends require downtime during the process.
| Production deployments are rolling deployments for delivery nodes. However, editorial backends require a downtime during the deployment process. Plan your deployment schedule accordingly to minimize impact on content editors. |
3. Upgrading to a newer Major AMP version
Unlike Minor AMP upgrades, moving to a newer Major AMP version requires changes to the infrastructure configuration of your environments.
To start the upgrade, inform CoreMedia Support about the specific Major AMP version you plan to migrate to (e.g., 2406.1 instead of 2406.0) and specify the target environment.
Phases and General Tasks During the Upgrade Process
-
Task 1: After completing the code migration, open a request via CoreMedia support specifying the new Major AMP version (e.g. 2406.1) and the Development Sandbox you want to use for the upgrade. After the configuration has been done, you can build and deploy the new version on the Sandbox. All functionality should be tested a usual in your development process. Pay special attention to any bug fixes or new features introduced with the release. Always ensure that your Development Sandbox is fully operational before proceeding to further environments.
-
Task 2: After successful testing in the Development Sandbox, push the new version of CMCC to the Docker repository of your CMCC-Service account via the push pipeline in your Sandbox. Now the new release is available for being deployed in a Pre-Production or Production environment.
-
Task 3: To start using the new release on a Pre-Production environment, open a support request. Specify the Major AMP version (e.g., 2412.1), the new software version (Docker container tag), the target environment for testing (e.g., UAT), and your preferred deployment date (at least three business days in advance).
-
Task 4: Complete your defined quality assurance process, and formally approve the release for use in Production.
-
Task 5: After approval, open a support request to deploy the new version to your Production environment, following the same procedure as for Pre-Production.
-
Task 6: If you have multiple Development Sandboxes or Pre-Production Environments, update them as well by following the same procedures.
| Production deployments are rolling deployments for delivery nodes, but editorial backends require downtime. Plan the deployment carefully to minimize disruption for content editors. |
4. Upgrading to a Newer AEP Version
Upgrading your CMCC version to a newer AEP version, e.g., 2404 to 2406 also requires configuration changes of the underlying infrastructure.
Due to more extensive changes in the AEP, (e.g., a newer Spring Boot version,) the usual approach for upgrading is the so-called Coordinated Deployment, which allows testing the new version during the deployment process, including the option of a fast switch back in case of any issues.
For more details, refer to the CoreMedia Content Cloud Service manual available in the dashboard of your Cloud Manager.
Is this page useful?