Last modified: 2014-04-18 20:18:16 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 T65329, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 63329 - create a parsoid user in labs LDAP
create a parsoid user in labs LDAP
Status: VERIFIED FIXED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-03-31 21:27 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-04-18 20:18 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Antoine "hashar" Musso (WMF) 2014-03-31 21:27:32 UTC 
deployment-prep could use a unique identifier for the 'parsoid' user much like we did for 'l10nupdate' user (bug 62529).

UID/GID 605 is apparently free in LDAP.
Comment 1 Marc A. Pelletier 2014-04-02 12:35:40 UTC 
uid=605(parsoid) gid=605(parsoid) groups=605(parsoid)
Comment 2 Antoine "hashar" Musso (WMF) 2014-04-02 12:37:18 UTC 
Migrating parsoid user on deployment-parsoid04.eqiad.wmflabs

Thank you!
Comment 3 Gabriel Wicke 2014-04-18 18:53:43 UTC 
@Antoine: I'm curious why you need a specific UID/GID for Parsoid. The Debian package just uses names, and there is no need for a home dir.
Comment 4 Antoine "hashar" Musso (WMF) 2014-04-18 19:36:38 UTC 
On beta the Parsoid instance writes its logs to the shared directory in /data/project/parsoid which is a NFS server.  I needed the same UID / GID to be used on the NFS server and the Parsoid instance.

The same goes for user apache, mwdeploy and l10nupdate which (may?) need to be consistent across instances since they end up writing their logs to /data/project/logs which is shared.
Comment 5 Gabriel Wicke 2014-04-18 20:18:16 UTC 
Ah, makes sense. Thanks for the explanation!
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links