Closed
Bug 1165985
Opened 9 years ago
Closed 9 years ago
Please deploy release 0.6.0 to msisdn-gateway STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rpapa, Unassigned)
References
Details
This deployment includes a heartbeat fix (see Release notes) and config changes. Also, msisdn.stage and msisdn-isoprod.stage have changed. The new STAGE endpoints are as follows: [A]. msisdn.stage.mozaws.net --> Nexmo (real endpoint) [B]. msisdn-loadtest.stage.mozaws.net --> Omxen (fake endpoint) CONFIG CHANGES: - numerous internal changes from an infrastructure perspective - significant build pipeline changes - datadog agent has been added to the build. - updated the AMI (and so all the base OS packages). - now use the Amazon provided SSL policies. - Version information is exposed at the stack, ASG and instance level. ------------------ RELEASE NOTES ------------------ https://github.com/mozilla-services/msisdn-gateway/releases COMPARISONS https://github.com/mozilla-services/msisdn-gateway/compare/0.4.5...0.5.0 https://github.com/mozilla-services/msisdn-gateway/compare/0.5.0...0.5.1 https://github.com/mozilla-services/msisdn-gateway/compare/0.5.1...0.6.0 TAGS https://github.com/mozilla-services/msisdn-gateway/releases/tag/0.6.0 https://github.com/mozilla-services/msisdn-gateway/commit/ada23f91f65091cfeefaed05257f50d84a79347c CHANGELOG 0.6.0 (2015-05-15) ------------------ - [bug 1164404] - The heartbeat didn't detect the readonly redis cluster.
Reporter | ||
Comment 1•9 years ago
|
||
Hey Dean, Everything looks good on the 0.6.0 stage deploy, but before I go crazy with loadtesting, just want to confirm that for STAGE we're using: /data/msisdn-gateway/config/production.json not: /data/msisdn-gateway/config/test.json (this file is pointing to rest.nexmo on both servers, though it doesn't contain any keys, so I assume it's nothing more than a 'sample' file? I am able to verify it externally using cli and browser tools that calls to each server are hitting correctly: http://omxen.dev.mozaws.net/receive?to=1<DEVICE PHONE> [{"text": "Your verification code is: 150906", "from": "Mozilla"}] as well as from cloudwatch Other than that we can probably deploy first thing tomorrow. ------------------ SUMMARY ------------------ e2e test and quick loadtests - OK 0.6.0 tag unit tests - PASS ------------------ STAGE VALIDATION ------------------ STAGE STACK - PACKAGE VERSION $ sed -n '/version/p' /data/msisdn-gateway/package.json: "version": "0.6.0", https://msisdn.stage.mozaws.net: { "name": "mozilla-msisdn-gateway", "description": "The Mozilla MSISDN Gateway", "version": "0.6.0", "homepage": "https://github.com/mozilla-services/msisdn-gateway/", "endpoint": "https://msisdn.stage.mozaws.net" } https://msisdn-loadtest.stage.mozaws.net: { "name": "mozilla-msisdn-gateway", "description": "The Mozilla MSISDN Gateway", "version": "0.6.0", "homepage": "https://github.com/mozilla-services/msisdn-gateway/", "endpoint": "https://msisdn-loadtest.stage.mozaws.net" } https://msisdn.stage.mozaws.net/__heartbeat__: { "storage": true } https://msisdn-loadtest.stage.mozaws.net/__heartbeat__: { "storage": true } $ curl -I https://msisdn.stage.mozaws.net HTTP/1.1 200 OK Access-Control-Allow-Credentials: true Content-Length: 204 Content-Type: application/json; charset=utf-8 Date: Mon, 18 May 2015 22:13:21 GMT ETag: W/"cc-304f62d" Timestamp: 1431987201 Connection: keep-alive $ curl -I https://msisdn-loadtest.stage.mozaws.net HTTP/1.1 200 OK Access-Control-Allow-Credentials: true Content-Length: 213 Content-Type: application/json; charset=utf-8 Date: Mon, 18 May 2015 22:13:29 GMT ETag: W/"d5-c9ef74d9" Timestamp: 1431987209 Connection: keep-alive ------------------ E2E TEST https://msisdn.stage.mozaws.net ------------------ $ msisdn-cli --host=https://msisdn.services.mozilla.com -c 315 -n +1<DEVICE PHONE NUMBER> Please enter the code that you will get by SMS from +12182967993: 104592 Verified: { "exp": 1432068391680, "iat": 1431981981680, "iss": "msisdn.services.mozilla.com", "lastAuthAt": 1431981991680, "lastVerifiedAt": 1431981991523, "principal": { "email": "92663fd3-66c4-d56d-b496-50b533f7425a@msisdn.services.mozilla.com" }, "pubkey": "<stripped>", "public-key": "<stripped>", "publicKey": "<stripped>", "verifiedMSISDN": "+1<DEVICE PHONE NUMBER>" } ------------------ LOADTEST https://msisdn-loadtest.stage.mozaws.net ------------------ Users [80], Agents 5, Hits 1000 no errors https://loads.services.mozilla.com/run/1de72db2-320e-451b-8518-3ddde5c461e5 Users [80], Agents 5, Hits 1000 no errors https://loads.services.mozilla.com/run/01985903-2f34-4555-8059-801d7d4c0dbc
Flags: needinfo?(dwilson)
Comment 2•9 years ago
|
||
/data/msisdn-gateway/config/production.json is the correct file. The test one must come from the package as it's not something we manage via puppet. We can look at getting it removed to make things a little clearer.
Updated•9 years ago
|
Flags: needinfo?(dwilson)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•9 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•