11.01.13 Engineering Progress Report for Firefox Accounts and Sync.next
ckarlof at mozilla.com
Tue Nov 5 14:58:06 PST 2013
On Nov 5, 2013, at 3:51 AM, Lloyd Hilaiel <lhilaiel at mozilla.com> wrote:
> I continue to love these updates as a means of staying abreast of development and rooted in reality. thanks.
> On Nov 2, 2013, at 2:03 AM, Chris Karlof <ckarlof at mozilla.com> wrote:
>> Firefox Accounts wiki: https://wiki.mozilla.org/Identity/Firefox-Accounts
>> Sync.next wiki: https://wiki.mozilla.org/User_Services/Sync
>> Firefox Accounts API/Server/Client libraries (Danny Coates, Ryan Kelly, Zach Carter, Vlad Filippov)
>> - Landed new DB API supporting MySQL storage back end: https://github.com/mozilla/picl-idp/pull/254
> Is C* off the table? Where can I learn about our learnings?
1) IMO, it's way overkill for our current use case.
2) Our team can support MySQL in their sleep, but I can't say that for C*
3) The node driver for C* is immature.
4) Don't be too clever for well understood problems.
I encourage Danny or Ryan to add to this.
> Is MySQL a temporary thing or the path forward?
As temporary or permanent as anything else. We have no timeline or criteria to replace it. Danny and Ryan wrote the data store abstraction layer in the Auth Server to not rule out C*, but that's just because they're too wimpy to burn bridges. :)
> Finally, what is the sanest multi-region strategy available to us leveraging our mysql learnings from persona?
I think Benson and Gene covered this pretty well in the other thread.
1) Read slaves and hot standbys in other regions. (I am confident this will work well enough until we are insanely successful.)
2) Multi-master mode, slaving each other. (I don't know anyone with experience with this in production. If you do, speak up.)
>> - Experimentation with using SSE for checking email verification status: https://github.com/mozilla/picl-idp/tree/server-sent-events
>> - Work started on new JS FxA Web client: https://github.com/mozilla/gherkin
>> - Existing one was a gross fork of the Firefox Account integration testing client
>> - Decision: email verification will be clicking on a link and verifying intention by clicking another button on the landing page
>> - Firefox Accounts branding bug: https://bugzilla.mozilla.org/show_bug.cgi?id=930196
>> - Next steps: continue to work with UX on final UI for flows, continue work on Gherkin
>> Android (Nick Alexander, Richard Newman)
>> - Android UX sprint for November 6-8 in TO
>> - first try builds of native C pbkdf2_sha256 + script: https://bugzilla.mozilla.org/show_bug.cgi?id=915312
> Interesting. https://github.com/mozilla-services/android-sync/blob/2a70fa28f00ae0f75a686ceb764fa8ad418f7328/jni/scrypt/c/sha256.c
> So again, I’m wondering if taking a subset of this work and landing it in platform in a way that is decoupled from mainline Sync.next work could help out FirefoxOS and desktop?
>> - Next steps: start transition to native UI (i.e., away from hosted code): https://bugzilla.mozilla.org/show_bug.cgi?id=899217
>> Desktop (Chris Karlof, Brian Warner, Mark Hammond, Tim Taubert)
>> - Starting to landing FxA code that will support both Desktop and FxOS
>> - https://bugzilla.mozilla.org/show_bug.cgi?id=911384
>> - Almost completed migrating key fetching, email verification, public key generator, and assertion generator to browser code
>> - Next steps: Continue getting more tests working with the code from the work week, finish migrating about:accounts code to the browser, continue to land FxA common code in m-c
>> Firefox Accounts Devops (Benson Wong, Gene Wood, James Bonacci, Peter Dehaan)
>> - Completed deep dive into architecture
>> - New architecture doc: https://wiki.mozilla.org/Identity/Firefox-Accounts#Architecture
>> - Next steps: Start to build out provisioning logic, load testing of new MySQL architecture
>> Dev-fxacct mailing list
>> Dev-fxacct at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev-fxacct