330482 - Create additional CNAMES for start.mozilla.com

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[:Gavin Sharp [email: [e-mail]]]

To fix bug 327208, additional CNAMES need to be added to start.mozilla.com. I will attach a list of what needs to be added. Not sure who needs to sign off on this.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Attachment: CNAMES to be added

These correspond to all the locales that exist in 1.0.x, obtained from http://lxr.mozilla.org/l10n-aviarybranch/source/browser/locales/ . It does not include ko-kr and ja-jp, which already have CNAMES. "be" is a 1.5.0.x locale that does not already have a CNAME, so I've included it.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

Comment on attachment 215036 [details]
CNAMES to be added

Sorry, this list has duplicates. Will attach the correct file in a bit.

Comment 3

[Dave Miller [:justdave]]

This needs coordination from marketing first as they need to verify that the correct destination domains exist at Yahoo/Google first.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Attachment: correct zonefile

Comment 5

[:Gavin Sharp [email: [e-mail]]]

We need to ensure that a vhost for ja-jp.start.mozilla.com is correctly configured at ja-jp.mozilla.search.yahoo.com.

Comment 6

[Mike Schroepfer]

John/Chris - we are blocked on your confirmation that these are the right addresses for the start pages for 1.0.8

Comment 7

[:Gavin Sharp [email: [e-mail]]]

The main issue, as I understand it, is that we need to ensure that Yahoo is set up to handle ja-jpm.start.mozilla.com pointing to ja-jp.mozilla.search.yahoo.com. Dave Miller mentioned that there were problems related to that in the past. All other domains (pointing to Google) should be OK.

That being said, I'm not sure whether that should really hold back this change - if we make these changes, and bug 327208's patch is checked in, default homepages for all 1.0.x builds, with the possible exception of ja-JPM (pending a config change to Yahoo's server), should work. They would be identical to the start pages for the 1.5.0.x builds. Things can then be tested and we can see where we are at.

Comment 8

[Mike Shaver (:shaver emeritus)]

Why don't we just point ja-jpm.start.mozilla.com at virtual-redirect.mozilla.org, and then redirect from there to ja-jp.start.mozilla.com, which is correctly configured and working already at Yahoo today?

This is what we're already doing with ja-jp-mac.start.mozilla.com (the 1.5 name for ja-jpm), and it seems to be working fine.

Comment 9

[:Gavin Sharp [email: [e-mail]]]

Ah, I hadn't considered that - but you're right, that would work. I take it this bug can now be moved back to server ops so these changes can be made?

Comment 10

[Mike Schroepfer]

Why in the world would we do a http redirect?  Do we know for sure the server can take the load?  Have we measured the additional latency induced by sending every Japan request across the pacific ocean? 

Why not push the zone file (or edit a local hosts file) and test out whether it works fine?

Comment 11

[Mike Schroepfer]

Also - why not checkin bug 327208?  Once we get those in we can respin and test out whole system.

Comment 12

[Mike Schroepfer]

Assigning to Justin to implement zone file.   

Comment 13

[Mike Schroepfer]

Ok - didn't fully grok the history here - so sorry for jumping on this.  Just had a in-person discussion with Justin, CBeard, Lilly, and with Gavin over IRC.  Here's the scoop:

1) We need to push this zone file EXCEPT for ja-jpm.  This is to make sure that the local.start.mozilla.com works for all 1.0.8 users since many of the locales have different code from 1.0.x and 1.5.0.x and thus those dns records don't exist.  Justin will drive this in.  

2) Sounds like for ja-jpm Y! Japan is not setup in their VHosts - so we will do the same redirect hack as done in 1.5 for the Mac.  This is just for Japan mac users.  Justin will make sure this redirect is setup

3) In parallel it might not be a bad idea for John to work with Y! to setup their vhosts for the mac so we don't force the extra latency on Japan users.  Lilly to take this.

Thanks all!

Schrep

Comment 14

[Justin Fitzhugh]

Depends on the original and temporary hack/bug which was done (318021).  We need to get the Yahoo vHosts setup correctly (for ja-jp-mac and ja-jpm) so we can move both of these off virtual-redirect and to cnames in parallel - jlilly will talk to Yahoo.
 
(In reply to comment #10)
> Why in the world would we do a http redirect?  Do we know for sure the server
> can take the load?  Have we measured the additional latency induced by sending
> every Japan request across the pacific ocean? 
> 
> Why not push the zone file (or edit a local hosts file) and test out whether it
> works fine?
> 

Comment 15

[Rafael Ebron (:rebron)]

http://ja-jp-mac.start.mozilla.com
is supported by Yahoo! in vhost as of 12/14/05 


Working on http://ja-jpm.start.mozilla.com to get supported.

Comment 16

[Rafael Ebron (:rebron)]

ETA: 3/22 for http://ja-jpm.start.mozilla.com
on the Yahoo side.

Comment 17

[Justin Fitzhugh]

Ok, all the zone updates are done and tested, ja-jp-mac is no longer a redirect but rather a cname and the ja-jpm redirect is in and working.  I'll keep 318021 open until 3/22 when I'll test that the ja-jpm vhost is in and working - then migrate ja-jpm to a cname.

Comment 18

[Justin Fitzhugh]

Ok, all the zone updates are done and tested, ja-jp-mac is no longer a redirect but rather a cname and the ja-jpm redirect is in and working.  I'll keep 318021 open until 3/22 when I'll test that the ja-jpm vhost is in and working - then migrate ja-jpm to a cname.