Last modified: 2014-03-10 22:40:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T46889, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44889 - Selecting configuration files depending on the realm of the current (bastion) server isn't always sensible
Selecting configuration files depending on the realm of the current (bastion)...
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-12 00:53 UTC by Sam Reed (reedy)
Modified: 2014-03-10 22:40 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sam Reed (reedy) 2013-02-12 00:53:55 UTC
CF https://rt.wikimedia.org/Ticket/Display.html?id=4510

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.
Comment 1 Greg Grossmeier 2014-03-10 22:40:29 UTC
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" ) );

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links