This bug covers setting up the new production environment for Input using the Fjord codebase. Bug #847925 covered building -stage, if that helps. Should this bug cover setting up chief for production? If not, I'll open a new bug for that.
i will use this bug as a tracker for all the others i need to create for the remaining infrastructure bugs i will need to create. the systems (web and celery nodes) are already built and in place at this point.
Assignee: server-ops-webops → cturra
Status: NEW → ASSIGNED
Whiteboard: [triaged 20130313]
(In reply to Will Kahn-Greene [:willkg] from comment #0) > Should this bug cover setting up chief for production? If not, I'll open a > new bug for that. Yes, we'll setup Chief for prod too
Adding blocker for the input -prod tracking bug.
Status: ASSIGNED → NEW
I spent the day testing things in my check list and everything looks ok so far. We have bug #831132 covering restricting the admin to vpn-only and getting chief set up (I don't know what bug that's under--maybe this one). I think those are the only two outstanding things.
Chief for input-prod is ready to use at http://inputadm.private.phx1.mozilla.com/chief/input.prod/ I've successfully done a push http://inputadm.private.phx1.mozilla.com/chief/input.prod/logs/origin.master.1364144846 I've communicated the password to :willkg privately
I've opened a netflow bug that's the final step to get the IRC bots online, once that is done the Chief setup for stage and prod will be complete complete.
(In reply to Brandon Burton [:solarce] from comment #6) > I've opened a netflow bug that's the final step to get the IRC bots online, > once that is done the Chief setup for stage and prod will be complete > complete. IRC bots are online and in #input now
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.