Closed
Bug 1346277
Opened 9 years ago
Closed 9 years ago
CAB review for Bugzilla failover instance in AWS
Categories
(Infrastructure & Operations :: MOC: Service Requests, task)
Infrastructure & Operations
MOC: Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gozer, Assigned: gozer)
References
Details
Date TBD.
We would like to schedule a failover test for Bugzilla in AWS to confirm our operational status since the last failover test
Link to solution design:
https://mana.mozilla.org/wiki/display/EA/Bugzilla
Link to UAT test plan:
https://docs.google.com/a/mozilla.com/spreadsheets/d/1AwN82cjdsOXi980EciTArzpK7Yxs8Md5DjIrHGkcIX4/edit?usp=sharing
Link to operational checklist:
https://docs.google.com/spreadsheets/d/16cQlBdQoOZdz6Zpf4x5-a-wjSTly_OWGZprjV6Qcm-0
Comment 1•9 years ago
|
||
I followed up with gozer via email, I'll get this CAB entry opened.
Assignee: nobody → kferrando
Status: NEW → ASSIGNED
Comment 2•9 years ago
|
||
We had last talked about doing this at the following TCW. If we're really doing it *THIS* weekend, the banner on BMO needs to get in place ASAP and we need to verify that at least one of the devs is available this weekend.
Flags: needinfo?(gozer)
Flags: needinfo?(dylan)
Flags: needinfo?(dkl)
Comment 3•9 years ago
|
||
(In reply to Kendall Libby [:fubar] from comment #2)
> We had last talked about doing this at the following TCW. If we're really
> doing it *THIS* weekend, the banner on BMO needs to get in place ASAP and we
> need to verify that at least one of the devs is available this weekend.
No, let's do this *next* TCW not 4/1. Sorry I think there was some confusion and in an attempt to start socializing this change it got thrown into the upcoming schedule.
| Assignee | ||
Comment 4•9 years ago
|
||
(In reply to Corey Shields [:cshields] from comment #3)
> (In reply to Kendall Libby [:fubar] from comment #2)
> > We had last talked about doing this at the following TCW. If we're really
> > doing it *THIS* weekend, the banner on BMO needs to get in place ASAP and we
> > need to verify that at least one of the devs is available this weekend.
>
> No, let's do this *next* TCW not 4/1. Sorry I think there was some
> confusion and in an attempt to start socializing this change it got thrown
> into the upcoming schedule.
Yes, completely agree here. Not sure where the signals got crossed, and I suspect I didn't entirely help on that front either.
My understanding was that this was going to happen 2 TCW aways, not this upcoming one, and the date was May 6th, IIRC.
Flags: needinfo?(gozer)
Comment 5•9 years ago
|
||
Great! I'm frankly ambivalent on the date, but it wasn't what we had discussed and so I wanted to either get us correctly set for this weekend or clear up any confusion. Success!
Flags: needinfo?(dylan)
Flags: needinfo?(dkl)
Updated•9 years ago
|
Assignee: kferrando → gozer
| Assignee | ||
Comment 6•9 years ago
|
||
Failover test complete and an overall success!
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•