Closed
Bug 733544
Opened 13 years ago
Closed 12 years ago
update PuppetAgain users module to flesh out builder user
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P2)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 764948
People
(Reporter: dustin, Assigned: kmoir)
References
Details
This module currently creates the builder user, but will need to set up .ssh/*, .hgrc, .bash_profile, and a crontab as per the old manifests.
Comment 1•13 years ago
|
||
http://hg.mozilla.org/build/puppet/rev/8e47c8b35f6d sets up .ssh/* using a static authorized keys file instead of an LDAP-generated one. It also sets up a basic .hgrc, .gitconfig and a basic .vimrc.
Worth noting:
1) I am making the assumption that on linux, all home dirs are in /home/ and in /Users/ on mac.
2) There doesn't appear to be any explicit creation of the cltbld group
3) We should be generating the authorized_keys file based on who is in the releng group in LDAP.
4) I have very basic hg, vim and git configs. Leaving them in users should be fine since a whole new module for these files seems like a heavy hammer.
Updated•13 years ago
|
Assignee: nobody → jhford
Comment 2•13 years ago
|
||
filed bug 734290 to track work on follow-on LDAP based authorized keys file generation.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to John Ford [:jhford] from comment #1)
> 1) I am making the assumption that on linux, all home dirs are in /home/ and
> in /Users/ on mac.
I think it will be safe to assume /home everywhere but Darwin. We can, of course, adjust later.
> 2) There doesn't appear to be any explicit creation of the cltbld group
Adduser seems to do that automatically.
> 4) I have very basic hg, vim and git configs. Leaving them in users should
> be fine since a whole new module for these files seems like a heavy hammer.
I think this is the correct place for it, in fact.
There are some releng-specific attributes in the files here -- "Mozilla Release Engineering", "release@mozilla.org", and the SSH config. For the latter, I think we should make everything use BatchMode -- it's no loss of security (since batch mode will not accept keys).
I'm re-opening for these changes. Prioritize appropriately.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•12 years ago
|
Assignee: jhford → kmoir
Reporter | ||
Comment 4•12 years ago
|
||
Kim, I think most of this is addressed in your Darwin work. Can you confirm and dupe if so?
Assignee | ||
Updated•12 years ago
|
Status: REOPENED → RESOLVED
Closed: 13 years ago → 12 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•