836928 - Change native-persona.org references to persona.org when browserid b2g branch merges with dev

Status: RESOLVED DUPLICATE of bug 863417

(Core Graveyard :: Identity, defect)

Description

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

The work done in the b2g branch of browserid (persona code base) will be merged into the main dev branch.  When this happens, we need to update links in our client code from the integration server native-persona.org to the production server persona.org.

I have opened issue 2982 for browserid to track the server work: https://github.com/mozilla/browserid/issues/2982

I think Marketplace and Identity are the only parties that need to care about this right now.  So once that bug is closed, they can file follow-ups to block this bug and land the change from native-persona to persona.  Does that sound like a plan?

Comment 1

[Jason Smith [:jsmith]]

Umm...why are we flipping around servers past the Jan 15th date? This isn't going to make the triage guys too happy.

We can't guarantee what build the OEM guys are running either (it's up to them to pick what build they are running, not Mozilla, even if we suggest a later build).

Comment 2

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

Hi, Jason,

I should have mentioned that we will be able to have native-persona.org redirect (and proxy the verifier) to persona.org indefinitely, so if for some reason we can't get an update pushed to the OEMs' code or subsequently to device, everything will still work.

Comment 3

[Ben Adida [:benadida]]

Jason: also important and worth mentioning that we received guidance from B2G team that critical server architecture pointer patches would be acceptable after Jan 15th, assuming they are well motivated.

Comment 4

[Alex Keybl [:akeybl]]

(In reply to Jed Parsons [:jparsons] from comment #0)
> The work done in the b2g branch of browserid (persona code base) will be
> merged into the main dev branch.  When this happens, we need to update links
> in our client code from the integration server native-persona.org to the
> production server persona.org.
> 
> I have opened issue 2982 for browserid to track the server work:
> https://github.com/mozilla/browserid/issues/2982
> 
> I think Marketplace and Identity are the only parties that need to care
> about this right now.  So once that bug is closed, they can file follow-ups
> to block this bug and land the change from native-persona to persona.  Does
> that sound like a plan?

What's the ETA on this merge? Preferably, this would happen no later than next week.

Comment 5

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

I don't expect the server-side persona code will be merged until the next train or two have departed.  I defer to Lloyd for a sense of what the schedule might be.

Lloyd, do you have any sense of when the b2g branch will be merged into dev?

Alex and Andrew, the existing configuration should be ok for b2g, as we can swing native-persona.org to redirect and proxy as necessary to persona.org at any time.  We've already done this once before, to transition notoriousb2g to native-persona, so we know it will work.

Comment 6

[Jason Smith [:jsmith]]

(In reply to Jed Parsons [:jparsons] from comment #5)
> I don't expect the server-side persona code will be merged until the next
> train or two have departed.  I defer to Lloyd for a sense of what the
> schedule might be.
> 
> Lloyd, do you have any sense of when the b2g branch will be merged into dev?
> 
> Alex and Andrew, the existing configuration should be ok for b2g, as we can
> swing native-persona.org to redirect and proxy as necessary to persona.org
> at any time.  We've already done this once before, to transition
> notoriousb2g to native-persona, so we know it will work.

This comment reads off that we should track this for b2g18, but not block. Sounds like it's not the "end of the world" if we shipped with this bug still in the product.

Comment 7

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

Yes, that's my feeling.  I opened this as a core identity bug to track work that we (identity) eventually need to resolve, but I don't think this is a blocker.

Comment 8

[Jed Parsons (use needinfo, please) [:jedp, :jparsons]]

(In reply to Jed Parsons [:jparsons] from comment #7)
> Yes, that's my feeling.  I opened this as a core identity bug to track work
> that we (identity) eventually need to resolve, but I don't think this is a
> blocker.

Yes, I said that, and I see now that I was wrong.

When we last evaluated this issue, it seemed that a proxy/redirect solution for the first batch of phones would be ok.

Having heard repeated complaints about network latency issues (which redirect will only compound), and having discussed the enormous stability and maintenance implications with the identity team and our ops team, I say that I was wrong two months ago in thinking that this was not a blocker.

We must have tef phones pointing to a url in the persona.org domain.

Jason has referred discussion from bug 863417 here, so I'm nomming this tef+

Comment 9

[Jason Smith [:jsmith]]

I think that's okay. Let's do the one-line gaia fix in this bug to flip the URL on a 1.01-specific patch.

We should ask if someone from Edwin's team could take a look at a custom build with the production URL to see if nothing scary is busted.

Edwin - Can someone on your team generate a custom build with the production URL and do some sanity checking to make sure nothing scary is going to break here?

Comment 10

[Edwin Wong [:edwong]]

Yes - we'll test the fix locally now and update the bug with our results.

Comment 11

[Jason Smith [:jsmith]]

We've agreed now on fixing this over in bug 863417.