ECDN upgrade from version 1.4.x to 2.0.x

ECDN edge versions eligible for automatic, incremental upgrade: 1.4.1~20170324+1490356483 1.4.1~20170508+1494260601 1.4.1~20170517+1495018515

Servers started with earlier releases will need to be recreated.

Upgrading the ECDN edge server instances from 1.4.x to 2.0.x requires a collaborative effort between you and the ECDN Support team. Please follow the steps below:

  1. You: You may need to update the corporate firewall settings.
    • This upgrade requires the edge instances to have network connectivity to the ECDN backend endpoint download.deepcaching.com, from where the edge servers can download the latest configuration settings.
    • If your company exercises control of outgoing corporate traffic to the Internet by using a whitelist of known destinations configured in the corporate firewall, then you need to request your network administrators to add the ECDN the destination download.deepcaching.com to the allowable whitelist for HTTPS (outgoing port 443) connectivity.
    • If you attempt an upgrade without enabling this connectivity, then the upgrade attempts will fail. With such failures, you may require to do a fresh install of the new release, which may take 15+ minutes for each instance + virtual appliance image download times.
  2. You: Identify a maintenance window and first server.
    • You have to identify a maintenance window for when edges may be upgraded. The updates take approximately 15 minutes per edge instance + download time.
    • The upgrade will be initiated on one edge server initially to validate the upgrade process in your specific network environment. The initial edge server is usually the sandbox machine, or the least mission critical instance.
      Note: You can set up a "sandbox" instance the same way like any other production servers, however it is advised to be set to "Disabled" on the ECDN Portal. Set it to "Enabled" only for testing/validation purposes, when there is no critical event is broadcasted.
    • Share the maintenance window time and the initial machine name with the ECDN Support team.
  3. You: Create an ordered list in which edge server instances must be upgraded.
    • After the initial edge server is upgraded all other machines will be upgraded in parallel. If you prefer to roll out the upgrades in phases, please create an  ordered list instance names and locations reflecting the order in which the edges should be upgraded.
    • Share this ordered list with ECDN Support team.
  4. You: Reboot the edge instance(s). This ensures a clean starting point.
  5. ECDN Support: Initiate the upgrade process.
    • At the designated maintenance window start time, ECDN Support will initiate the upgrade process, as per the ordered list you provided.
  6. You: Validate the edge instance after the upgrade.
    • When the upgrade is complete, you will be asked to run a few simple validation tests.
    • Check the version number of the edge as seen in the ECDN web portal. It should reflect version 2.0.x.
    • You can start an actual live broadcast, enable the debug overlay in the player, and visually confirm that the content is being served from the just installed ECDN instance. Note, you will need to start the player from the same location as the ECDN instance.
Powered by Zendesk