Please deploy autopush 1.0 to PRODUCTION

VERIFIED FIXED

Status

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

People

(Reporter: rpapa, Assigned: oremj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/autopush/releases

TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.0rc1
https://github.com/mozilla-services/autopush/commit/1e5a1bc1a6d7efbad0c4ea9fea071681d8d8438a

CHANGELOG

1.0rc1 (Apr 29, 2015)
=====================

Features
--------

* Verify ability to read/write DynamoDB tables on startup. Resolves Issue #46.
* Send un-acknolwedged direct delivery messages to the router if the client is
  disconnected without ack'ing them. Resolves Issue #36.
* Use IProducer to more precisely monitor when the client has drained the data
  to immediately resume sending more data. Resolves Issue #28.
* Add /status HTTP endpoint for autopush/autoendpoint. Resolves Issue #27.
* Add example stage/prod config files. Resolves Issue #22.
* Switch internal routing from requests to twisted http-client. Resolves Issue
  #21.
* Add logging for user-agent to metrics tags. Resolves Issue #20.
* Add Datadog stats output. Resolves Issue #17.
* Add GCM and APNS Bridges. Resolves Issue #16.
* Use eliot structured logging for stdout logging that matches ops standard
  for logging. Resolves Issue #11.
* Allow storage/router table names to be configurable. Resolves Issue #4.
* Added optional CORS headers (use --cors to enable). Resolves Issue #3.
* Add provisioned error metrics to track when throughput is exceeded in AWS
  DynamoDB. Resolves Issue #2.
* Add Sentry support (SENTRY_DSN must be set in the environment). Resolves
  Issue #1.

Bug Fixes
---------

* Capture and log exceptions in websocket protocol functions.
* Fix bug with 'settings' in cyclone overriding cyclone's settings. Resolves
  Issue #13.
Hey Jeremy, OK if we deploy this next Mon., 5/11 @11am PST?
Depends on: 1157811
Flags: needinfo?(oremj)
(Assignee)

Updated

3 years ago
Assignee: nobody → oremj
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(oremj)
Resolution: --- → FIXED
With this deployment we're moving from SimplePush (1.5.0) to autopush (1.0).

------------------
SUMMARY (PRODUCTION PRE-DEPLOY)
------------------

Able to locate and ring Flame device using findmydevice on B2G 2.2 with default settings.
Pre-deploy verification (SimplePush) PRODUCTION - OK!

https://updates.push.services.mozilla.com/status/
{
  "status": "OK",
  "clients": 624,
  "version": "1.5.0"
}

https://updates.push.services.mozilla.com/realstatus/ - OK

------------------
SUMMARY 
------------------

Able to locate, ring and lock Flame device using findmydevice on B2G 2.2 with default settings.

Verifying PRODUCTION.

------------------
TEST NOTES
------------------

geolocation in and out for the first few hours.  Some of this may have be due to reconnection traffic, but equally as likely due to one of other factors:
* low battery power on device
  - JR pointed out that this can cause geo to shut off to conserve power (even if plugged in)
* poor AP bandwidth 
  - once I switched phone over to SIM card w/ data and walked out of the building, it began to easily connect
  - also, when I moved the device to a place in the office with strong AP signal, geo became responsive again

Will need to take this into consideration in future when using FMD on device for verification.

https://updates.push.services.mozilla.com/status/
{
  "status": "OK",
  "version": "1.0rc1"
}

PRE-DNS-SWITCH TESTING 

Currently we're unable to do a pre-DNS switch test on elb 
Ideally we need something like secondary update servers for testing on prod:
perhaps an:  https://updates.push-test.services.mozilla.com?
Status: RESOLVED → VERIFIED
Hey Jeremy, realstatus was working prior to deployment, but throwing 404 now.  Can you check and see if perhaps it's not mapped properly?
https://updates.push.services.mozilla.com/realstatus
Thanks!
Flags: needinfo?(oremj)
(Assignee)

Comment 4

3 years ago
That was something that was built in to pushgo, but not autopush. If you need it back, an app bug will need to be filed.
Flags: needinfo?(oremj)
You need to log in before you can comment on or make changes to this bug.