Closed
Bug 1204668
Opened 9 years ago
Closed 9 years ago
Please deploy shavar 0.6.5.2 to STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cloud-services-qa, Assigned: ckolos)
References
Details
------------------ RELEASE NOTES ------------------ https://github.com/mozilla-services/shavar/releases COMPARISONS https://github.com/mozilla-services/shavar/compare/0.6.4.2...0.6.5 https://github.com/mozilla-services/shavar/compare/0.6.5...0.6.5.1 https://github.com/mozilla-services/shavar/compare/0.6.5.1...0.6.5.2 TAGS https://github.com/mozilla-services/shavar/releases/tag/0.6.5.2 https://github.com/mozilla-services/shavar/commit/e02c421e04580064b074bbb51abdde22a174c957
Comment 1•9 years ago
|
||
------------------ Tag 0.6.5.2 ------------------ * Fix missing data freshness check NOTE: use new stage URL for e2e testing: shavar.stage.mozaws.net (tracking.stage.mozaws.net will now be used for diary study only)
Assignee: nobody → ckolos
QA Contact: rpappalardo
Comment 2•9 years ago
|
||
Production deployment has been re-scheduled for Wed. @1:30PST to allow time to for this stack to be deployed and tested.
Comment 3•9 years ago
|
||
:ckolos has deployed this release to STAGE, so marking fixed ================================ HOST CHECKS (STAGE) ================================ EC2 INSTANCE PROPERTIES region: us-east-1: tags["Type"]: shavar_server tags["AppGitRef"]: n/a tags["Stack"]: shavar-stage-87 ELB: shavar-stage-ELB1-1RSG0FI9ES1B, shavar-stage-ELB2-3S6LNEO29XPZ, shavar-stage-ELB3-STNM22PNI7RY launch_time: September 14, 2015 at 5:38:08 PM UTC-7 (17 hours) ================================ STACK-CHECK (STAGE) ================================ $ curl -d" " 'https://shavar.stage.mozaws.net/list?client=foo&appver=1&pver=2.2' mozfull-track-digest256 mozpub-shumway-digest256 mozpub-track-digest256 mozstd-track-digest256 mozstd-trackwhite-digest256 moztestpub-track-digest256 moztestpub-trackwhite-digest256 $ curl -d"mozstd-track-digest256;" 'https://shavar.stage.mozaws.net/downloads?client=foo&appver=1&pver=2.2' n:3600 i:mozstd-track-digest256 u:tracking-protection.stage.mozaws.net/mozstd-track-digest256/1442275596 $ curl -d"mozfull-track-digest256;" 'https://shavar.stage.mozaws.net/downloads?client=foo&appver=1&pver=2.2' n:3600 i:mozfull-track-digest256 u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1442275596
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 4•9 years ago
|
||
All e2e tests have passed. We did discover a UI bug with the whitelist test which :francois is investigating, but this isn't a blocker. ================================ E2E TESTS ================================ ---------------------------- List Delivery & Creation Tests ---------------------------- MOZTESTPUB LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK MOZSTD LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK MOZFULL LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK ---------------------------- List Additions / Deletions Tests ---------------------------- MOZTESTPUB LIST ..................... blacklist deletions ..................... * verify enabled - OK -- The resource at "https://extremetracking.com/" was blocked because tracking protection is enabled. * delete from blacklist - DONE * verify disabled - OK -- Your browser is not set up for tracking protection. Please check your setup and try again. ..................... blacklist additions ..................... * add to blacklist - DONE * verify enabled - OK ..................... whitelist deletions ..................... * verify enabled - DONE * delete from whitelist - DONE * verify disabled - OK - list blockage working correctly: googlesyndication is loaded in devtools and in NSPR logs - bug found with UI 'shield' element not appearing properly, but this isn't a blocker (francois to investigate)
Comment 5•9 years ago
|
||
:ckolos has redeployed 0.6.5.2 to stage w/ new config. re-verifying new 88 stack.... ================================ HOST CHECKS (STAGE) ================================ ---------------------------- HOST CHECKS (STAGE) ---------------------------- EC2 INSTANCE PROPERTIES region: us-east-1: tags["Type"]: shavar_server tags["AppGitRef"]: n/a tags["Stack"]: shavar-stage-88 public_dns_name: ec2-54-152-245-229.compute-1.amazonaws.com launch_time: 2015-09-16T18:21:11.000Z ELBs (routed to shavar.stage.mozaws.net): shavar-stage-ELB1-4KL66BCUQI70, shavar-stage-ELB2-2TKQGW882J9H ================================ STACK-CHECK (STAGE) ================================ $ curl -d" " 'https://shavar.stage.mozaws.net/list?client=foo&appver=1&pver=2.2' mozfull-track-digest256 mozpub-shumway-digest256 mozpub-track-digest256 mozstd-track-digest256 mozstd-trackwhite-digest256 moztestpub-track-digest256 moztestpub-trackwhite-digest256 $ curl -d"moztestpub-track-digest256;" 'https://shavar.stage.mozaws.net/downloads?client=foo&appver=1&pver=2.2' n:3600 i:moztestpub-track-digest256 u:tracking-protection.stage.mozaws.net/moztestpub-track-digest256/1442379603 $ curl -d"mozstd-track-digest256;" 'https://shavar.stage.mozaws.net/downloads?client=foo&appver=1&pver=2.2' n:3600 i:mozstd-track-digest256 u:tracking-protection.stage.mozaws.net/mozstd-track-digest256/1442275596 rpappalardo-17419:txt rpappalardo$ $ curl -d"mozfull-track-digest256;" 'https://shavar.stage.mozaws.net/downloads?client=foo&appver=1&pver=2.2' n:3600 i:mozfull-track-digest256 u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1442275596
Comment 6•9 years ago
|
||
Load Testing is complete on staging. Final results with 1 ELB scaled up in front of 9 c4.2xlarge's: ~3200 requests per second to each test instance at roughly 50-60% CPU load. Network in traffic was close to 100 mbit/s, disk and memory all well safe. Add that up and we have ~29k total request per second supported across all 9 instances. We feel this is safe for launch and we will monitor and tweak (up or down) as users update Firefox and also if we change the backoff from once an hour to once per day as the block list settles.
Comment 7•9 years ago
|
||
================================ E2E TESTS ================================ ---------------------------- List Delivery & Creation Tests ---------------------------- MOZTESTPUB LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK MOZSTD LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK MOZFULL LIST file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK ---------------------------- List Additions / Deletions Tests ---------------------------- MOZTESTPUB LIST ..................... blacklist deletions ..................... * verify enabled - OK -- The resource at "https://extremetracking.com/" was blocked because tracking protection is enabled.[Learn * delete from blacklist - * verify disabled - OK -- Your browser is not set up for tracking protection. Please check your setup and try again. ..................... blacklist additions ..................... * add to blacklist - DONE * verify enabled - OK - (verify in devconsole that googlesyndication is present) ..................... whitelist deletions ..................... * verify enabled - OK * delete from whitelist - DONE * verify disabled - OK - list blockage working correctly (verify in devconsole that googlesyndication is absent), but UI elements not appearing properly - Shield not appearing (seems to be a client bug)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•