This is a notice as well as request for comments on changing the hostnames of the drupal webservers.

Background: as part of a cleanup of the *.osuosl.org namespace, I will be removing the CNAMES drupal1.osuosl.org and drupal2.osuosl.org. Without the host being in that namespace, there is no reason for the hosts to have a redundant `drupal' name in the *.drupal.org zone. As we have already done with the database servers (moving drupaldbN.drupal.org -> dbN.drupal.org) I would like to move these to be wwwN.drupal.org. Note that this alias already exists for the servers, however this would change the hostnames of the box to be wwwN.

Changes required: all OSL scripts that reference drupalN.(drupal|osuosl).org will be changed to read wwwN.drupal.org. Admins logging in to the web nodes are encouraged to use wwwN.drupal.org now. The deprecated drupalN.drupal.org will be set up to alias to the servers, but its use is no longer recommended. The drupalN.osuosl.org will *not* be preserved.

There is no expected downtime for this change. Most critical functions already use IP addressing only (load balancers, database server grant tables). The uncontrollable factors in this move would be infrastructure scripts that are not managed by the OSL. This is where I would like comments from Gerhard or others on whether time is needed before this change is made. References to drupalN.drupal.org, like in the memcache drupal config, will still work (but should be changed); the only scripts that would break are those that do a reverse lookup on the IP and expect it to match drupalN.drupal.org.

Everything is ready on my end for pushing out this change to www2, www1 will follow after.

--
Eric Searcy
OSU Open Source Lab

Comments

gerhard killesreiter’s picture

gerhard killesreiter commented
Status: Postponed (maintainer needs more info) » Reviewed & tested by the community

I am trying hard to think of a place where this change could break something. I couldn't find anything. I've looked at all the various scripts, but they either access the db servers directly, or use drupal.org through http.

dww’s picture

dww
we/he/they
commented

Sounds fine to me. I don't know of any project* related scripts that reference these hostnames, so I'm pretty sure we're cool there. A few questions:

A) what about drupal3.osuosl.org aka cvs.drupal.org? should we just ssh to it as cvs.d.o?

B) I presume the alias for updates.drupal.org will be unharmed by this move, right? ;)

Thanks!
-Derek

emsearcy’s picture

emsearcy commented
Assigned: Unassigned » emsearcy
Status: Reviewed & tested by the community » Closed (fixed)

A. No, I'm not planning to change drupal3's name. We're planning to migrate CVS and mail to the new box donated by Sun sometime in the near future, and the name change can wait till then; it will be easier because no one will be using services on that box.

B. Correct.

I renamed drupal2 a few hours ago, the only thing I hadn't accounted for that broke was host access rights for SSH logins, which was quickly fixed once killes let me know he couldn't log in.

p.s. The brief outage at 00:46 UTC, also a few hours ago, was an unrelated problem with the load balancers; I've put in a work-around until I can troubleshoot them tomorrow.

Closing ticket.

emsearcy’s picture

emsearcy commented

drupal1 has been renamed to www1 now as well. Also, I fixed the load balancers today; yesterday's work-around was to short-circuit the validation and web node failover code that was temporarily not working (so only failover between load balancers was working), but they are back to normal now.

Component: Webserver » Servers