Closed
Bug 844366
Opened 12 years ago
Closed 12 years ago
sync: deploy hekad-0.1.1-2 and metlog-py-0.10.0-1 to syncstorage prod
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
x86_64
Linux
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rmiller, Assigned: bobm)
References
Details
(Whiteboard: [qa+])
Attachments
(5 files, 1 obsolete file)
hekad and metlog-py have stood up well under functional testing and load testing in the sync staging environment, we're ready to have them in production. RPMs for both hekad and metlog-py are attached, as well as syncstorage.json config file (to be stored in /etc/mozilla-services/heka/syncstorage.json).
| Reporter | ||
Comment 1•12 years ago
|
||
| Reporter | ||
Comment 2•12 years ago
|
||
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bobm
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•12 years ago
|
||
Proposed puppet manifest changes for production heka deploy
Attachment #719195 -
Flags: review?(wdawson)
Comment 4•12 years ago
|
||
Comment on attachment 719195 [details]
Heka puppet manifest diffs for production sync heka deploy
You know what you did.
Attachment #719195 -
Flags: review?(wdawson) → review-
| Assignee | ||
Comment 5•12 years ago
|
||
New and improved puppet manifest changes!
Attachment #719248 -
Flags: review?(wdawson)
Comment 6•12 years ago
|
||
Comment on attachment 719248 [details]
Heka puppet manifest diffs for production sync heka deploy: Now with operational fixes!
It makes me angry, but go ahead and do it.
Attachment #719248 -
Flags: review?(wdawson) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
Production change scheduled here: https://intranet.mozilla.org/Services/Ops/ChangeWindow_20130305
Comment 8•12 years ago
|
||
I want to help out :bobm on this if there is time for some QA input/testing.
QA Contact: jbonacci
Comment 9•12 years ago
|
||
Sorry for the delayed response!
Services QA signs off on this release in Stage.
Let's get this into Prod!
Comment 10•12 years ago
|
||
Also, I want to add that the Stage testing was performed with the default configuration: single core.
We can open a new ticket and schedule more testing in Stage if we want to look at multi-core support.
| Assignee | ||
Comment 11•12 years ago
|
||
Change scheduled here: https://intranet.mozilla.org/Services/Ops/ChangeWindow_20130312
| Assignee | ||
Comment 12•12 years ago
|
||
Unable to deploy to production due to RPM conflict problem involving metlog that did not manifest during the stage deploy. The Sync staging environment is presently in use, but will investigate this problem there when available.
| Reporter | ||
Comment 13•12 years ago
|
||
Attachment #717408 -
Attachment is obsolete: true
| Reporter | ||
Comment 14•12 years ago
|
||
Comment on attachment 724464 [details]
python26-metlog-py-0.10.0-1.noarch.rpm
correct spelling for the rpm file name
Attachment #724464 -
Attachment description: correct spelling for metlog rpm → python26-metlog-py-0.10.0-1.noarch.rpm
| Assignee | ||
Comment 15•12 years ago
|
||
python26-metlog-py-0.10.0-1.noarch.rpm has been pushed back to stage, and Sync has been restarted without incident. Running a stage load test.
Comment 17•12 years ago
|
||
I am going to assume this is long since done.
:rmiller or :bobm can you mark this ticket?
| Assignee | ||
Comment 18•12 years ago
|
||
:jbonacci Actually, it hasn't. I am planning on rolling it out with this latest version of Sync 1.15-7 from Bug 854073 provided it passes QA.
| Assignee | ||
Comment 19•12 years ago
|
||
This has been deployed.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•