1033407 - Set MobileID service production URL

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Runtime, defect)

Description

[Fernando Jiménez Moreno [:ferjm]]

We need to change the MSISDN server url once the production url mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1020899#c29 is working.

Comment 1

[Maria Angeles Oteo (:oteo)]

Right now using the development server URL but for sure we need to change it to the Production one for 2.0,  so nominating.

Comment 2

[Jason Smith [:jsmith]]

(In reply to Maria Angeles Oteo (:oteo) from comment #1)
> Right now using the development server URL but for sure we need to change it
> to the Production one for 2.0,  so nominating.

Will discuss in triage, but I'm leaning on the side of this being set with the feature-b2g flag, since this falls under required feature work for Loop.

Comment 3

[bhavana bajaj [:bajaj]]

(In reply to Jason Smith [:jsmith] from comment #2)
> (In reply to Maria Angeles Oteo (:oteo) from comment #1)
> > Right now using the development server URL but for sure we need to change it
> > to the Production one for 2.0,  so nominating.
> 
> Will discuss in triage, but I'm leaning on the side of this being set with
> the feature-b2g flag, since this falls under required feature work for Loop.

Its a semantic issue and not a big change to get into an argument on feature vs blocking, so I am going to block on this issue so we do not ship with this.

Comment 4

[Maire Reavy [:mreavy]]

Maria -- Is this a change your team can make when the production url is ready?  Can someone on your team own this bug?  Thanks.

Comment 5

[Maria Angeles Oteo (:oteo)]

Thank you Fernando!

Comment 6

[:shell escalante]

just checking if this change has been checked in and uplifted?

Comment 7

[Maire Reavy [:mreavy]]

Hi Fernando -- I realize this is a simple change, but our release drivers want to get this in and uplifted ASAP.  Do you think you can do this tomorrow (Tuesday)?   Thanks!

Comment 8

[Fernando Jiménez Moreno [:ferjm]]

AFAIK, the production server isn't ready yet. If I am not wrong, the push date is this Wednesday (15th), so we should not make the change until then.

Comment 9

[Fernando Jiménez Moreno [:ferjm]]

Attachment: v1

Comment 10

[Fernando Jiménez Moreno [:ferjm]]

Tarek, could you let us know when the production server is ready, so we can land this patch, please? Thanks :)

Comment 11

[Rémy Hubscher (:natim)]

The server is deployed but can only validates US number at the moment.
:shell can you tell us what country should be covered by the production MSISDN server?

At the moment the development server covers US/FR/SP and default to UK for international validation (with high cost for the end user.)

Comment 12

[Tarek Ziadé (:tarek)]

(In reply to Fernando Jiménez Moreno [:ferjm] from comment #10)
> Tarek, could you let us know when the production server is ready, so we can
> land this patch, please? Thanks :)

The production deployment is being handled by our ops see bug 1036736 (added in the blockers) right after the current tag has been validated and deployed on stage. This should be ready early this week.

The country numbers validation setup can be handled in parallel of switching to the production server. Worst case scenario will be to have the same set up as the dev server wrt phone #s.

Comment 13

[Tarek Ziadé (:tarek)]

((In reply to Tarek Ziadé (:tarek) from comment #12)
> Worst case scenario will be to have the same set up as the dev server wrt phone #s.

(Until we've tweaked them of course. But that can happen after the switch.)

Comment 14

[Maire Reavy [:mreavy]]

(In reply to Tarek Ziadé (:tarek) from comment #12)
> (In reply to Fernando Jiménez Moreno [:ferjm] from comment #10)
> > Tarek, could you let us know when the production server is ready, so we can
> > land this patch, please? Thanks :)
> 
> The production deployment is being handled by our ops see bug 1036736 (added
> in the blockers) right after the current tag has been validated and deployed
> on stage. This should be ready early this week.

Tarek -- If this should be ready early this week, can we target landing this patch tomorrow (Wednesday)?   Sorry for the extra pressure, but our drivers are pushing us to land all blockers against v2.0 ASAP.  Thanks.

Comment 15

[Tarek Ziadé (:tarek)]

(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #14)
> 
> Tarek -- If this should be ready early this week, can we target landing this
> patch tomorrow (Wednesday)?  

I will be able to confirm this when Benson gets online today. He's pacific time.

> Sorry for the extra pressure, but our drivers
> are pushing us to land all blockers against v2.0 ASAP.  Thanks.

no problem at all !

Comment 16

[James Bonacci [:jbonacci]]

Production is live with the latest release: 0.3.1.
You can move forward with this change.

Comment 17

[Fernando Jiménez Moreno [:ferjm]]

Thanks!

I'll push it as soon as b2g-inbound or mozilla-inbound are open again (https://treestatus.mozilla.org/)

Comment 18

[Fernando Jiménez Moreno [:ferjm]]

https://hg.mozilla.org/integration/b2g-inbound/rev/a5070fdf5801

Comment 19

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/a5070fdf5801

Comment 20

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/6a7c58688d94

Comment 21

[:shell escalante]

maire provided the info