Last modified: 2014-04-25 21:31:27 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 T55723, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53723 - Package Parsoid and clean up deploy system
Package Parsoid and clean up deploy system
Status: NEW
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks: 57711
  Show dependency treegraph
 
Reported: 2013-09-03 21:23 UTC by Gabriel Wicke
Modified: 2014-04-25 21:31 UTC (History)
11 users (show)

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


Attachments

Description Gabriel Wicke 2013-09-03 21:23:12 UTC
We'd like to make it easy for both ourselves and third parties to have a properly configured Parsoid install. This should include a proper init script, log rotation etc.

In production, we currently use puppet for config files and git-deploy for pushing out the code and restarting Parsoid (see https://wikitech.wikimedia.org/wiki/Parsoid). Files managed by puppet live in the puppet repository, where operations can review code that will be running with root rights. Our puppetization is not very complete yet, with log rotation for example still missing (which causes parsoid servers to hang after running out of disk space).

There are more moving parts though: We currently manage our dependencies and config in a private config repository which we deploy separately from the main code. For Jenkins testing, we are using another contrib repository which also needs to be updated manually.

It would be good to merge all this in a way that lets us

* build Debian packages
* still allows operations to review root-level code
* supports current deployment methods (git-deploy)
* minimizes manual dependency tracking and contrib updates

An idea that Ryan brought up is to use submodules for this. The details of how this might look are discussed in https://www.mediawiki.org/wiki/Parsoid/Packaging.
Comment 1 Gabriel Wicke 2013-10-10 23:58:51 UTC
Ori's vagrant upstart script: https://dpaste.de/dC84/raw/
Comment 2 physikerwelt 2013-12-09 10:45:56 UTC
A good proof of concept is to repackage mediawiki-math (http://packages.debian.org/sid/mediawiki-math) for mathml+svg rendering.
In contrast to the old package the new version does no longer depend on latex itself, but on several node modules and phtomjs.
In addition to that a puppet module has to be developed that configures the package according to the wikimedia server configuration.
(https://gerrit.wikimedia.org/r/#/c/90733/6)
If there is a way for an automatic debianization (maybe jenkins could do that) I don't see a particular need for git deploy. Or did I miss something?
Comment 3 Gerrit Notification Bot 2014-02-04 03:47:53 UTC
Change 110666 had a related patch set uploaded by GWicke:
Parsoid debianization

https://gerrit.wikimedia.org/r/110666
Comment 4 Gerrit Notification Bot 2014-02-19 23:26:24 UTC
Change 110666 merged by jenkins-bot:
Parsoid debianization

https://gerrit.wikimedia.org/r/110666
Comment 5 Andre Klapper 2014-04-25 06:43:56 UTC
Patch was merged a while ago - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?
Comment 6 Gabriel Wicke 2014-04-25 21:30:43 UTC
The patch is merged, but there are still some things missing:

* we don't have a longer-term Debian repo yet where we can upload this to; waiting for ops to implement this

* use debs for deployments in testing and perhaps at some point production

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


Navigation
Links