Closed Bug 786479 Opened 12 years ago Closed 12 years ago

sync: server-storage stage deploy: server_storage -> 1.13-5, server_core -> 2.10-7

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rfkelly, Unassigned)

Details

(Whiteboard: [qa+])

Please deploy server-storage 1.13-5 and server-core 2.10-7 to stage sync server environments. Build command:

make build PYPI=http://pypi.build.mtv1.svc.mozilla.com/simple PYPIEXTRAS=http://pypi.build.mtv1.svc.mozilla.com/extras PYPISTRICT=1 SERVER_STORAGE=rpm-1.13-5 SERVER_CORE=rpm-2.10-7 CHANNEL=prod RPM_CHANNEL=prod build_rpms

This is an upgrade of server-core with the new gunicorn worker from Bug 786176, and a *downgrade* of server-storage after the not-very-successful 1.13-6 tag from Bug 784229.

To enable to new gunicorn worker, please edit the /service/gunicorn-syncstorage/run script and replace the current "-k gevent" option with "-k services.gunicorn_worker.MozSvcWorker".  No other config changes should be required.
Building.
Status: NEW → ASSIGNED
Deployed.  Only temporarily changing /service/gunicorn-syncstorage/run.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [qa+]
Loadtesting of this deployment conformed to our expectations and matched previous observations from server-storage 1.13-5.  No errors from couchbase, pylibmc identified as blocking the eventlopo, and regular __heartbeat__ request failures which would eventually lead to client-visible 503s.

For future reference, the loadtest graphs are August 28 from 18:45 through 20:00 PDT.  It will be interesting to compare these with 1.13-6 and 1.13-7 releases.
Good idea snapshotting the graph info!

Verified the webheads in Sync Stage:

sync*.web.scl2.stage.svc.mozilla.com
python26-services-2.10-7.noarch
python26-syncstorage-1.13-5.noarch
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.