QA/BrowserID/OPsBuildOut: Difference between revisions

From MozillaWiki
< QA‎ | BrowserID
Jump to navigation Jump to search
Line 307: Line 307:
| valign="top" | Work with OPs: initial Dev test  
| valign="top" | Work with OPs: initial Dev test  
| valign="top" | lloyd/petef  
| valign="top" | lloyd/petef  
| valign="top" | in progress
| valign="top" | On track for week of 11/28
| valign="top" |  
| valign="top" |  
* See bullets below
* See bullets below
Line 314: Line 314:
| valign="top" | Work with OPs: code for Stage  
| valign="top" | Work with OPs: code for Stage  
| valign="top" | lloyd/petef  
| valign="top" | lloyd/petef  
| valign="top" | in progress
| valign="top" | On track for week of 11/28
| valign="top" |  
| valign="top" |  
* Important open issues for Dev and Stage:
* Important open issues for Dev and Stage:
Line 322: Line 322:
* 566: heartbeat should not check backend servers
* 566: heartbeat should not check backend servers
* 582: improved file based configuration
* 582: improved file based configuration
|-
| valign="top" | better logging
| valign="top" |
| valign="top" | in progress
| valign="top" |
* GitHub: various issues


|-
|-
| valign="top" | Work with OPs: load test code and deploy  
| valign="top" | Work with OPs: load test code and deploy  
| valign="top" | lloyd/petef  
| valign="top" | lloyd/petef  
| valign="top" | in progress
| valign="top" | On track for week of 11/28
| valign="top" |  
| valign="top" |  
*Bug 695952  
*Bug 695952  

Revision as of 18:02, 28 November 2011

Back To ==> Mozilla BT Services

Intro

This is the main QA site for the BrowserID OPs Build-Out. All tasks, projects, status, and other important information related to the Build-Out will be listed here and updated frequently.

  • Overall/Master Schedule (details): to be added
  • Build-Out Schedule per four environments: November/December
  • Deployment Schedule per four environments: November/December
  • Load Test Schedule per four environments: November/December
  • QA Test Schedule per four environments: November/December

QA

Task/Project Owner Status Notes, Links, Tickets, Issues
Track OPs BrowserID build-out planning and HW orders jbonacci completed
  • see Bug 697477
BrowserID arch review jbonacci completed
Track RPM and deployment work in Dev jbonacci completed
  • see Bug 695596
Track Dev build-out jbonacci completed
  • see Bug 695957
Track Stage build-out jbonacci completed
  • see Bugs 695941, 695944
Track Prod build-out jbonacci planned
  • see Bugs 695941, 695943, 695946, 695955, 695956, 695960, 695972, 698044
Track Test/CI build-out jbonacci planned
  • see Bug 695958
Track DEV load test development jbonacci On track for week of 11/28
  • see Issue 504
Track OPs load test deployment jbonacci On track for week of 11/28
  • see Bug 695952
Track OPs dashboard/monitoring work jbonacci in progress
  • see Bugs 695961, 695963, 695967
Load test tutorial jbonacci planned
  • none
Logging for QA work jbonacci planned
  • QA generated scripts for capturing log information per service
Monitoring/dashboards tutorial jbonacci planned
  • Pencil will be used for dashboard, so tutorial should be similar to that used for Sync
Stability testing Dev env QA On track for week of 11/28
Stability testing Stage env QA On track for week of 11/28
Load testing Stage env QA/OPs On track for week of 11/28
  • none
Stability testing Prod env QA planned
  • need help from Dev and OPs
Stability testing Test/CI env QA planned
  • need from with Dev and OPs
QA node/npm "easy" installs jbonacci ongoing
Discussion of Android compatibility for BrowserID QA/Dev completed
  • 2.2, 2.3, 3.x and newer vs. supporting older versions
  • Percentage-wise (of users) 2.2 and newer seems ok
Complete ID2 configuration jbonacci/lloyd/petef On track for Work Week
  • working with Lloyd and Pete on this
QA RPM installs to ID2 jbonacci On track for Work Week
  • need RPM info from Dev and OPs
QA Test Plan updates jbonacci ongoing
QA Test wiki updates jbonacci ongoing
Client-side BrowserID automation jbonacci planned
  • Meeting week of 11/28 to talk CI/Selenium
Server-side BrowserID automation jbonacci planned
  • Need to work with Shane and Austin to see what we can come up with
  • Work Week
BrowserID and AMO integration/automation jbonacci planned
  • Meeting week of 11/28 to talk AMO/BrowserID automation/integration



Dev

Task/Project Owner Status Notes, Links, Tickets, Issues
Initial plan for Scaling to 1 million users Dev team completed
Metrics dashboard Dev team completed
  • see Bug 690107
Maintain "all-in-one" BrowserID lloyd ongoing
  • none
GitHub repository reorganization lloyd completed
  • Issue 503: improve repository organization
Better logging lloyd in progress
  • GitHub Issues 119, 537, 541, 536, 530, 529, etc.
Process splitting: browserid, verifier, keysigner, dbwriter lloyd completed
  • GitHub Issue 460
Second client (dev.)(beta.)myfavoritebooze.org lloyd completed
  • support 'keep me signed in' feature
Developer Engagement Plan Dev/PM teams completed
Crypto discussions and work Dev/Security teams ongoing
  • GitHub issues: various
Work with OPs: RPM creation for deployment lloyd/petef completed
  • Bug 695956
Work with OPs: Dev deployment lloyd/petef completed
  • Bug 695957
Work with OPs: initial Dev test lloyd/petef On track for week of 11/28
  • See bullets below
Work with OPs: code for Stage lloyd/petef On track for week of 11/28
  • Important open issues for Dev and Stage:
  • 504: repair load_gen
  • 560: move bcrypt to webhead
  • 561: handle mysql master failover in dbwriter process
  • 566: heartbeat should not check backend servers
  • 582: improved file based configuration
Work with OPs: load test code and deploy lloyd/petef On track for week of 11/28
  • Bug 695952
  • Issue 504: repair load_gen
Update GitHub Scaling to 1M lloyd completed


Table for OPs

Task/Project Owner Status Notes, Links, Tickets, Issues
Build-out planning OPs completed
VM setup/config for Dev and Test/CI petef completed
HW orders for Prod:SCL2 OPs status?
HW orders for Prod:PHX1 OPs status?
HW orders for Stage OPs completed
Logging petef in progress
  • Bugs 695916, 695963, 695967
  • /var/log/browserid on webheads, secure webheads, keysigners
  • /var/log/zeus on Zeus servers
  • TBD for database
Metrics petef in progress
  • Bugs 695916, 695963, 695967
RPM design/build/test petef/lloyd completed
  • Bug 695956
  • Latest pull request was 11/14
Jenkins/Hudson for BrowserID-Server petef completed
Set up Load test env petef completed
  • Bug 695952
Zeus configuration petef in progress
  • Bug 695943
MySQL petef in progress
  • Bug 695972
  • mysql replication/monitoring strategy fleshed out (doc coming)
  • DB/MySQL failover work, Bug 695972
Dev environment deploy and test petef/lloyd in progress
  • Bug 695957
  • 11/7-11/14 DEV env build-out and test deployments
  • First official deploymant: train-2011.11.17
  • Dev Server: https://dev-browserid.services.mozilla.com
  • Dev RP (temp): http://beer.mtv1.dev.svc.mozilla.com
  • OPs needs to configure persistence on the test beer site otherwise beer names are not sticking across sessions
  • Need to see what happens on Stage (once it is up and running again)
  • OPs needs to puppetize and config mongodb on Dev, so my guess is Stage will need this also
Stage environment deploy and test petef/lloyd in progress
Stage environment load test petef/QA planned
  • Planned: benchmarks and performance in Stage.
Prod environment deploy and test petef planned
  • Bugs 695946, 695960, 698044
Test/CI environment deploy and test petef planned
Other: working with infra-sec on documentation, vuln scans, more reliable CEF logging, and RSBAC rollout OPs in progress
  • none
Puppet configuration (transferable to Stage) OPs in progress
  • Bug 695956
RSBAC work OPs in progress
  • Bug 695955


Quick Summaries/History: July - Oct

QA:

  • Focus for Summer and Fall
    • Weekly deployments to Beta environment
    • Verification of deployments to current Production environment
    • Test Plan and Weekly Trains wikis
  • Tracking Dev activity for scaling to one million users
  • Tracking OPs activity for BrowserID environment build-outs

DEV:

  • Scalability planning started in the Summer.
  • Planning path for security review and production build-out was started in the Summer.
  • Metrics dashboard for identity
  • Code migration to MySQL
  • Command-line load generation and performance analysis
  • Debug improvements
  • Other areas shared with OPs: monitoring, logging improvements, RPM generation script, schema changes to improve database performance and scalability

OPs:

  • BrowserID env designs
  • Capacity planning
  • Hardware was ordered in October
  • Dev environment planning, build-out and configuration was started
  • RPM generation work was started
  • Other areas of work: node cluster, mysql strategy, monitoring strategy, logging, DB performance, scalability, zeus vips setup, nginx/apache, webhead/secure webhead planning
  • Dependent on Dev for keysigner design and split, dbwriter design and split, logging improvements, repository restructuring, process split, code integration for packaging, and the load-gen code
  • REF: Bug 695940 - BrowserID production tracking bug

Important Links


OPs Tickets

  • Bug 695940 - BrowserID production tracking bug
    • This is a meta bug for all the other OPs tickets


Other Tickets

  • Bug 690107 - Build dashboards for identity
  • Bug 644776 - Security Review For BrowserID
  • Bug 692247 - Accessibility review for revised design of BrowserID
  • Bug 694073 - Need socketlabs SMTP parameters for browserid
  • Bug 650863 - SSL cert needed for browserid.org
  • Bug 695955 - browserid: write rsbac security policies for all host types


GitHub Issues


BrowserID Environments

See the main OPs BrowserID site for full details:


Load Testing

  • Load_Gen code and test - Dev work is still in progress
  • See the following bug and issue:
    • Bug 695952 - browserid: loadtest
    • Issue 504: repair load_gen
  • Load Test hardware (per OPs)
    • There are eight dedicated client machines to send load
      • Need machine name information
    • There is also a dedicated VLAN that does not hit the firewall to push more load, if required.
  • Load Test information per four environments: TBD


Dashboards and Monitoring


Bugs vs. GitHub Issues

  • TBD


Back To ==> Mozilla BT Services