Important: This guide is for the V2 version of Media portal only. If you’re using V3, please refer to Configuration Management for V3, and if you are on V1.5, please note that this version has now been deprecated and we invite you to read our guide on migrating to V3.
A saved configuration isn't active until you deploy it (promote it) to an environment—either staging or production. Once you promote it, Media Portal lists the configuration under that environment; it may take several minutes to be fully propagated through the CDN network. To do A/B testing with configurations in production, you can enable a second production slot for a service component ID (SCID). Once you enable the second production slot, you can then change the traffic allocation for the slots.
To manage deployment, you must first sign into Media Portal, open the Caching page by navigating to My Services > Caching, and select the access group and SCID containing the configuration you want to deploy, and then, from the “configuration list”, select the configuration you want to promote
Promoting a Configuration to an Environment
To promote a configuration to an environment, open a configuration version of your choice as described above. Media Portal automatically selects the latest version of the configuration and shows the details for the configuration.
If you want to select a specific version, you can find it by clicking on “View History”. If you want to promote the configuration that was previously promoted to staging, select it under the “staging” section of the list.
Once you’ve opened the configuration version of your choice, click on “promote”. In the “Promote Configuration” subsection, set the radio button to “staging” or “production” depending on the environment you wish to deploy the configuration, and add any notes that will help you or others keep track of the configuration.
Select the check box if you want to receive an email when Media Portal finishes promoting the configuration. and finally click on “promote”. Media Portal promotes the configuration to the environment. You'll now see this configuration listed under the environment you selected in the configuration list; it may take several minutes to be fully propagated through the CDN network.
Enabling a second production slot for a SCID
For the production environment, it is possible to add a second production slot. To enable a second production slot for a SCID, open a configuration version of your choice as described above.
click on “promote” and set the environment to “production”. You’ll notice an option to enable an additional slot. Click on “Enable” there to activate a second production slot for your SCID.
Once the second slot is enabled, type the percentage of traffic you want to allocate to the configuration in slot B, add any notes if you wish and click “promote”.
Media Portal promotes the configuration to the second production slot (slot B) and allocates traffic to the configuration based on the percentage you specified. The configuration appears in Transient status while Media Portal propagates the change across the Lumen CDN.
Once you enable a second production slot for a SCID, you cannot return to having only one production slot.
You can only promote a configuration to a slot with 0% traffic allocated to it. If the slot is carrying traffic, first adjust the traffic allocation to 0%.
Changing the Traffic Allocation for the Production Slots on a SCID
To adjust the traffic allocation of production slots, open a configuration (“selected from the “production” section of the list), and click on “Adjust”. Media Portal lists the slot the configuration occupies and the percentage of traffic the configuration is currently receiving. Use the “Traffic Percentage” fields to adjust the traffic allocation between the two configurations. (Remember the total of the two slots must add up to 100%.)
Viewing the History for an Environment
You can view a history of the configurations promoted to the staging and production environments for a SCID. To view the history for an environment, Navigate to the Caching page, and select the access group and the SCID you want to work with, and click on “View Environment History” button. Media Portal displays the environment history for the SCID. By default, you'll see environment history for production. To view environment history for your staging environment, click the “Staging” tab. Lastly, to view a list of the transactions promoting configurations to environments for the SCID, click the “Transactions” tab.
Viewing CName Information for Aliases
Once you push a configuration to a production slot, Lumen adds the CName (canonical name) information for each of the aliases. Each alias must have a CName entry to direct traffic to the Lumen CDN. When you add aliases to a configuration and promote the configuration to production, Lumen creates a corresponding CDN DNS name.
To view CName information for aliases on a configuration, From an open configuration in a production slot, scroll down to the “Properties” section, then select a property from the list. Media portal lists the CName value for each of the aliases on the property.
Learn more about
Top 10 articles