Closed
Bug 917600
Opened 11 years ago
Closed 10 years ago
Set up Chief for www-dev
Categories
(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)
Infrastructure & Operations Graveyard
WebOps: Product Delivery
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cturra, Assigned: cturra)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/120] )
all of the bedrock demo, stage and prod environments have cheif, but dev is still using the old bash script. this bug is to track the work for getting www-dev running chief also.
Updated•11 years ago
|
Summary: setup cheif for www-dev → setup chief for www-dev
Comment 1•11 years ago
|
||
I've heard further reports that www-dev goes down from time to time. We should figure that out. I'm commenting here because I'm wondering if moving www-dev to chief might solve or at least help diagnose the issue. I've yet to file a separate bug for figuring out the dev issue, but I'll do that now if we want. Otherwise I'll wait to see if fixing this one makes it better or not, and file at that point if necessary.
Flags: needinfo?(cturra)
Assignee | ||
Comment 2•11 years ago
|
||
chief wouldn't make any difference with regards to any environment unavailability. off the top of my head i don't recall any specific environment issues, but if we can track down dates/times from any dev outages that have been seen, please provide them. *a quick note on that - if dev is unavailable, all demo environments would be also because they're hosted on the same web heads.
Flags: needinfo?(cturra)
Comment 3•11 years ago
|
||
My thought there was perhaps there was something about the other update script that caused it to fail and bring apache with it, and that the chief script would do things differently. I don't have any good data on when this happened. I know there was a recent bug (bug 937092) in which :flod reported an outage, but I've no idea how quickly the outage was noticed and I don't have any info other than that. I can begin tracking it now, but we've often been able to fix these on our own by using chief on a demo since, like you said, it's the same apache.
Comment 4•10 years ago
|
||
see https://bugzilla.mozilla.org/show_bug.cgi?id=1014768#c3 -- can we get an update on the status of this bug?
Updated•10 years ago
|
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/120]
Updated•10 years ago
|
Summary: setup chief for www-dev → Set up Chief for www-dev
Comment 5•10 years ago
|
||
The commander script for www-dev is now in the repo: https://github.com/mozilla/bedrock/blob/master/bin/update/deploy-dev.py It should be on the dev server in a matter of minutes.
Comment 6•10 years ago
|
||
:jakem or :cturra, this is the bug I was referring to during the bedrock devops meeting-- can one of you add the symlink to the file from comment #5 as discussed please?
Assignee | ||
Comment 7•10 years ago
|
||
this has lingered too long - i am going to get chief on here by the end of the week (maybe even sooner!)
Assignee: server-ops-webops → cturra
Assignee | ||
Comment 8•10 years ago
|
||
woohoo. that went faster than i had expected. chief setup now complete and tested \o/ http://bedrockadm.private.phx1.mozilla.com/chief/bedrock.dev/history
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 9•10 years ago
|
||
RAWK! \o/ Nice work Chris! Thanks!
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
Updated•8 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
•