Closed
Bug 988003
Opened 11 years ago
Closed 11 years ago
JSON File CDN
Categories
(Websites :: glow.mozilla.org, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bensternthal, Assigned: nmaul)
References
Details
Bug covers setting up whatever output folder is specified in bug #986237 to be served via CDN.
| Assignee | ||
Comment 1•11 years ago
|
||
CDN property created, named "glow.cdn.mozilla.net". Origin is "glow-origin.cdn.mozilla.net". Neither one exists in DNS yet, and server-side setup details are unknown at this point.
| Assignee | ||
Comment 2•11 years ago
|
||
glow.cdn.mozilla.net added to DNS, points to Edgecast.
glow-origin.cdn.mozilla.net added to DNS, points to new VIP https://63.245.217.19/. Currently just a default nginx page.
Still waiting on some DNS propagation and teh CDN config propagation. Should be good within an hour or so.
This is done for now, until we have some prod content to point at it, domain names, SSL certs, etc.
Comment 3•11 years ago
|
||
Prod server is now up and serving media, but the CDN doesn't seem to be working. For me it tries for a long time and never returns.
I tried:
$ curl -v glow.cdn.mozilla.net/static/js/main.js
and:
$ curl -v https://glow.cdn.mozilla.net/static/js/main.js
Flags: needinfo?(nmaul)
Comment 4•11 years ago
|
||
Seems jakem is out. Got any time and ideas :cturra?
Flags: needinfo?(cturra)
Comment 5•11 years ago
|
||
i think i tracked down why this isn't working. there were a couple origin references at edgecast set to cdn.moziila.net instead of cdn.mozilla.net. grrr.. typos!
i have just submitted the cdn config change, which can take a bit to propagate to the edge nodes. it should be good to test in an hour.
Flags: needinfo?(cturra)
Updated•11 years ago
|
Flags: needinfo?(nmaul)
Comment 6•11 years ago
|
||
Looks like that was it. Thanks :cturra!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•