Last modified: 2014-09-22 21:53:14 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 T45338, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43338 - Trebuchet blockers (tracking)
Trebuchet blockers (tracking)
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
deploysprint-13
:
Depends on: 43615 51142 54185 43339 43340 43614 51581
Blocks: 45528
  Show dependency treegraph
 
Reported: 2012-12-22 00:53 UTC by Rob Lanphier
Modified: 2014-09-22 21:53 UTC (History)
6 users (show)

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


Attachments

Description Rob Lanphier 2012-12-22 00:53:54 UTC
This bug will likely become a tracking bug.  There's a number of steps that we need to figure out with respect to git-deploy.  Full list started here:
http://wikitech.wikimedia.org/view/Git-deploy_deployment
Comment 1 Rob Lanphier 2013-01-05 00:17:35 UTC
A few of the tasks in progress:

bug 43339: Deploy git-deploy to the Beta Cluster - Antoine is just back from vacation, and is getting started on this.
bug 43340: Design new on-disk layout for MediaWiki install on tin/eqiad Apaches - Sam and Tim are working on this.
bug 43614: l10n generation in git-deploy - Brad has started work on this.
bug 43615: Audit salt scripts for completeness (checking against scap/sync-file/sync-dir) - Aaron will be doing this.
Comment 2 Rob Lanphier 2013-01-05 00:27:52 UTC
Assigning meta issue to Chris for purposes of tracking.  Lightly edited status email about this move included below.
-----
We've long talked about moving away from scap/sync-dir/sync-file as tools for deploying code to the cluster.  Ryan Lane has been working on a git-deploy based system which we hope is just about ready for deployment.

git-deploy as implemented is documented here:
http://wikitech.wikimedia.org/view/Git-deploy

We're currently planning to use this system to deploy 1.21wmf8, which is scheduled for Wednesday, January 16.  The plan to move to git-deploy came together fairly quickly, which is why this is the first you may be hearing about this.

This is an ambitious plan, and so plans may yet change quickly yet. The "must do" objective driving this is a switch of the disk layout, which we want to have done prior to the datacenter migration the following week.  If we're not successful with moving to git-deploy, please be aware that there will be other changes that will be done in service of that goal.

Chris Steipp and Ryan Lane will be available to help deployers transition to the new system.
Comment 3 Andre Klapper 2013-02-28 00:04:23 UTC
[assigning to Ryan as RobLa said]
Comment 4 MZMcBride 2013-07-07 15:29:47 UTC
Is git-deploy dead?
Comment 5 Ryan Lane 2013-07-08 17:01:30 UTC
It's used for parsoid and eventlogging and other deployment targets are being added. It's currently deprioritized for MediaWiki.
Comment 6 MZMcBride 2013-07-10 22:57:22 UTC
(In reply to comment #5)
> It's used for parsoid and eventlogging and other deployment targets are being
> added. It's currently deprioritized for MediaWiki.

Aha, good to know! Thank you for clarifying.

This bug came up in the context of rewriting/upgrading Wikimedia's deployment scripts (scap, etc.). It's unclear whether improving these deployment scripts (bug 27294) would be a good use of time/energy.
Comment 7 Ryan Lane 2013-07-10 22:59:15 UTC
Until at least next quarter we won't be starting work again on git-deploy, so it makes sense to continue improving the current ones; it likely doesn't make sense to rewrite them completely, though.
Comment 8 Greg Grossmeier 2014-02-12 18:32:33 UTC
reseting assignee mostly because this is a tracking bug, and I don't want the assumption that Ryan (or one person) will be tackling all blockers.

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


Navigation
Links