|Resolved||elukey||T258970 Set up environment for Product Analytics system user|
|Resolved||elukey||T230743 Create a repository and user for Product Analytics Oozie jobs|
|Resolved||elukey||T255039 Creation of a new POSIX group and system user for the Product Analytics team|
- Mentioned In
- T261953: Set up an Oozie job to count Wikipedia Preview requests and clickthroughs in the webrequest logs
T258970: Set up environment for Product Analytics system user
rAWPR26c440018318: Add README
T246578: Refactor Analytics POSIX groups in puppet to improve maintainability
T246250: Sunset external automatic translation dashboard
- Mentioned Here
- T255039: Creation of a new POSIX group and system user for the Product Analytics team
Can you please reply to the previous comment? Thanks! (Also, what is a "user" in which specific system?)
Sorry for the ambiguity.
Yes, we'd like a new repo in Gerrit. I'll tag and ping ProductAnalytics for them to Request one in:
Regarding the user, I meant a Hadoop user, not to be done by Release Engineering.
Can you Product Analytics please, as Greg suggests, request a repository in Gerrit to store your team's Oozie jobs?
I can do that as well, but I thought you'd like to chose a repo name, owner and type.
@mpopov, I'm still wondering about this.
Technically, it looks like Gerrit allows us to use analytics/wmf-product as a repo and still nest other repos within it. But it doesn't seem like it would work in GitLab (which treats "groups" and "projects" separately). And even if worked, it would still be pretty confusing for analytics/wmf-product to be a repo for jobs while, say, analytics/wmf-product/wmfdata-python is a totally separate project!
@nshahquinn-wmf: That's an excellent point! I updated the task description with the analytics/wmf-product/jobs repo idea. I like that. Should we just use the analytics/wmf-product root repo as a convenient index of "sub-repos" like analytics/wmf-product/jobs and analytics/wmf-product/wmfdata-python?
Using it as an index definitely makes sense. I wish Gerrit did that automatically, but since it doesn't, manual it is 😁 For now, there won't be anything to index other than the jobs repo, but no reason not to get started!