Closed Bug 1283570 Opened 8 years ago Closed 8 years ago

Please re-deploy shavar 0.7 to STAGE - CONFIG CHANGES

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rpapa, Assigned: ckolos)

References

Details

Assignee: nobody → ckolos
QA Contact: rbillings
Deployed in stage: curl https://shavar.stage.mozaws.net/__version__ {"commit":"6b5ffd3a78da793e3830faf913a99293b07e0ea5","version":"0.7","source":"https://github.com/mozilla-services/shavar.git"}
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
thanks, :ckolos! ------------------------- NOTES ON THIS DEPLOY ------------------------- [1]. no longer serves: mozpub-track-digest256 [2]. update loadtests to query simultaneously: base-track-digest256, mozstd-trackwhite-digest256, mozplugin-block-digest256 (instead of mozpub-track-digest256) [3]. e2e-tests will largely remain unchanged (except for list removal/addition) COMMENTS [1]. I will update testplan wiki soon to reflect list changes: https://wiki.mozilla.org/Services/TrackingProtection/Shavar_Server_-_Testing [2]. We'll be adding a matrix to the testplan wiki with the following info to help coordination between Ops/Dev/QA: a. list name b. server-deploy - lists 2 add c. server-deploy - lists 2 remove d. client-version - lists 2 add e. client-version - lists 2 remove f. comments - ops/qa/dev
================================ STACK-CHECK (STAGE) ================================ $ curl -d" " 'https://shavar.stage.mozaws.net/list?client=foo&appver=1&pver=2.2' base-track-digest256 baseeff-track-digest256 basew3c-track-digest256 content-track-digest256 contenteff-track-digest256 contentw3c-track-digest256 mozfull-track-digest256 mozfullstaging-track-digest256 mozplugin-block-digest256 mozplugin2-block-digest256 mozstd-track-digest256 mozstd-trackwhite-digest256 mozstdstaging-track-digest256 mozstdstaging-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/1458773165 $ 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/1458773165
thanks :rbillings! - per IRC, we'll hold off on further verification till testplan has been updated with new files. LOADTEST NOTES from :francois #!/bin/sh curl --data-binary @- https://<shavar server>/downloads?pver=2.2 <<EOF mozstd-track-digest256;a:1 mozstd-trackwhite-digest256;a:1 mozplugin-block-digest256;a:1 EOF
=========================================== SHAVAR - SERVER-SIDE STACK-CHECK =========================================== TEST ENVIRONMENT: stage ----------------------------- DOWNLOAD LISTS ----------------------------- STAGE - shavar.stage.mozaws.net base-track-digest256 baseeff-track-digest256 basew3c-track-digest256 content-track-digest256 contenteff-track-digest256 contentw3c-track-digest256 mozfull-track-digest256 mozfullstaging-track-digest256 mozplugin-block-digest256 mozplugin2-block-digest256 mozstd-track-digest256 mozstd-trackwhite-digest256 mozstdstaging-track-digest256 mozstdstaging-trackwhite-digest256 moztestpub-track-digest256 moztestpub-trackwhite-digest256 ----------------------------- LIST: MOZSTD ----------------------------- RESPONSE: n:3600 i:mozstd-track-digest256 u:tracking-protection.stage.mozaws.net/mozstd-track-digest256/1458773165 EXAMPLE RESPONSE: n:3600 i:mozpub-track-digest256 u:tracking-protection.stage.mozaws.net/mozpub-track-digest256/1442275596 ----------------------------- LIST: MOZSTDSTAGING ----------------------------- RESPONSE: n:3600 i:mozstdstaging-track-digest256 u:tracking-protection.stage.mozaws.net/mozstdstaging-track-digest256/1465420870 EXAMPLE RESPONSE: n:3600 i:mozstdstaging-track-digest256 u:tracking-protection.stage.mozaws.net/mozstdstaging-track-digest256/1442275596 ----------------------------- LIST: MOZFULL ----------------------------- RESPONSE: n:3600 i:mozfull-track-digest256 u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1458773165 EXAMPLE RESPONSE: n:3600 i:mozfull-track-digest256 u:tracking-protection.stage.mozaws.net/mozfull-track-digest256/1442275596 ----------------------------- LIST: MOZFULLSTAGING ----------------------------- RESPONSE: n:3600 i:mozfullstaging-track-digest256 u:tracking-protection.stage.mozaws.net/mozfullstaging-track-digest256/1465420870 EXAMPLE RESPONSE: n:3600 i:mozfullstaging-track-digest256 u:tracking-protection.stage.mozaws.net/mozfullstaging-track-digest256/1442275596
---------------------------- LOADTESTS ---------------------------- SUMMARY Our original loadtesting target was to be able reach approx: 10-11K reqs/sec (mean) for 3 shavar nodes ~= 3.6K reqs/sec (mean) per 1 shavar node per :ckolos, this configuration is more than adequate for PROD. also, with auto-scaling we can go as high as 15 nodes current load on shavar PROD is approx: PROD: shavar 0.6.9 11K reqs/sec (mean) for 6 shavar nodes ~= 1.8K reqs/sec (mean per 1 shavar node TEST RESULTS load sustained by new release on STAGE is approx: STAGE: shavar 0.7.0 24K reqs/sec (mean) for 7 shavar nodes ~= 3.4K reqs/sec (mean) per 1 shavar node These results are consistent with previous shavar deployments. STAGE: shavar 0.6.5.2: https://bugzilla.mozilla.org/show_bug.cgi?id=1204668#c6 29K reqs/sec (mean) for 9 shavar nodes ~= 3.2K reqs/sec (mean) per 1 shavar node STAGE: shavar 0.6.9 https://bugzilla.mozilla.org/show_bug.cgi?id=1254279#c6 42K reqs/sec (mean) for 12 shavar nodes ~= 3.5K reqs/sec (mean) per 1 shavar node
E2E-TEST UPDATE - will try to complete by end of next week
--------------------------------------------- VERIFY LIST FILES CACHE / FILE SIZES --------------------------------------------- https://wiki.mozilla.org/Services/TrackingProtection/Shavar_Server_-_Testing#verify_list_files_cache MOZSTESTPUB ......................................... VERIFY: -track-digest256 < 100k ......................................... moztestpub-track-digest256.cache --> 55K moztestpub-track-digest256.pset --> 16B moztestpub-track-digest256.sbstore --> 62K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... moztestpub-trackwhite-digest256.cache --> 310K moztestpub-trackwhite-digest256.pset --> 16B moztestpub-trackwhite-digest256.sbstore --> 349K MOZSTD ......................................... VERIFY: -track-digest256 < 100k ......................................... mozstd-track-digest256.cache --> 55K mozstd-track-digest256.pset --> 16B mozstd-track-digest256.sbstore --> 62K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 310K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 349K MOZFULL ......................................... VERIFY: -track-digest256 < 100k ......................................... mozfull-track-digest256.cache --> 72K mozfull-track-digest256.pset --> 16B mozfull-track-digest256.sbstore --> 81K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 310K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 349K MOZSTAGING ......................................... VERIFY: -track-digest256 < 100k ......................................... mozstdstaging-track-digest256.cache --> 55K mozstdstaging-track-digest256.pset --> 16B mozstdstaging-track-digest256.sbstore --> 62K mozfullstaging-track-digest256.cache --> 72K mozfullstaging-track-digest256.pset --> 16B mozfullstaging-track-digest256.sbstore --> 81K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstdstaging-trackwhite-digest256.cache --> 310K mozstdstaging-trackwhite-digest256.pset --> 16B mozstdstaging-trackwhite-digest256.sbstore --> 349K
BASE ......................................... VERIFY: base-track-digest256 < 100k ......................................... base-track-digest256.cache --> 55K base-track-digest256.pset --> 16B base-track-digest256.sbstore --> 62K ......................................... VERIFY: baseeff-track-digest256 < 100k ......................................... baseeff-track-digest256.cache --> 12B baseeff-track-digest256.pset --> 16B baseeff-track-digest256.sbstore --> 196B ......................................... VERIFY: basew3c-track-digest256 < 100k ......................................... basew3c-track-digest256.cache --> 12B basew3c-track-digest256.pset --> 16B basew3c-track-digest256.sbstore --> 196B ......................................... VERIFY: content-track-digest256 is < 400k ......................................... content-track-digest256.cache --> 17K content-track-digest256.pset --> 16B content-track-digest256.sbstore --> 19K ......................................... VERIFY: content-track-digest256 is < 400k ......................................... content-track-digest256.cache --> 17K content-track-digest256.pset --> 16B content-track-digest256.sbstore --> 19K ......................................... VERIFY: contenteff-track-digest256 is < 400k ......................................... contenteff-track-digest256.cache --> 12B contenteff-track-digest256.pset --> 16B contenteff-track-digest256.sbstore --> 196B ......................................... VERIFY: mozstd-trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 310K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 349B
The last one is slightly incorrect - it has a duplicate content-track-digest256 and is missing contentw3c-track-digest. Corrected version: BASE ......................................... VERIFY: base-track-digest256 < 100k ......................................... base-track-digest256.cache --> 55K base-track-digest256.pset --> 16B base-track-digest256.sbstore --> 62K ......................................... VERIFY: baseeff-track-digest256 < 100k ......................................... baseeff-track-digest256.cache --> 12B baseeff-track-digest256.pset --> 16B baseeff-track-digest256.sbstore --> 196B ......................................... VERIFY: basew3c-track-digest256 < 100k ......................................... basew3c-track-digest256.cache --> 12B basew3c-track-digest256.pset --> 16B basew3c-track-digest256.sbstore --> 196B ......................................... VERIFY: content-track-digest256 is < 400k ......................................... content-track-digest256.cache --> 17K content-track-digest256.pset --> 16B content-track-digest256.sbstore --> 19K ......................................... VERIFY: contenteff-track-digest256 is < 400k ......................................... contenteff-track-digest256.cache --> 12B contenteff-track-digest256.pset --> 16B contenteff-track-digest256.sbstore --> 196B ......................................... VERIFY: contentw3c-track-digest256 is < 400k ......................................... contentw3c-track-digest256.cache --> 12B contentw3c-track-digest256.pset --> 16B contentw3c-track-digest256.sbstore --> 196B ......................................... VERIFY: mozstd-trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 310K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 349B
================================ E2E TESTS ================================ ---------------------------- List Delivery & Creation Tests ---------------------------- MOZTESTPUB LIST file delivery / filesizes - OK its-a-tracker page - [N/A] CNN page - OK YouTube page - [N/A] 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 MOZSTAGING file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK BASE file delivery / filesizes - OK its-a-tracker page - OK CNN page - OK YouTube page - OK
Whitelist test modified replacing googleanalytics and doubleclick.net. ================================ E2E TESTS ================================ ---------------------------- List Additions / Deletions Tests ---------------------------- MOZTESTPUB LIST ..................... blacklist deletions ..................... * verify enabled - OK * delete from blacklist - DONE * verify disabled - OK ..................... blacklist additions ..................... * add to blacklist - DONE * verify enabled - OK ..................... whitelist deletions ..................... * verify enabled - OK * delete from whitelist, re-verify - OK
================================ SUMMARY ================================ all e2e & load tests passing on STAGE verifying this release
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.