I think we should prepare our infra / layout for grow of the update status project since I think it will become rather important. To make future grow of the project possible (and facilitate in new options that might or might not be implemented like distributed updates and so) I think its important to separate the update process from the webserver, at least make this possible. This since both cover different functionalities (machine to machine update check vs eyeball to machine browsing).

I propose to make a fqdn like "updates.drupal.org" for this and reflect this in the code like:

$server = variable_get('update_status_server', 'http://drupal.org/xmlrpc.php');

$server = variable_get('update_status_server', 'http://updates.drupal.org/xmlrpc.php');

and do a VHOST on update.drupal.org that 301's to drupal.org or use a CNAME in the DNS that points updates.drupal.org. towards drupal.org.

I think this is an important step to facilitate both functionalities. Note that this needs to be cecked by the hosting company and probably by killes as well?

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

I think this is a good idea. I'll need to speak to OSUOSL to get a DNS entry (preferred solution).

merlinofchaos’s picture

merlinofchaos commented

This sounds like an excellent idea to me.

dww’s picture

dww
we/he/they
commented

+1 from me, too. Dries was talking about an "xmlrpc.drupal.org", but i actually think service-specific (updates) not mechanism-specific (xmlrpc) indirection is better, since we know we'll want to keep providing this service, even if we decide to change the mechanism. and, it's entirely possible we'll have other major services that might eventually need to be spread out, instead of putting all xmlrpc handlers on the same box.

bertboerland’s picture

bertboerland commented

1) i thought about useing "update.drupal.org" but decided to propose "updates.d.o". update sounds like an automatic process

2) please use a functional name (service) like updates instead of an technical name like xmlrpc. i once browsed cvs.mythtv.com and thought the project was nearly dead just to find out they switched to another versioning system hence hostname. we will get there at one time as well (cvs.d.o :-) and I hope we use a functional name if and when we get there. we dont label our website apache.drupal.org do we? :-)

sepeck’s picture

sepeck commented

Excellent idea. I agree with updates.drupal.org being more portable and generic.

cshields’s picture

cshields commented

ok, I've cname'd updates to www for now (our utility is bugging on the MX record for drupal.org and thinks I am trying to cname to that so it won't let me). We're about to upgrade that soon anyway and if the updates -> www is a problem, can change it then or just make a pointer directly to the web servers.

this will be effective in 10 mins

Cheers!

dries’s picture

dries commented

I'm OK with the name. One thought: if we plan to do more XML-RPC-y stuff, we could also settle for the slightly more generic rpc.drupal.org (where index.php would automatically map onto xmlrpc.php).

bertboerland’s picture

bertboerland commented

now all that needs to be done is reflect this change in the code. since this is an arbitrary oneliner no diff here

BTW1: updates.d.o hasnt propagate here yet. as a matter of fact I cant find it on the PRIM or SEC as well?

> updates.drupal.org
Server: ns2.auth.osuosl.org.
Address: 140.211.166.141#53

** server can't find updates.drupal.org: NXDOMAIN

BTW2: i raised another issue here on the use of SSL

mckim’s picture

mckim commented

We accidentally created the CNAME updates.drupal.be --> www.drupal.org which is why it wasn't working.
I have changed the CNAME to be updates.drupal.org --> www.drupal.org.

The ttl is set at 24 hours, so it may take a bit of time to propagate the change.

cshields’s picture

cshields commented

This was my bad.. sorry guys

dww’s picture

dww
we/he/they
commented
Status: Active » Fixed

committed the change to HEAD and DRUPAL-5. not worth a new official release for this (especially since it's all just pointing to d.o for the foreseeable future) but it'll be included in the next release.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)