CloudServices/Loop/WeeklyStandup/2014-06-10: Difference between revisions
< CloudServices | Loop | WeeklyStandup
Jump to navigation
Jump to search
(Created page with "Live notes can be viewed at: https://etherpad.mozilla.org/Loop-2014-06-10") |
No edit summary |
||
Line 1: | Line 1: | ||
=Reference Docs= | |||
* MVP Tasks: https://bugzilla.mozilla.org/showdependencytree.cgi?id=971986&hide_resolved=1 | |||
* Wiki: https://wiki.mozilla.org/CloudServices/Loop | |||
* Loop MVP User Stories: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlJmiyFngeSwdGJEVnItQ2NVbGx6NXdjbVBUYmIxSGc#gid=0 | |||
* Backlog User Stories: https://docs.google.com/a/mozilla.com/spreadsheets/d/1r_zkWTbold5dlA5vh8P4xugTmRlfYQo5mUAuYc2qAxQ/edit#gid=1480050446 | |||
* Loop Server: https://docs.services.mozilla.com/loop/index.html | |||
* Design Docs: https://people.mozilla.org/~dhenein/labs/loop-docs/ | |||
* Fernando's proposal: https://wiki.mozilla.org/Loop/Architecture/ID | |||
* Chris's phone number verification strawman: https://github.com/mozilla/fxa-auth-server/wiki/API-extensions-for-supporting-MSISDN-verification-in-FxA-auth-server | |||
* TEF Mobile roadmap: https://fxosroadmap.aha.io/published/e0d1cbf8cd519bea36a3053355b6d1f7?page=1 | |||
* Loop Dev Schedule: https://drive.google.com/a/mozilla.com/file/d/0B1KBl68pRmhsMmhqQXM3SVE2ZkE/edit?usp=sharing | |||
* wiki https://wiki.mozilla.org/Media/Webrtc | |||
** extended team list: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlKBl68pRmhsdENBZDRKclBSZlhiRC1tb1BGQS1JU2c&usp=drive_web#gid=0 | |||
=Agenda= | |||
* Status update server side | |||
** We are in nightlies! | |||
* UX update: | |||
** Link to initial Loop + FxA OAuth flows below: | |||
*** https://www.dropbox.com/s/xywjgd3oqo7e19j/Loop-FxA-OAuth.pdf | |||
*** this is a work in progress please provide any feedback or questions to John | |||
* Follow-up from last meeting: | |||
** FxA for Desktop | |||
*** Contract commitment for FxA authentication to desktop by Fx34 - need by Fx33 to be able to leverage for Fx34 | |||
* Discuss improving our communication process with DevOps | |||
** Bob and Wes can be a back up for Benson | |||
** Benson will take lead on MSISDN deployment | |||
=Notes= | |||
* we need to make sure we have all the tooling in place on server side for debugging | |||
* We are on schedule for MSISDN | |||
** we need to synchronize schedules to ensure we are all on the same page | |||
** TEF client side is ready | |||
** ready to deploy MSISDN on stage & production | |||
** session token expiration | |||
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1022678 | |||
* discuss sizing of redis (elasticache) for loop-production | |||
* dev relay info for msisdn deployment - configuration, sms endpoint settings, etc | |||
** https://github.com/mozilla-services/msisdn-gateway | |||
* QA in progress | |||
** Anthony Hughes is primary QA contact for Loop/TokBox | |||
** Would Tokbox be interested in using our load testing cluster? - Edwin to follow-up with Anthony | |||
* Deployment Discussion: | |||
**usage = nbUsers * 280 + nbCallsPerDay * 1365 + nbUrlRevocationPerMonth * 150 + 600000 (bytes) | |||
** nbCallsPerDay is let's say 10 | |||
** Note that we have a redesign coming down the pipe that will store URL information on the server instead of having it as part of the URL itself. | |||
**MSISDN overview for Benson | |||
*** https://github.com/mozilla-services/msisdn-gateway | |||
*** architecture is not a problem | |||
*** phone number configuration for each country is where it will get tricky |
Latest revision as of 16:46, 10 June 2014
Reference Docs
- MVP Tasks: https://bugzilla.mozilla.org/showdependencytree.cgi?id=971986&hide_resolved=1
- Wiki: https://wiki.mozilla.org/CloudServices/Loop
- Loop MVP User Stories: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlJmiyFngeSwdGJEVnItQ2NVbGx6NXdjbVBUYmIxSGc#gid=0
- Backlog User Stories: https://docs.google.com/a/mozilla.com/spreadsheets/d/1r_zkWTbold5dlA5vh8P4xugTmRlfYQo5mUAuYc2qAxQ/edit#gid=1480050446
- Loop Server: https://docs.services.mozilla.com/loop/index.html
- Design Docs: https://people.mozilla.org/~dhenein/labs/loop-docs/
- Fernando's proposal: https://wiki.mozilla.org/Loop/Architecture/ID
- Chris's phone number verification strawman: https://github.com/mozilla/fxa-auth-server/wiki/API-extensions-for-supporting-MSISDN-verification-in-FxA-auth-server
- TEF Mobile roadmap: https://fxosroadmap.aha.io/published/e0d1cbf8cd519bea36a3053355b6d1f7?page=1
- Loop Dev Schedule: https://drive.google.com/a/mozilla.com/file/d/0B1KBl68pRmhsMmhqQXM3SVE2ZkE/edit?usp=sharing
- wiki https://wiki.mozilla.org/Media/Webrtc
Agenda
- Status update server side
- We are in nightlies!
- UX update:
- Link to initial Loop + FxA OAuth flows below:
- https://www.dropbox.com/s/xywjgd3oqo7e19j/Loop-FxA-OAuth.pdf
- this is a work in progress please provide any feedback or questions to John
- Link to initial Loop + FxA OAuth flows below:
- Follow-up from last meeting:
- FxA for Desktop
- Contract commitment for FxA authentication to desktop by Fx34 - need by Fx33 to be able to leverage for Fx34
- FxA for Desktop
- Discuss improving our communication process with DevOps
- Bob and Wes can be a back up for Benson
- Benson will take lead on MSISDN deployment
Notes
- we need to make sure we have all the tooling in place on server side for debugging
- We are on schedule for MSISDN
- we need to synchronize schedules to ensure we are all on the same page
- TEF client side is ready
- ready to deploy MSISDN on stage & production
- session token expiration
- discuss sizing of redis (elasticache) for loop-production
- dev relay info for msisdn deployment - configuration, sms endpoint settings, etc
- QA in progress
- Anthony Hughes is primary QA contact for Loop/TokBox
- Would Tokbox be interested in using our load testing cluster? - Edwin to follow-up with Anthony
- Deployment Discussion:
- usage = nbUsers * 280 + nbCallsPerDay * 1365 + nbUrlRevocationPerMonth * 150 + 600000 (bytes)
- nbCallsPerDay is let's say 10
- Note that we have a redesign coming down the pipe that will store URL information on the server instead of having it as part of the URL itself.
- MSISDN overview for Benson
- https://github.com/mozilla-services/msisdn-gateway
- architecture is not a problem
- phone number configuration for each country is where it will get tricky