Closed Bug 1252560 Opened 9 years ago Closed 9 years ago

Please deploy shavar 0.6.8 to STAGE

Categories

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

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: cloud-services-qa, Assigned: ckolos)

Details

Assignee: nobody → ckolos
QA Contact: rpappalardo
:ckolos has deployed 0.6.8 to STAGE. thank you! starting testing.... ---------------------------- HOST CHECKS (STAGE) ---------------------------- EC2 INSTANCE PROPERTIES region: us-east-1: id: i-716a7cf1 tags["Type"]: shavar_server tags["Stack"]: shavar-stage-117 public_dns_name: ec2-52-87-177-69.compute-1.amazonaws.com launch_time: 2016-02-23T19:58:59.000Z PROCESS CHECK python, uwsgi, datadog, shavar --> Running! ================================ STACK-CHECK (STAGE) ================================ :francois, I noticed some changes to the lists since 0.6.5.2 and just want to confirm this is correct. mozpub-shumway-digest256 is no longer there and that there are several new lists (marked NEW below) is this as expected? If so, then I'll need to update the testplan for STAGE: https://wiki.mozilla.org/Services/TrackingProtection/Shavar_Server_-_Testing#STAGE and I assume also for PROD? https://wiki.mozilla.org/Services/TrackingProtection/Shavar_Server_-_Testing#PRODUCTION $ curl -d" " 'https://shavar.stage.mozaws.net/list?client=foo&appver=1&pver=2.2' mozfull-track-digest256 mozfullstaging-track-digest256 [NEW] mozplugin-block-digest256 [NEW] mozplugin2-block-digest256 [NEW] mozpub-track-digest256 mozstd-track-digest256 mozstd-trackwhite-digest256 mozstdstaging-track-digest256 [NEW] mozstdstaging-trackwhite-digest256 [NEW] 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/1453241766 $ 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/1453241766
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(francois)
Resolution: --- → FIXED
per IRC chat w/ Francois: In regards to list changes: francois> the moztestpub lists are the end-to-end tests (for STAGE only) In regards to testplan changes: 11:37:04 AM <francois> I think the only thing I would add is that when you look at the downloaded lists, the size of the -staging lists should be similar to the other lists. 11:37:22 AM <francois> And the plugin blocking lists should be non-zero :)
Flags: needinfo?(francois)
Initial test results NOTE: test scripts: https://github.com/rpappalax/shavar-verify --------------------------------------------- VERIFY SERVER /download --------------------------------------------- https://wiki.mozilla.org/Services/TrackingProtection/Shavar_Server_-_Testing#Server-side_Test_Cases --------------------------------------------- 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 --> 51K moztestpub-track-digest256.pset --> 16B moztestpub-track-digest256.sbstore --> 58K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... moztestpub-trackwhite-digest256.cache --> 314K moztestpub-trackwhite-digest256.pset --> 16B moztestpub-trackwhite-digest256.sbstore --> 354K MOZSTD ......................................... VERIFY: -track-digest256 < 100k ......................................... mozstd-track-digest256.cache --> 53K mozstd-track-digest256.pset --> 16B mozstd-track-digest256.sbstore --> 60K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 301K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 339K MOZFULL ......................................... VERIFY: -track-digest256 < 100k ......................................... mozfull-track-digest256.cache --> 70K mozfull-track-digest256.pset --> 16B mozfull-track-digest256.sbstore --> 78K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstd-trackwhite-digest256.cache --> 301K mozstd-trackwhite-digest256.pset --> 16B mozstd-trackwhite-digest256.sbstore --> 339K MOZSTAGING ......................................... VERIFY: -track-digest256 < 100k ......................................... mozstdstaging-track-digest256.cache --> 53K mozstdstaging-track-digest256.pset --> 16B mozstdstaging-track-digest256.sbstore --> 60K mozfullstaging-track-digest256.cache --> 70K mozfullstaging-track-digest256.pset --> 16B mozfullstaging-track-digest256.sbstore --> 78K ......................................... VERIFY: -trackwhite-digest256 is < 400k ......................................... mozstdstaging-trackwhite-digest256.cache --> 301K mozstdstaging-trackwhite-digest256.pset --> 16B mozstdstaging-trackwhite-digest256.sbstore --> 339K
NOTE ON PLUGINS TEST PAGE: A a different test page will need to be created at itisatrap.org/firefox/blocked.html (which doesn't exist yet)
================================ 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
NOTE ON LOADTEST TARGET: autoscale 3->9, 10-11K RPS
================================ E2E TESTS ================================ ---------------------------- 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 ..................... * test will need to be repeated NOTES FROM FRANCOIS: googlesyndication seems a little bit unreliable since for devedition I had to clear the cache and reload the page a few times before the shield appeared. So I would suggest a small change to the test script: - instead of removing googlesyndication.com from the whitelist, try removing googleanalytics.com I think it will work better than googlesyndication because they will always load their analytics script whereas they may not always load all of their ad scripts.
================================ SUMMARY ================================ Closing this ticket out in favor of a new 0.6.9 tag w/ fixes see: Bug 1254279 - Please deploy shavar 0.6.9 to STAGE Adding notes below from loadtesting done on 0.6.8 ---------------------------- LOADTESTS ---------------------------- with auto-scaling, able to push shavar up to 36K RPS. 3 hosts (without autoscaling) will run ~ 10K/s So, we'll deploy 3 hosts and let it scale from there. per ckolos, this configuration will more than adequate for PROD.
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.