Services/Mobile-ID

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>

Deployment

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	XXXX
France	Nexmo	208 - 308 - 340 - 543 - 546 - 547 - 647 - 742	XXXX
Spain	Nexmo	214	XXXX
Others	Nexmo		XXX

This environment can be used to test end-to-end scenario until the service hits the Stable channel.

Load-Stage

• Host: https://msisdn-loadtest.stage.mozaws.net/
• Maintainer: OPS
• SMS Gateway: OMXEN
• Usage: Server-side 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.

This server will be a perfect mirror of the production environment, updated with the tag of the upcoming release

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	XXXX
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

The Tuesday release will be announced to the loop mailing list when the tagging is happening, so everyone has a chance to try it out.

Theorical dates for July/August:

• July 8th - tagging
• July 14th - prod push
• July 22th - tagging
• July 28th - prod push
• August 5th - tagging
• August 11th - prod push
• August 19th - tagging
• August 25th - prod push
• and so forth...

Once the service will hit the Stable channel, we will introduce the new real-stage environment

Branches and bugfix deployments

In case of a bugfix:

• A commit will with the fix will be pushed to master.
• A new branch will be created on the github repository with the versions that needs the patch, and the fixes will be applied there (backported).
• A new tag will be created with the new version (the patch version will be updated) and a deployment request will be filled.

For instance, in case the 0.9.0 release contains a bug that needs to be fixed:

1. Fix the code in master;
2. Backport (cherrypick) the commit in the 0.9.x branch (create it if needed);
3. Tag a new minor release: 0.9.1 and fill a new deployment request.