Page MenuHomePhabricator

Selecting configuration files depending on the realm of the current (bastion) server isn't always sensible
Closed, InvalidPublic



From Rob: "Not sure if its legit, but the mctest.php script from wikitech only outputs tampa based mc servers. This should be confirmed if the spence check is only checking against Tampa mc or both mc server sets. (Or, at minimum, the active cluster, which is presently eqiad.)"

In most cases, using a script on a bastion host, we are likely to want to do it against the active cluster, and not have to use a bastion in the "correct"/current datacentre. There is, however, cases where we would want this behavior.

Version: wmf-deployment
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:20 AM
bzimport added a project: Deployments.
bzimport set Reference to bz44889.
bzimport added a subscriber: Unknown Object (MLST).

The RT ticket is closed (effectively dupe of this), so I'm copy/pasting the only unique info from there to here:

13:59 < mutante> require( getRealmSpecificFilename( "$wmfConfigDir/db.php" ) );
13:59 < mutante> require( getRealmSpecificFilename( "$wmfConfigDir/mc.php" ) );

This is a duplicate of T82145 now, which is the original (and now imported) RT ticket.

faidon subscribed.

This hasn't been an issue since.