1036736 - Deploy Release 0.3.1 to msisdn-gateway Production

Status: VERIFIED FIXED

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

Description

[James Bonacci [:jbonacci]]

Getting this opened and ready...

Comment 1

[Rémy Hubscher (:natim)]

Configuration changes are about the smsGateways.

Should be something close to:

  "smsGateways": {
    "nexmo": {
	  "endpoint": "http://127.0.0.1:8080/send",
	  "apiKey": "123",
	  "apiSecret": "456",
      "priority": 2
    }
  },

Comment 2

[James Bonacci [:jbonacci]]

This can't be 0.4.0 if Stage is 0.3.1. We need to test the same release that is pushed to Production.
Are we planning to roll Stage forward after its unblocked?

Comment 3

[James Bonacci [:jbonacci]]

Ah, already answered here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1037604#c1
https://bugzilla.mozilla.org/show_bug.cgi?id=1037604#c2

Comment 4

[James Bonacci [:jbonacci]]

Going back to 0.3.1 (as is) so that client teams have something to talk to...

Comment 5

[James Bonacci [:jbonacci]]

I will wait for the URL change to get made: bug 1033407
before I mark this as Verified.

Comment 6

[James Bonacci [:jbonacci]]

natim: should 'make test', 'make bench', and/or 'make megabench' work against Production?
Right now 'make test' does, but I am not really sure what we are hitting (omxen vs. nexmo) in reality.
thoughts?

Comment 7

[Rémy Hubscher (:natim)]

No they shouldn't works because the loadtests is using omxen as a fake device to receive SMS in production we are using directly Nexmo.

I can update this project: https://github.com/natim/msisdn-verifier-client
To let you try manually with your mobile phone.

Comment 8

[James Bonacci [:jbonacci]]

OK, marking as Verified. The code change is on b2g-inbound:
https://bugzilla.mozilla.org/show_bug.cgi?id=1033407#c18

Comment 9

[James Bonacci [:jbonacci]]

:natim - yea this would be helpful
"I can update this project: https://github.com/natim/msisdn-verifier-client
To let you try manually with your mobile phone."

Comment 10

[Rémy Hubscher (:natim)]

Ok well I made a PR to the ferjm main project but I also deployed it for the dev.
Can you try it and tell me if it works for you?

https://msisdn-dev.stage.mozaws.net/app/

For production it doesn't works yet for a CORS configuration issue.
Alexis and I released a patch in master. Shall we release 0.3.2 or can we go forward with stagging and tag 0.4.2 first?

Comment 11

[Benson Wong [:mostlygeek]]

We should have a 0.3.2 version of the application. So we can deploy the change w/out doing any puppet automation work.

Comment 12

[James Bonacci [:jbonacci]]

yea, 0.3.2 is fine.
We have this: Stage Deploy 0.4.1: https://bugzilla.mozilla.org/show_bug.cgi?id=1038772
We need bugs for these: 
Prod Deploy 0.3.2 
Prod Deploy 0.4.1
I will open these in a few minutes

Comment 13

[James Bonacci [:jbonacci]]

More correctly, I will open one bug when we know the actual release.
I am not sure we want to keep parallel releases going.
It's too much work for QA and for OPs.

So, please pick what is important to go out next:
0.3.2 
OR
0.4.1
OR
0.4.2

Thanks.

:natim
:alexis
:tarek

Comment 14

[Rémy Hubscher (:natim)]

:mostlygeek are your ready with 0.4.1 already?

Comment 15

[Benson Wong [:mostlygeek]]

I don't have 0.4.1 ready. I would like to get 0.3.2 out the door first, close out all of these deploy bugs and then we can start work on a QA / release branch for the 0.4.x branch.

Comment 16

[James Bonacci [:jbonacci]]

We only have two bugs open now:
Prod 0.3.2: https://bugzilla.mozilla.org/show_bug.cgi?id=1040885
Stage 0.4.1: https://bugzilla.mozilla.org/show_bug.cgi?id=1038772

That's it. No more confusion. ;-)