Closed Bug 598748 Opened 16 years ago Closed 15 years ago

Provide access to Socorro config via puppet for Socorro devs

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: laura, Assigned: jabba)

References

Details

(Whiteboard: [q4])

Socorro devs should be able to see the production and staging configs. Production access can be read-only.
Depends on: 598747
The easiest way to do this is to create a puppet module with your config in it, then host that in an svn repo of your choosing, and have the master puppet config pull that in via an svn external. We can certainly do the initial setup of it for you, but you'll need to tell us where to put it (repo).
If it has machine names and stuff in it then I guess it will need to be a private svn?
Assignee: server-ops → jdow
Depends on: 598750
Whiteboard: [q4]
I've provided read-only access to rsnyder, lthomson, rhelmer, aking, lars, deinspanjer. For those folks with two ldap accounts, I've provided it to the @mozilla.com account, so this repo might need to be checked out as following: svn co svn+ssh://'user@mozilla.com'@svn.mozilla.org/sysadmins/puppet/trunk/modules/socorro/ where user is the username. Ping me over irc for debugging, if it doesn't work.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.