CloudServices/Meetings/2011-05-10
- Time: Tuesday at 9:15 AM PST / 12:15 PM EST / 5:15 PM UTC.
- Place: Mozilla HQ, North Bridge
- Phone (US/Intl): 650 903 0800 x92 Conf: 8616#
- Phone (Toronto): 416 848 3114 x92 Conf: 8616#
- Phone (US): 800 707 2533 (pin 369) Conf: 8616#
Who's away?: rnewman.
Contents
Ops
Load test cluster
Zeus configured, deploying reg/sreg/sync, fixing ACLs, smoke test expected this week.
Python reg/sreg
Staging and prod ldap ready for new code release to be tested/deployed on this week's train.
Ops work on hold per mconnor, pending results of planning meeting and potential client-only rewrite.
Engineering
Account Registration/Management
Python Registration Server (reg/sreg) (Tarek)
- deployment in dev/stage for account portal this week
- push planned next week
Account Portal (Toby)
Node Assignment (Toby)
Requires work on the auth library first: https://wiki.mozilla.org/Services/ServerCore/AuthRewrite
Sync
Python Sync Server (Tarek)
- waiting for the bench infra
PHP Sync Server (Toby)
Sync Client (rnewman)
Identity
Server (JR)
- New server spec (yay), reviewing and scoping changes.
- Talking with Rob about splitting tasks for new system. Addressing the differences.
Client (ddahl)
Latest patch is attached to bug 652653
Based on irc conversations from yesterday, I may want to wait to continue hacking on this until the 'final' plans and specs are in place
- We are holding at 2 http://www.youtube.com/watch?v=OyGcCwfBODk
- More updates as they are available
System Management
Big Lebowski (rtilder)
Notifications
- still need to sync with product, F1 stuff ate most of last week. - mconnor
QA
Testing and Sign-offs (tracy)
- Sync server push to prod on Monday passed live spot check. Tracked in bug 650328
- No s-c Sync client testing this week
- Will catch up on m-c Sync verifications this week
- Following bug 618913 - Implement in product notifications to set up Sync
- I'll make sure it is verified when fixed and notifications are covered in Fx team regression testing.
- Last weeks sreg/reg to python failed QA. Retrying for next train tracked https://wiki.mozilla.org/Services/User/Releases/0.2. Will test again Thursday.
Automated Testing (jgriffin)
Deployment Requests
As per the production release process any production change requests for the next release window (Monday afternoon) must be called out here by the developer requesting the update, with all required bugs/test plans already complete by the start of the meeting.
- Python Registration Server, bug 654148
Metrics
Reports and Monitoring (daniel)
Product
Sync
- Jennifer updating all feature pages for Sync. See Roadmap for all features.
- Looking at landing Sync Discoverability feature for FF6. Dev work done. Working on getting QA in the loop.
Security
- Weekly Train InfraSec Review Bug - 655763
- Security-Sensitive Client Services Bug - You should have access
- MozillaID Review Wiki Page
- v1 Documentation - will be updated with changes
- F1 (Share) Review Wiki Page
- v1 Documentation - will be updated with changes