<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><br><div><div>On Nov 1, 2013, at 4:56 PM, Benson Wong <<a href="mailto:bwong@mozilla.com">bwong@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi, <br><br>I think the first step is figuring out what things look like from a high level: <br><a href="https://mana.mozilla.org/wiki/display/SVCOPS/Firefox+Accounts+Server+Layout">https://mana.mozilla.org/wiki/display/SVCOPS/Firefox+Accounts+Server+Layout</a><br><br></blockquote><div><br></div><div>I see that you're proposing RDS as our MySQL deployment.</div><div><br></div><div>Questions:</div><div>1) What's our general experience with RDS?</div><div>2) I don't think multi-region operation is a requirement for us at the moment, but it might be in the future. Can we continue to use RDS (which doesn't support multi-region repl), say by replicating to our own MySQL instances in other regions [1], or would we migrate away from RDS?</div><div><br></div><div>-chris</div><div><br></div><div>[1] <a href="https://aws.amazon.com/about-aws/whats-new/2013/09/05/amazon-rds-new-data-migration-capabilities-mysql/">https://aws.amazon.com/about-aws/whats-new/2013/09/05/amazon-rds-new-data-migration-capabilities-mysql/</a></div><div><br></div><div><br></div><br><blockquote type="cite">Then we can create the cloudformations. Let's stick w/ JSON. <br>Then we can craft the puppet stuff, scripts to build RPMs, etc. <br><br>There are a few goals I would like to do w/ FxA. I'm very flexible on these and willing <br>to let them slide to get the app live (first priority).<br><br>- empower Devs/QA to be able to deploy their own stacks at specific versions of the source.<br>- use a svc. ops shared service, heka? statsd? something<br>- integrate deeper w/ StackDriver. Perhaps even NewRelic's node.js client (if it's good enough)<br>- use Simple Work Flow + web interface for a GUI based deploy. Persona access controlled.<br><br>I'm mostly done w/ the Telemetry guy's ops. More accurately, they not blocked on ops stuff right now so this is my main focus. <br><br>Let's set up a meeting time next week to go over architecture w/ Ryan? <br><br>Ben<br><br><br>----- Original Message -----<br>From: "Gene Wood" <<a href="mailto:gene@mozilla.com">gene@mozilla.com</a>><br>To: "Mozilla Services Operations" <<a href="mailto:services-ops@mozilla.com">services-ops@mozilla.com</a>>, "Ryan Kelly" <<a href="mailto:rfkelly@mozilla.com">rfkelly@mozilla.com</a>><br>Cc: <a href="mailto:dev-fxacct@mozilla.org">dev-fxacct@mozilla.org</a><br>Sent: Friday, November 1, 2013 4:21:08 PM<br>Subject: Firefox Accounts DevOps next steps for November<br><br>Now that the MySQL connector code has been landed in the API Server for<br>Firefox Accounts we (Services Ops) should be clear to assemble the<br>provisioning for Firefox Accounts. I've begun work on the<br>CloudFormation/Cumulus environment provisioning code.<br><br>Benson, would it make sense for you to start on the masterless Puppet<br>provisioning code for the API Server at this point? I suspect that the lion<br>share of the provisioning behavior needed is represented in Ryan's bash<br>scripts here (<br><a href="https://github.com/mozilla/picl-deployment/tree/master/buildscripts">https://github.com/mozilla/picl-deployment/tree/master/buildscripts</a> ).<br><br>Ryan, can you give some more details on which of those scripts come into<br>play on the API server and in what order?<br><br>-Gene<br>_______________________________________________<br>Dev-fxacct mailing list<br><a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>https://mail.mozilla.org/listinfo/dev-fxacct<br></blockquote></div><br></body></html>