1082174 - Please deploy Loop-Client 0.8.0 code to stage

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Mark Banner (:standard8)]

We'd like to deploy the loop-client 0.8.0 release to stage.

https://github.com/mozilla/loop-client/releases/tag/0.8.0

We'd like to get it deployed to production tomorrow, Tuesday 13 Oct, as there's some information meant to be going out about the changes in this version.

No configuration changes required.

Comment 1

[James Bonacci [:jbonacci]]

That may not be possible. QA needs *at least* 1 day for testing client in Stage before it goes to Production. Is this version a blocker for some bigger release or testing?

If :dwilson can deploy to Stage during EU time, QA can probably pick this up and test on Tuesday PDT.
This could then go to Production during EU time Wednesday (early morning PDT).


In the future, please give Services QA more time for these releases.

Comment 2

[Mark Banner (:standard8)]

(In reply to James Bonacci [:jbonacci] from comment #1)
> That may not be possible. QA needs *at least* 1 day for testing client in
> Stage before it goes to Production.

Sorry, unfortunately the required patches weren't completed until late yesterday.

> Is this version a blocker for some bigger release or testing?

We were asked for it to be deployed on or before today. I've let the relevant folks know.

Comment 3

[Dean Wilson (:deanw)]

This has been deployed to staging.

Comment 4

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

------------------
QUICK CHECKS
------------------

Dean, Bob -
there are currently 3 staging environments for loop-client of which the last one listed is the only one we need:

loop-client (0.7.0)
loop-client-2014-10-10-16-03 (0.7.0)
loop-client-2014-10-14-10-40 (0.8.0-1) ***

It looks like this may be causing some undesired routing as:
https://call.stage.mozaws.net/VERSION.txt (and, btw, https://call.stage-old.mozaws.net/VERSION.txt)
point to the older instances:

0.7.0
22d17d885245f6626e460b5e67a243e2db042401 Thu, 2 Oct 2014 20:20:50 +0100

Would you be willing to look into this? Seems like the first two just need to be blown away and the 0.8.0 one renamed, but you know you know more than me :)


FYI: https://loop.stage.mozaws.net seems to pointing where we want it to:

{"name":"mozilla-loop-server","description":"The Mozilla Loop (WebRTC App) server","version":"0.12.4","homepage":"https://github.com/mozilla-services/loop-server/","endpoint":"https://loop.stage.mozaws.net","fakeTokBox":false,"fxaOAuth":true,"i18n":{"defaultLang":"en-US","lang":"en-US"}}

Comment 5

[Dean Wilson (:deanw)]

We've removed the old stacks but we've not repointed DNS due to iam migration work. We'll have to come back to the DNS side.

Comment 6

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

------------------
RELEASE NOTES
------------------

https://github.com/mozilla/loop-client/releases

TAG
https://github.com/mozilla/loop-client/commit/33b70343eb0b98475d42f9a1496d0214f90c9814

CONFIG CHANGES: 

https://github.com/mozilla-services/puppet-config/commit/31584d16a10a1c26e306865712d0afd7dc509b24
changing webAppUrl to suit Bug 1082566
note in bug: "This config change has been made in puppet. It will be deployed to prod with the 0.12.4 release."


------------------
STAGE VERIFICATION
------------------

STAGE STACK:
loop-client-svcops 0.8.0-1 x86_64 11847783
puppet-config-loop 20141009174905-1 x86_64 15667

/data/loop-client/content/VERSION.txt:
0.8.0
33b70343eb0b98475d42f9a1496d0214f90c9814 Mon, 13 Oct 2014 22:39:23 +0100

PROCESSES RUNNING:
stackdriver, nginx, python, circus, heka  

FILES ON STAGE:
/opt
aws  ec2  openresty  rh  stackdriver

/data:
hekad  loop-client

/etc:
heka.d

/etc/puppet/yaml/app:
loop_client.dev.yaml  
loop_client.prod.yaml 
loop_client.stage.yaml  
loop_client.yaml  
loop_server.dev.yaml  
loop_server.prod.yaml  
loop_server.stage.yaml  
loop_server.yaml

LOGS:
/var/log/circus.log
/var/log/hekad
/media/ephemeral0/nginx/logs 

HEKA:
/data/hekad
/etc/heka.d

Comment 7

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

------------------
QUICK CHECKS (ROUND #2)
------------------

bobm fixed DNS, so there is now 1 staging environment for loop-client:
loop-client-2014-10-14-10-40

Thanks, Bob!

https://call.stage.mozaws.net/VERSION.txt:
0.8.0
33b70343eb0b98475d42f9a1496d0214f90c9814 Mon, 13 Oct 2014 22:39:23 +0100


https://call.stage.mozaws.net/config.js:
var loop = loop || {};

loop.config = {
  serverUrl: 'https://loop.stage.mozaws.net',
  feedbackApiUrl: 'https://input.allizom.org/api/v1/feedback',
  feedbackProductName: 'Loop'
};


/data/loop-cient/content/config.js:
loop.config = {
  serverUrl: 'https://loop.stage.mozaws.net',
  feedbackApiUrl: 'https://input.allizom.org/api/v1/feedback',
  feedbackProductName: 'Loop'
};



https://call.stage.mozaws.net/:
Welcome to the Firefox Hello web client.


$ curl -I https://call.stage.mozaws.net:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-length: 2499
Content-Type: text/html
Date: Tue, 14 Oct 2014 22:01:47 GMT
ETag: "543cedef-9c3"
Last-Modified: Tue, 14 Oct 2014 09:33:35 GMT
Vary: Accept-Encoding
Connection: keep-alive


https://loop.stage.mozaws.net/:
{"name":"mozilla-loop-server","description":"The Mozilla Loop (WebRTC App) server","version":"0.12.4","homepage":"https://github.com/mozilla-services/loop-server/","endpoint":"https://loop.stage.mozaws.net","fakeTokBox":false,"fxaOAuth":true,"i18n":{"defaultLang":"en-US","lang":"en-US"}}

PUPPET FILES:
/etc/puppet/yaml/app/loop_client.stage.yaml
classes_hash:
    yum::repos::mozilla_services_aws_stage: true

loop_client::app_server_url: "https://loop.stage.mozaws.net"
loop_client::feedback_api_url: "https://input.allizom.org/api/v1/feedback"


/etc/puppet/yaml/app/loop_client.yaml
classes_hash:
    loop_client: true
    stackdriver: true

stackdriver::nginx::nginx_status_url: http://127.0.0.1:7999/nginx_status

loop_client::app_server_url: "SET_ME"


https://call.stage.mozaws.net/legal/terms/ - VERIFIED

------------------
TEST CALLS
------------------

Successfully placed 10 or so calls back and forth between Nightly and Aurora without issue.
New UI changes and user flow look great.

A few minor issues noted / bugs filed:

[1] Bug 1082954 - Loop calls started from a "used" Start page terminate ~7 seconds into call
    (i.e. re-cycling a start page results in a failed call)

[2] Bug 1082956 - Exit button on feedback page doesn't work

Comment 8

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

Per email w/ ahughes, [1] is a dupe of: Bug 1074517 - Second call with URL gets disconnected
Since [2] is new (not a regresssion), we can go ahead and push to prod.

Comment 9

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

Per deanw - we'll be moving to new dev IAM by tomorrow
QA to re-verify before pushing to prod

Comment 10

[James Bonacci [:jbonacci]]

ah, no.

Get 0.8.0 out to Production FIRST.
Then mess with new Dev IAM.

Sorry. Over-ruled by QA.

Comment 11

[Bob Micheletto [:bobm]]

As 0.8.0 is out, I shall defer on the rest of this deployment to my esteemed colleague.

Comment 12

[James Bonacci [:jbonacci]]

Yea, that's ok.
See new bug 1083529