Service Migration to Version 3.0 FAQ

As of 2022, Lumen has introduced a superior caching configuration self-service product accessible from the Media Portal and also directly via API. A migration is required to take advantage of it. Our support engineers will support you through this with tooling designed to minimize disruption to you.

Work with your account team or create an online MACD ticket in the Media Portal.

The migration process has been designed to be transparent for you and your production traffic. Dedicated Lumen CDN operations staff will work with you to determine a timeline for the migration and support you throughout the process.

Once the migration starts, our operations team will first re-create your configuration in a v3 format and test in thoroughly in our labs. Operations teams will then gradually deploy the candidate CMv3 configuration using our new staged activation capability (described below).

Risk to any outage is minimized. Without affecting your current pre-3.0 service image (configuration), your assigned migration engineer converts your configuration to the new version 3.0 format and deploys it into production with a 0% traffic allocation. At a time arranged with you, we will begin a series of stages where we divert an incrementally increasing amount of traffic to be served by the converted configuration. Each step will be monitored for anomalies until 100% is reached. Your approval will trigger the final step to complete the migration.

We discourage making any changes until your migration is complete to minimize unexpected disruptions and to better analyze the outcome of each migration step. Using the configuration management version 3.0 during a migration is allowed; however, any configuration changes you save may not be deployed until the migration is complete.