Deploy Release 0.3.1 to msisdn-gateway Production

VERIFIED FIXED

Status

Cloud Services
Operations: Deployment Requests
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: jbonacci, Assigned: mostlygeek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

4 years ago
Getting this opened and ready...
(Reporter)

Updated

4 years ago
Depends on: 1035960
Whiteboard: [qa+]
(Assignee)

Updated

4 years ago
Assignee: nobody → bwong

Updated

4 years ago
Blocks: 1033407
No longer blocks: 1033407
Summary: Deploy Release 0.3.1 to msisdn-gateway Production → Deploy Release 0.4.0 to msisdn-gateway Production
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
    }
  },
Blocks: 1033407
(Reporter)

Comment 2

4 years ago
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?
(Reporter)

Updated

4 years ago
Depends on: 1038772
No longer depends on: 1035960
(Reporter)

Updated

4 years ago
Summary: Deploy Release 0.4.0 to msisdn-gateway Production → Deploy Release 0.4.1 to msisdn-gateway Production
(Reporter)

Comment 4

4 years ago
Going back to 0.3.1 (as is) so that client teams have something to talk to...
Status: NEW → ASSIGNED
Summary: Deploy Release 0.4.1 to msisdn-gateway Production → Deploy Release 0.3.1 to msisdn-gateway Production
(Assignee)

Updated

4 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Comment 5

4 years ago
I will wait for the URL change to get made: bug 1033407
before I mark this as Verified.
No longer depends on: 1038772
(Reporter)

Comment 6

4 years ago
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?
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.
(Reporter)

Comment 8

4 years ago
OK, marking as Verified. The code change is on b2g-inbound:
https://bugzilla.mozilla.org/show_bug.cgi?id=1033407#c18
Status: RESOLVED → VERIFIED
(Reporter)

Comment 9

4 years ago
: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."
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?
(Assignee)

Comment 11

4 years ago
We should have a 0.3.2 version of the application. So we can deploy the change w/out doing any puppet automation work.
(Reporter)

Comment 12

4 years ago
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
(Reporter)

Comment 13

4 years ago
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
:mostlygeek are your ready with 0.4.1 already?
(Assignee)

Comment 15

4 years ago
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.
(Reporter)

Comment 16

4 years ago
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. ;-)
You need to log in before you can comment on or make changes to this bug.