1101480 - Update loop-stage configuration to use Loop Push staging environment

Status: VERIFIED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Alexis Metaireau (:alexis)]

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

I believe wss://push.stage.mozaws.net/ is the correct address but I need ben to confirm.

Comment 1

[Ben Bangert [:benbangert]]

That is simplepush stage, Loop-Push stage is wss://push-loop1.stage.mozaws.net/

Comment 2

[Jeremy Orem [:oremj]]

We just renamed this to wss://loop-push1.stage.mozaws.net/

wss://loop-push2.stage.mozaws.net/ is also available.

Comment 3

[Ben Bangert [:benbangert]]

:alexis, has this change been done? We'd like QA to be able to start testing Loop using a complete staging so we can promote usage of Loop-Push Production ASAP.

Comment 4

[Ben Bangert [:benbangert]]

Remy has noted that changing this config value is an operations task as the URL is in loop-server config data that ops can change.

:oremj Can you make this change to loop-server staging?

Comment 5

[Jeremy Orem [:oremj]]

Added in https://github.com/mozilla-services/puppet-config/pull/1008

bobm is going to push the config.

Comment 6

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

The change has taken place:

$ time for i in {1..100}; do curl -s https://loop.stage.mozaws.net/push-server-config; echo ""; done | sort | uniq -c
  55 {"pushServerURI":"wss://loop-push1.stage.mozaws.net/"}
  45 {"pushServerURI":"wss://loop-push2.stage.mozaws.net/"}

real    1m9.744s
user    0m1.006s
sys     0m0.378s

Comment 7

[Ben Bangert [:benbangert]]

Great, do we need another ticket to change production to loop-push production when QA signs off?

Comment 8

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

(In reply to Ben Bangert [:benbangert] from comment #7)
> Great, do we need another ticket to change production to loop-push
> production when QA signs off?

:kthiessen will create another ticket for loop-push prod deployment tomorrow once he's marked stage verified.

Comment 9

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

This is just a config change, but adding notes for good measure:

------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/pushgo/releases

TAG
https://github.com/mozilla-services/pushgo/releases/tag/1.4.1

CONFIG/OPS CHANGES
loop-server/stage: pushServerURIS -> stage loop push 
https://github.com/mozilla-services/puppet-config/commit/394c34be51be335e4fab9206c40c8c54edd0400f

Comment 10

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

------------------
SUMMARY
------------------
placed ~10 successful calls back and forth between Nightly and Aurora. tested mute/unmute functions. All good.

NOTE:
using the following config:
loop.server: https://loop.stage.mozaws.net
services.push.serverURL: wss://loop-push1.stage.mozaws.net/

Tag-teaming w/ :kthiessen...
Leaving ticket for Karl to mark verified tomorrow so we can complete verification of:
Bug 1075654 - need to confirm loop client will reconnect to websocket upon server side termination
at switchover from stage to prod

------------------
STAGE VALIDATION
------------------
STAGE STACK
$ rpm -qa | grep pushgo
pushgo-svcops 20141124185038-9889e80 x86_64 10865341

VERSION
https://github.com/mozilla-services/pushgo/commit/9889e80
same as:
https://github.com/mozilla-services/pushgo/releases/tag/1.4.1

NOTE:
https://updates-push.stage.mozaws.net/realstatus/:
{"ok":true,"clientCount":0,"maxClients":180000,"maxEndpointConns":20000,"store":{"ok":true},"pinger":{"ok":true},"locator":{"ok":true},"goroutines":522,"version":""}
* version not rendering is known issue per :oremj

QUICK CHECKS
:kthiessen already checked push-server-config and load-balancing on stage:
see: Comment 6
see: https://mana.mozilla.org/wiki/display/SVCOPS/SimplePush#SimplePush-Deployments

Comment 11

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

I was expecting Bob to come in and mark this change RESOLVED/FIXED, but I will go ahead and move it to VERIFIED/FIXED in two steps.

Comment 12

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

Expect a ticket to move this to production in an hour or two.