Closed Bug 1052186 Opened 11 years ago Closed 11 years ago

Deploy Release 0.4.3 to msisdn-gateway Production

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jbonacci, Unassigned)

References

Details

(Whiteboard: [qa+])

No description provided.
Whiteboard: [qa+]
I just released MSISDN-Gateway 0.4.2 — https://github.com/mozilla-services/msisdn-gateway/releases/tag/0.4.2 We will have to do some configuration for production. Here is the mtSenderMapping configuration: mtSenderMapping: { "302": "+12182967993", "310": "+12182967993", "311": "+12182967993", "312": "+12182967993", "313": "+12182967993", "314": "+12182967993", "315": "+12182967993", "316": "+12182967993", "332": "+12182967993", "544": "+12182967993" } Here is the moVerifierMapping: "moVerifierList": { "208": "+33644639987", "308": "+33644639987", "340": "+33644639987", "543": "+33644639987", "546": "+33644639987", "547": "+33644639987", "647": "+33644639987", "742": "+33644639987", "214": "+34911067087", "302": "+12182967993", "310": "+12182967993", "311": "+12182967993", "312": "+12182967993", "313": "+12182967993", "314": "+12182967993", "315": "+12182967993", "316": "+12182967993", "332": "+12182967993", "544": "+12182967993" } We don't want to set up a default moVerifier but we want to let the default mtSender to Mozilla@
Testing is complete in Stage. We are clear to push to Production.
Status: NEW → ASSIGNED
Stack is deployed.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I updated the html5 validation app: https://github.com/natim/msisdn-verifier-client It looks like cors doesn't work with the current setup. Can you verify that allowedOrigins is set to ["*"]
it's not but I can set it to that.
The PR looks good. The cors problem is fixed. Also now we don't hit the nexmo API, I have no logs of my messages on the Nexmo dashboard.
the API secrets for nexmo were wrong. Fixed now. Redeploying with new secrets.
Based on Remy's tests, we can mark this Verified. QA was unable to use the same test to verify an SMS...
Status: RESOLVED → VERIFIED
I have updated the code of the verifier here: http://mozilla-services.github.io/msisdn-verifier-client/ :jbonaci I tried with your american phone number so you should have receive a message.
Well I checked on the dashboard and message to US and Canadian number still don't work. I did a quick fix on the nexmo.sendSMS for US and Canadian number and released 0.4.3
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Summary: Deploy Release 0.4.2 to msisdn-gateway Production → Deploy Release 0.4.3 to msisdn-gateway Production
Ok I did the roundTrip script that you can find here: https://github.com/mozilla-services/msisdn-gateway/tree/master/tools/roundTrip just: make install and then you can start the process. For MOMT flow: python roundTrip.py -H https://msisdn.services.mozilla.com -c 310 For MT flow: python roundTrip.py -H https://msisdn.services.mozilla.com -c 310 -n +16509XXXXXX
Codes for the MOMT flow are quite long, what I recommend you is to send them between your computer and your phone by email so that you can copy/paste them.
:natim No SMS on my phone :-) (Comment 11)
I have updated DEV with 0.4.3 so that you can test before going to production.
OK, cool. :edwong this is for you while I test Stage...
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
I am pretty sure I saw a quick verification from Remy and for Edwin. See IRC for the chat...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.