Confirmed users
1,018
edits
CloudServices/SimplePushServer: Difference between revisions
CloudServices/SimplePushServer (view source)
Revision as of 20:59, 22 October 2014
, 22 October 2014→Loop
(Major customer schema) |
(→Loop) |
||
| Line 116: | Line 116: | ||
== Deployments== | == Deployments== | ||
=== Loop === | === Loop === | ||
Hello (aka Loop) is a WebRTC based video chat program that is available to desktop and mobile devices. It uses a specialized version of SimplePush that does not have back end storage, since there is no need to alert connections that are offline. | |||
==== Configuration ==== | ==== Configuration ==== | ||
All systems are deployed to AWS and are set to autoscale within clusters. Clusters are not yet configured to scale, however ops is working to address this. | |||
There are two non-production networks of systems: | |||
<dl> | |||
<dt>Stable</dt><dd>This is a non production environment which hosts a stable development version of Simplepush for development and integration tests. This version may be auto-updated from the "dev" branch of https://github.com/mozilla-services/pushgo. </dd> | |||
<dt>QA</dt><dd>This is a non production environment that hosts the stable, pre-release version of SimplePush for load and QA testing. This version updates from explicit releases generated by https://github.com/mozilla-services/pushgo.</dd> | |||
</dl> | |||
It should be noted that effort is currently being made to ensure that the push service used by Hello is not significantly different (API wise) from the standard Push service. | |||
==== Deployment Architectures ==== | ==== Deployment Architectures ==== | ||
The <b>stable</b> environment is currently configured for push-loop-dev.stage.mozaws.net (for long lived socket connections) and updates-push-loop-dev.stage.mozaws.net (to receive the REST version PUTs) | |||
While the client has the ability to retry a connection if a given machine is not responsive, it has been requested by Ops that Push Protocol Redirects be re-enabled and that a separate suite of machines be created to do connection load balancing. (so clients would first connect to the central server, and then be redirected to a machine with available resources.) | |||
==== Monitoring And Metrics ==== | ==== Monitoring And Metrics ==== | ||
Push currently provides metrics using logstash compatible reporting mechanisms (e.g. stackdriver). In addition, logs are scraped and information displayed via kibana. | |||
Currently monitoring and metrics are being collected and displayed on to different systems. Effort will be made to simplify this. | |||
TODO: Dev & Ops need to identify a list of key health metrics to monitor for this system. | |||
==== Points of Contact ==== | ==== Points of Contact ==== | ||
In the event of significant events, operations notifies members of development teams that actions are required. | |||
TODO: dev will provide contact information as well as a "jiggle list" of actions which may alleviate issues. | |||
=== Find My Device === | === Find My Device === | ||
==== Configuration ==== | ==== Configuration ==== | ||