Services/Mobile-ID: Difference between revisions
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
=Deployement= | =Deployement= | ||
There are three environments. | There are three deployed environments. A fourth will be deployed later. | ||
| Line 60: | Line 60: | ||
|} | |} | ||
==Stage== | This environment can be used to test end-to-end scenario until the service hits the Stable channel. | ||
==Load-Stage== | |||
* <b>Host:</b> https://msisdn.stage.mozaws.net/ | * <b>Host:</b> https://msisdn.stage.mozaws.net/ | ||
| Line 73: | Line 75: | ||
Load tests can interact with OMXEN to check what SMSs are sent out of the system. | Load tests can interact with OMXEN to check what SMSs are sent out of the system. | ||
==Real-Stage== | |||
* <b>Host:</b> To be defined | |||
* <b>Maintainer:</b> OPS | |||
* <b>SMS Gateway:</b> Nexmo | |||
* <b>Usage:</b> Client-side QA | |||
Not yet commissioned. This environment will be used for end-to-end testing of the service once it hits the stable channel. | |||
==Production== | ==Production== | ||
| Line 103: | Line 115: | ||
The service is continuously pushed into the '''dev''' server where client developers can test it. | The service is continuously pushed into the '''dev''' server where client developers can test it. | ||
The service is released in '''stage''' then '''production''' every other week (or asap if we discover a security breach) | The service is released in '''load-stage''' then '''production''' every other week (or asap if we discover a security breach) | ||
* Tuesday - end of previous cycle. tagging. pushed to '''stage''' | * Tuesday - end of previous cycle. tagging. pushed to '''load-stage''' | ||
* Tuesday through Friday - load testing by James on '''stage''' | * Tuesday through Friday - load testing by James on '''load-stage''' | ||
* Monday - push to '''production''' if no regression, if any regression backed off | * Monday - push to '''production''' if no regression, if any regression backed off | ||
''Once the service will hit | ''Once the service will hit the Stable channel, we will introduce the new real-stage environment'' | ||
Revision as of 13:13, 10 July 2014
The Mobile-ID service provides a global mobile number validation system that can be used to authenticate a user's device. It interacts with SMS gateways to send and receive SMSs.
See : https://wiki.mozilla.org/Loop/Architecture#MSISDN_.28Phone_Number.29_Verification
Contacts
- Dev Team
- Tarek Ziadé <tarek@mozilla.com>
- Alexis Metaireau <alexis@mozilla.com>
- Rémy Hubscher <natim@mozilla.com>
- OPS
- Benson Wong <mostlygeek@mozilla.com>
- Wesley Dawson <whd@mozilla.com>
- QA
- James Bonacci <jbonacci@mozilla.com>
Deployement
There are three deployed environments. A fourth will be deployed later.
Dev
- Host: https://msisdn-dev.stage.mozaws.net/
- Maintainer: DEVs
- SMS Gateway: Nexmo
- Usage: Development and integration
This environment is updated with the master branch by devs on a regular basis - or upon request. you can get the version by displaying the root URL of the server.
This environment provides a Mobile number validation for the following countries:
| Client Country | Provider | MCC | Server Number |
|---|---|---|---|
| USA | Nexmo | 302 - 310 - 311 - 312 - 313 - 314 - 315 - 316 - 332 - 544 | 117142940188 |
| France | Nexmo | 208 - 308 - 340 - 543 - 546 - 547 - 647 - 742 | 33644630007 |
| Spain | Nexmo | 214 | 34911067077 |
| Others | Nexmo | 447937946655 |
This environment can be used to test end-to-end scenario until the service hits the Stable channel.
Load-Stage
- Host: https://msisdn.stage.mozaws.net/
- Maintainer: OPS
- SMS Gateway: OMXEN
- Usage: QA and Loadtesting
This environment is used by QA and dev for load tests. The goal is to measure how many connections can be handled by the server and anticipate errors that might happen on high load.
SMS are not sent for real, they are collected by a fake SMS Gateway: OMXEN. We deployed it at http://omxen.dev.mozaws.net/
Load tests can interact with OMXEN to check what SMSs are sent out of the system.
Real-Stage
- Host: To be defined
- Maintainer: OPS
- SMS Gateway: Nexmo
- Usage: Client-side QA
Not yet commissioned. This environment will be used for end-to-end testing of the service once it hits the stable channel.
Production
- Host: https://msisdn.services.mozilla.com/
- Maintainer: OPS
- SMS Gateway: Nexmo
- Usage: Production apps
This environment is used for production and is the default server for Nightly.
The prod environment provide a Mobile number validation for the following countries:
| Client Country | Provider | MCC | Server Number |
|---|---|---|---|
| USA | Nexmo | 302 - 310 - 311 - 312 - 313 - 314 - 315 - 316 - 332 - 544 | 12182967993 |
| More to come |
Release Cycle
The service is continuously pushed into the dev server where client developers can test it.
The service is released in load-stage then production every other week (or asap if we discover a security breach)
- Tuesday - end of previous cycle. tagging. pushed to load-stage
- Tuesday through Friday - load testing by James on load-stage
- Monday - push to production if no regression, if any regression backed off
Once the service will hit the Stable channel, we will introduce the new real-stage environment