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)

x86_64
Linux
task
Not set
normal

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).
Attached file metlog-py-0.10.0-1.noarch.rpm (obsolete) —
Assignee: nobody → bobm
Status: NEW → ASSIGNED
Proposed puppet manifest changes for production heka deploy
Attachment #719195 - Flags: review?(wdawson)
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-
New and improved puppet manifest changes!
Attachment #719248 - Flags: review?(wdawson)
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+
I want to help out :bobm on this if there is time for some QA input/testing.
QA Contact: jbonacci
Sorry for the delayed response! Services QA signs off on this release in Stage. Let's get this into Prod!
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.
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.
Attachment #717408 - Attachment is obsolete: true
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
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.
:bobm how are those load tests in stage?
Whiteboard: [qa+]
I am going to assume this is long since done. :rmiller or :bobm can you mark this ticket?
: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.
This has been deployed.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified across PHX1 and SCL2.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: