stable.dev.lcip.org needs some downtime to change it to the fxa-dev docker branch

[John Morrison]

Apologies, in advance. `stable.dev.lcip.org` has not been moved to the 
docker branch that other fxa-dev instances use.


I've made the changes to the docker branch that allow it to use a 
persistent RDS database, but in order to change stable to use that, it 
will require some downtime to make the switch.


I'd like to make that change tomorrow, so let me know if you have a 
problem with that timing.


John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: Can we npm5/node6 all the things?

[John Morrison]

On 08/14/17 17:40, Ryan Kelly wrote:
On 15 August 2017 at 10:20, Sean McArthur > wrote:



*tl;dr *- Let's upgrade all our stuff to npm5, and remove node4
support, so we can live in the bright new future!


Thanks for kicking off this discussion, Sean!  John and Jon, I'm 
particularly interested to know whether either of these changes would 
be scary from an ops/deployment perspective.
I'm +1 on moving to npm5. The travis and circle-ci instructions would 
need to to be changed to install npm@5.


Other things:
- there's some leftover CXX=g++-4.8 stuff that I think can be removed 
now (it was for older linux distros)
- I thought the `npm shrinkwrap` loop was known and had been fixed in 
some repos (but maybe I misremember)
- I do think there are some places/scripts that reach into 
`./node_modules/foo/node_modules/bin/bar.js`, but it just needs a 
grep-audit to discover them/any.
- (I'll mildly note that the yarn spin about npm isn't accurate, but I 
don't really care: Subresource integrity checks are the true way).
- By the way, we're also probably due to use node8, but let's do the 
cleanup for node6/npm5 now.


John



   Cheers,

 Ryan


___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct



___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

latest.dev.lcip.org is now running docker images

[John Morrison]

latest.dev.lcip.org is now running docker images

John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: train-90 planning summary

[John Morrison]

On 06/14/17 19:50, Ryan Kelly wrote:
* Verification reminders enabled in production, after successfully 
disabling DB replication for that table.


This is actually live in production now (not adding new emails to the 
verificationReminders table, but processing the backlog in the 
background, and no replication lag at this point).


John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: device registration traffic (was re: meeting summary: backend chat, 2017-02-07)

[John Morrison]

To update, here are peak daily values values: route 
postaccountuiddevicedeviceidupdate


Tue 01/31  839
Wed 02/01  902
Thu 02/02 1065
Fri 02/03  960
Sat 02/04  898
Sun 02/05  859
Mon 02/06 1115
Tue 02/07 1648
Wed 02/08 1258
Thu 02/09 1079

So, appears to be abating.

For access to Kibana, contact Wesley Dawson w...@mozilla.com

On 02/08/17 11:12, Ryan Kelly wrote:

On 9/2/17 05:04, Grisha Kruglov wrote:

Date/time matches the 100% rollout of 51 fennec on Play Store.

Device registration version was bumped in 51 from 1 to 2 in
https://bugzilla.mozilla.org/show_bug.cgi?id=1298727 to "to force
devices to re-register themselves (and send the Push callback url to FxA)".
See https://bugzilla.mozilla.org/show_bug.cgi?id=1298727

Most likely this is what you're seeing, devices re-registering
themselves during a sync.

Great, thanks Grisha!  Sounds like we should expect this traffic to
subside once the installed device population finishes the update.



   Cheers,

 Ryan




On Tue, Feb 7, 2017 at 8:16 PM, Nicholas Alexander
> wrote:

 +grisha,

 I think Grisha is most likely to know if things have changed here.

 Nick

 -- Forwarded message --
 From: *Ryan Kelly* >
 Date: Tue, Feb 7, 2017 at 8:13 PM
 Subject: device registration traffic (was re: meeting summary:
 backend chat, 2017-02-07)
 To: dev-fxacct >, Stefan Arentz >



 On 8/2/17 14:03, Ryan Kelly wrote:
 >
 > Earlier today we had our weekly backed-focussed catchup and we talked
 > about the following:
 > [...]
 > * The last couple of days have seen a marked uptick in db requests to
 >   update an existing device record.  We need to attempt a bit of user-
 >   agent analysis to see whether this is an early warning of changing
 >   traffic patterns in client code.

 It looks like this uptick in device registration traffic is due to
 Android.  See this kibana graph:


 
https://kibana-fxa-us-west-2.prod.mozaws.net/index.html#dashboard/temp/AVob5ra0TlXM2FwOCRjp
 


 Or the attached carefully-redacted screenshot.

 Stefan, was there a new Firefox for Android release recently that might
 have included changes to FxA device registration?


   Cheers,

 Ryan

 ___
 Dev-fxacct mailing list
 Dev-fxacct@mozilla.org 
 https://mail.mozilla.org/listinfo/dev-fxacct
 




___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct



___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: US holiday on Monday - reschedule meetings until Tuesday?

[John Morrison]

I'm easy either way.

On 01/13/17 02:37, Phil Booth wrote:
Works for me, although the 2nd half of the morning meeting would clash 
with the monthly internal meeting in that case (but I don't mind 
watching the recording).


On Fri, Jan 13, 2017 at 9:39 AM, Shane Tomlinson 
> wrote:


Hey all, you probably all saw Potch's email about it being MLK Jr
Day in the US, and a third of our team will be absent from the
meetings. I propose we reschedule all meetings to Tuesday, same time.

Shane

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org 
https://mail.mozilla.org/listinfo/dev-fxacct





___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct



___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: meeting summary: backend catchup, 2016/09/27

[John Morrison]

On 09/27/16 19:42, Ryan Kelly wrote:

* The long-running task of purging many gigabytes of expired oauth
   tokens is temporarily paused while the Firefox 49 release rolls out,
   since Firefox releases can lead to unexpected spikes in db write load.


Minor correction (maybe just a typo). This uptick is expected, and fine.

John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: London Planning Recap

[John Morrison]

On 06/20/16 09:15, Sean McArthur wrote:

# Quality

  * nodejs 4.0 LTS
  o 0.10 EOL is October 
  o All repos pass tests on 4.0
  o Docker makes this easier, but dockerization may take too long


On this point, the work to run 4.0 in production was completed months ago.

It would have been live now, but for unexpected events. I'd like to just 
do this in the next couple of trains, and be done with it.


John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: Project call overlaps with Web Coordination Bug Scrub

[John Morrison]

Yeah, I was thinking about this as I drove in. Nevermind. Was 
misinformed by the Milestone settings on fxa-content-server.


John

On 08/17/15 08:53, Shane Tomlinson wrote:

Hey John,
Yeah, Vlad is correct, though someone could chime in and tell us we 
are nuts. We have shifted the schedule by 1 week to align with the 
Firefox desktop calendar. Train 44 is tagged next week. The FxA 
Project calendar should be updated with the new schedule.


Shane

On Mon, Aug 17, 2015 at 4:46 PM, Vlad Filippov vfilip...@mozilla.com 
mailto:vfilip...@mozilla.com wrote:


Well, today is also the end of train-44. Zaach (or other) can you
tag fxa-content-server? Thanks.

Wait, what? Didn't we just have a train planning meeting last week?

Vlad.

On Mon, Aug 17, 2015 at 11:12 AM, John Morrison
jmorri...@mozilla.com mailto:jmorri...@mozilla.com wrote:

Well, today is also the end of train-44. Zaach (or other) can
you tag fxa-content-server? Thanks.

John


On 08/17/15 07:53, Shane Tomlinson wrote:

Heya!

Vlad just brought up that today's Mozilla internal meeting
overlaps with the FxA Web Coordination and Bug Scrub meetings.

Since we have an FxA wide meeting later today, there seems
to be no real harm in canceling the web coordination
meeting and asynchronously filling out our status in the
etherpad [1].

I propose we move bug scrub to tomorrow at the same time.
What do folks think?

Shane

---

[1] - https://id.etherpad.mozilla.org/fxa-web-coordination






___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: Project call overlaps with Web Coordination Bug Scrub

[John Morrison]

Well, today is also the end of train-44. Zaach (or other) can you tag 
fxa-content-server? Thanks.


John

On 08/17/15 07:53, Shane Tomlinson wrote:

Heya!

Vlad just brought up that today's Mozilla internal meeting overlaps 
with the FxA Web Coordination and Bug Scrub meetings.


Since we have an FxA wide meeting later today, there seems to be no 
real harm in canceling the web coordination meeting and asynchronously 
filling out our status in the etherpad [1].


I propose we move bug scrub to tomorrow at the same time. What do 
folks think?


Shane

---

[1] - https://id.etherpad.mozilla.org/fxa-web-coordination


___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: train-41 shortened dev cycle?

[John Morrison]

On 07/01/15 10:53, Ryan Kelly wrote:

Hi All,

As noted in the engineering standup on Monday, we cut train-40 a week
late due to Whistler, so we're currently off our standard release cycle.
  Let's try to get back on schedule ASAP by doing a short dev cycle for
train-41.

What this would mean in practice:

* Train-40 is going into production a week later than it ordinarily
   would have, week of Monday 6th July.

* Let's cut train-41 on schedule, also week of Monday 6th July.

* To ensure a smooth and simple release, let's avoid any string changes
   for train-41.

Does this sound OK?  :jrgm, how does this sound from your perspective?



Sure I suppose it works. But I thought it was already settled that it 
wouldn't be next week.


John

___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: FxA Engineering Coordination notes; June 1st 2015

[John Morrison]

On 06/01/15 22:04, Ryan Kelly wrote:

* Train 38 is deployed in production as of this afternoon.

There was a small hiccup with fxa-customs-server losing its ability to
talk to memcache [2] but otherwise things went smoothly.  You can view
the change summary at [3].
Small clarification: the problem with the fxa-customs-server was not 
related to train-38 deployment as the affected server had begun having 
problems before the deployment of train-38.


John


___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: new FxA dev environment proposal

[John Morrison]

On 12/08/14 11:59, Renoir Boulanger wrote:

- Have no access to dcoates/fedora20
Did you perhaps mean dannycoates/fedora20? Does `vagrant box add 
dannycoates/fedora20` work for you? It should be openly available.


John
___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: CloudServices New Development Environment

[John Morrison]

On 10/04/14 10:41, Daniel Coates wrote:

If we're able to skip migrating the database data it should be super easy with 
minimal downtime. Any reason we'd need to save anything?

I don't think there is a reason to save anything. We'll proceed in the 
new IAM with new database tables.


John

- Original Message -
From: Chris Karlof ckar...@mozilla.com
To: dev-fxacct@mozilla.org
Sent: Friday, October 3, 2014 10:34:00 AM
Subject: Fwd: CloudServices New Development Environment

Hi FxA’s,

We need to move all our fxa-dev or other dev infrastructure over to this new 
thing. We should give our partners (Marketplace, FMD, Loop) fair warning before 
we do the switch.

-chris


Begin forwarded message:




From: Chris Kolosiwsky  cko...@mozilla.com 
Subject: CloudServices New Development Environment
Date: October 3, 2014 at 9:27:23 AM PDT
To: cloudservices-...@mozilla.com

All:

We have a new environment (IAM) for your use in developing our awesome stuff. 
It's called the cloudservices-aws-dev environment. We still have some bits to 
move into place, but you should begin recreating instances and moving data as 
you need to from the Old moz-svc-dev environment.

The console login is located at the following URL:

http://cloudservices-aws-dev.signin.aws.amazon.com/

CloudOps is encouraging, but not requiring, you to make use of Amazon's Virtual 
MFA's for your access to the account. Apps are available in the Google Play and 
ITunes store.

If you have not received your login/password/access keys for this environment, 
please let me know.

Finally, as a reminder, please remember the *OLD* environment is scheduled for 
decommissioning at the END OF THIS MONTH.

Thanks!

Chris


_-=^=-_

Chris Kolosiwsky




___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct
___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct


___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: nightly fxa server seems to be broken

[John Morrison]

ansible job stopped in the middle. Trying running it again.

John

On 08/08/14 14:52, Chris Karlof wrote:

Not rendering and we’re getting some 404s

https://nightly.dev.lcip.org/

-chris



___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct


___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: How do we intend to integrate the oauth-server and 123done into the FxA stage environment?

[John Morrison]

(Resending, since autocomplete picked some other Ben... on my previous 
attempt)


I know there has been been work on an rpm build script, a cloudformation 
config, and puppet-config rules, but haven't tried them myself.


@mostlygeek or @ckolos would be able to comment more.

https://github.com/mozilla-services/svcops/blob/master/services/firefox-accounts/fxa-oauth-server/mock-create.sh
https://github.com/mozilla-services/svcops/blob/master/cloudformations/firefox-accounts/fxa-oauth-server.json
https://github.com/mozilla-services/puppet-config/tree/master/fxa/modules/fxa_oauth

On 06/03/14 19:06, Sean McArthur wrote:
I don't know much about our stage environment. I don't know how 
involved deploying to stage is, or who does it. Without a better 
understanding, I probably couldn't offer the best option. Thanks for 
bring this up, however.



On Tue, Jun 3, 2014 at 4:51 PM, Karl Thiessen kthies...@mozilla.com 
mailto:kthies...@mozilla.com wrote:



After a conversation with ckarlof, I thought I'd ask if anyone has
already thought about this before I start to formulate a plan:

I think we're agreed that having an oauth server and a 123done
instance that talk to the staging env would be a good idea.  My
question is, should we deploy them as an extension of what jrgm is
already doing on stage, or perhaps use Danny's whizzy new
stack-builder (which Vlad is happily hacking to accommodate the
two new servers)?  There may be other alternatives I haven't
thought of, but those two seem to me to be the most likely candidates.

Do we have proposed names? oauth.stage.mozaws.net
http://oauth.stage.mozaws.net and 123done.stage.mozaws.net
http://123done.stage.mozaws.net seem reasonable to me.

Is this all already in the planning stages, so I'm fretting for
naught?

Thanks for any context,
--KT.




___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct

Re: train 13

[John Morrison]

Sounds good to me.

John

On 05/12/14 16:45, Chris Karlof wrote:

Hi John and Edwin,

With this little process experiment for strings, we're extracting today and are 
going to give translators two weeks. This means that we'll cut train 13 on May 
19, but hold it's release until May 26.

Sound good?

-chris



___
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct