Page MenuHomePhabricator

create a parsoid user in labs LDAP
Closed, ResolvedPublic

Description

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.


Version: unspecified
Severity: normal

Details

Reference
bz63329

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:01 AM
bzimport added a project: Cloud-VPS.
bzimport set Reference to bz63329.
bzimport added a subscriber: Unknown Object (MLST).
hashar created this task.Mar 31 2014, 9:27 PM
coren added a comment.Apr 2 2014, 12:35 PM

uid=605(parsoid) gid=605(parsoid) groups=605(parsoid)

Migrating parsoid user on deployment-parsoid04.eqiad.wmflabs

Thank you!

@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.

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.

Ah, makes sense. Thanks for the explanation!