701885 - test AMO CDN changes

Status: VERIFIED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Jake Maul [:jakem]]

We are getting ready to cut AMO over to a new CDN config.

The current CDN name is 'static-cdn.addons.mozilla.net'. This will be changing to 'static-ssl-cdn.addons.mozilla.net'. The reason for the change is to standardize SSL and non-SSL naming conventions across sites and CDN providers. Some providers allow SSL and non-SSL traffic on the same CDN property (with appropriate billing), while others do not... hence the need for separate names. Since AMO is all-SSL, very little extra work is required.

This bug is to get this change tested before going into production.

The new name is configured and should be operational for testing purposes.

The best way I can think of to test this will be to set STATIC_URL on addons.allizom.org, and run through the standard tests there. I don't expect any problems.

Alternatively, we can simply hit "https://addons.mozilla.org/" and a few sub-pages and build up a list of CDN links, alter them to point to the new name, and make sure they all work. This might be easier, but possibly less thorough.

Comment 1

[krupa raj[:krupa]]

In addons-dev, currently the CDN name is addons-dev-cdn.allizom.org. What will this be changing to?

Comment 2

[Wil Clouser [:clouserw]]

What's the priority of this?  We're scrambling to get the developer preview of the apps store launched by the 22nd (or potentially end of the month).  QA doesn't want to split their time on this.

Comment 3

[Jake Maul [:jakem]]

Go ahead and concentrate on the app store for now. I can do a more thorough test of this independently, and put it into production when it's good. If it takes me much longer, QA might have more free time again. I've got some other pressing things as well.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED -- thanks, Jake, for doing the thorough, initial testing.

Can confirm that we deployed the changes with the previous AMO push, and that we're now successfully using both CDNs (EdgeCast + Akamai), on AMO:

somecomputer:~ moco$ nslookup static-ssl-cdn.addons.mozilla.net
Server:		10.250.0.21
Address:	10.250.0.21#53

Non-authoritative answer:
static-ssl-cdn.addons.mozilla.net	canonical name = 2-01-2967-0002.cdx.cedexis.net.
2-01-2967-0002.cdx.cedexis.net	canonical name = wildcard.addons.mozilla.net.edgekey.net.
wildcard.addons.mozilla.net.edgekey.net	canonical name = e987.g.akamaiedge.net.
Name:	e987.g.akamaiedge.net
Address: 173.222.36.43

somecomputer:~ moco$ nslookup static-ssl-cdn.addons.mozilla.net
Server:		10.250.0.21
Address:	10.250.0.21#53

Non-authoritative answer:
static-ssl-cdn.addons.mozilla.net	canonical name = 2-01-2967-0002.cdx.cedexis.net.
2-01-2967-0002.cdx.cedexis.net	canonical name = cs6.adn.edgecastcdn.net.
Name:	cs6.adn.edgecastcdn.net
Address: 72.21.92.26