1104994 - Update loop-prod configuration to use Loop Push production environment

Status: VERIFIED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Karl Thiessen [:kthiessen, he/him]]

+++ This bug was initially created as a clone of Bug #1101480 +++

The configuration needs to be updated with the right uri.

See https://github.com/mozilla-services/loop-server/blob/master/loop/config.js#L332-L336

Per https://mana.mozilla.org/wiki/display/SVCOPS/SimplePush#SimplePush-Deployments, I believe the proper endpoints are:
  wss://push1.push.hello.firefox.com
  wss://push2.push.hello.firefox.com

But I will want folks from Dev and Ops to check my choices there.

Comment 1

[Karl Thiessen [:kthiessen, he/him]]

It also makes sense to make sure that the loop-push production environment is on 1.4.1 -- git sha 9889e80.

Loop-Server should be on 0.13.2, I believe.  Again, anyone who knows differently should chime in here.

Comment 2

[Māris Fogels [:mars] (please needinfo)]

(In reply to Karl Thiessen [:kthiessen] from comment #0) 
> Per
> https://mana.mozilla.org/wiki/display/SVCOPS/SimplePush#SimplePush-
> Deployments, I believe the proper endpoints are:
>   wss://push1.push.hello.firefox.com
>   wss://push2.push.hello.firefox.com
> 
> But I will want folks from Dev and Ops to check my choices there.

needinfoing :benbangert to check the push endpoint URLs.

Comment 3

[Ben Bangert [:benbangert]]

There is no push2 from what I can see, there is push1 which is working properly.

Comment 4

[Richard Pappalardo [:rpapa][:rpappalardo]]

(In reply to Māris Fogels [:mars] from comment #2)
> (In reply to Karl Thiessen [:kthiessen] from comment #0) 
> > Per
> > https://mana.mozilla.org/wiki/display/SVCOPS/SimplePush#SimplePush-
> > Deployments, I believe the proper endpoints are:
> >   wss://push1.push.hello.firefox.com
> >   wss://push2.push.hello.firefox.com
> > 
> > But I will want folks from Dev and Ops to check my choices there.

> 
> needinfoing :benbangert to check the push endpoint URLs.

These endpoints have been verified on stage, but haven't yet been deployed to prod (that's why you only see push1 on prod at the moment).  bobm said he'd be able to do so tomorrow.  Once that's been done, Karl will verify.

Comment 5

[Māris Fogels [:mars] (please needinfo)]

bobm, are we able to finish this before PST noon today?  I'd like to have the afternoon for QA, Dev, and Ops to watch the system in production and make sure there are no issues.

Also, please ping kthiessen and mars in #push when the switch-over is done.  QA needs to know so that they can run their smoke tests against prod.

Thanks!

Comment 6

[Bob Micheletto [:bobm]]

Per the loop operations call: we're going forward with a deployment today.  I will inform #push when that is completed.

Comment 7

[Bob Micheletto [:bobm]]

New stack built.  QA testing presently.

Comment 8

[Bob Micheletto [:bobm]]

Configuration update complete.

Comment 9

[Karl Thiessen [:kthiessen, he/him]]

time for i in {1..100}; do curl -s https://loop.services.mozilla.com/push-server-config; echo ""; done | sort | uniq -c
 100 {"pushServerURI":"wss://push1.push.hello.firefox.com"}

real    0m13.718s
user    0m0.753s
sys     0m0.290s

Comment 10

[Karl Thiessen [:kthiessen, he/him]]

Calls from and to Aurora and Nightly work normally (with the new Rooms feature, even!).

JR Conlin found an issue with loop-client where right-click copy doesn't work as expected in Windows; I have no such issue on the Mac.  I've asked him to file a separate bug for it.

With calls working properly and the push-endpoint configured correctly, I'm calling this verified.

Thanks to everyone who helped out with this.

Comment 11

[Karl Thiessen [:kthiessen, he/him]]

Note on comment 9:  We decided to go with only one push endpoint -- push2 currently exists in stage but not in prod.  So the output in comment 9 is what's expected, as opposed to what is specified in comment 0.