Closed
Bug 827601
Opened 12 years ago
Closed 12 years ago
rename notoriousb2g.personatest.org to native-persona.org
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(blocking-b2g:tef+, blocking-basecamp:-, b2g18+ fixed, b2g18-v1.0.0 fixed)
RESOLVED
FIXED
People
(Reporter: jedp, Assigned: benfrancis)
References
Details
(Keywords: verifyme, Whiteboard: QARegressExclude)
Attachments
(1 file)
For v1 launch, we want to rename notoriousb2g to native-persona.org
There's a DNS switcheroo that needs to happen, and a line or two of gaia code, I believe.
Comment 1•12 years ago
|
||
We need to do this. Is any of the work here in the core? Or is it all Gaia work? Or a mixture of both?
blocking-basecamp: --- → ?
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #1)
> We need to do this. Is any of the work here in the core? Or is it all Gaia
> work? Or a mixture of both?
Just gaia code. Specifically, two lines in apps/system/js/identity.js.
Updated•12 years ago
|
Component: Identity → Gaia::System
Product: Core → Boot2Gecko
Comment 3•12 years ago
|
||
Note to triagers - we pretty much have to do this. Otherwise, persona won't use the right server for v1.
Comment 4•12 years ago
|
||
Jed - ferjm & I are trying native-persona.org and some URL variants, but I'm getting server not found. Can you clarify what URL we should be testing off of?
Flags: needinfo?(jparsons)
Blocks because it will cause breakage in persona. (Original name is ssssoo good though, makes me sad)
blocking-basecamp: ? → +
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → ben
Assignee | ||
Comment 6•12 years ago
|
||
Is this what you meant Jed?
Please confirm domain change before landing.
Attachment #699092 -
Flags: review?(jparsons)
Flags: needinfo?(jparsons)
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #4)
> Jed - ferjm & I are trying native-persona.org and some URL variants, but I'm
> getting server not found. Can you clarify what URL we should be testing off
> of?
Yes, DNS hasn't been set up for native-persona.org yet. Once ops has done that we can make the switch.
Flags: needinfo?(jparsons)
Reporter | ||
Comment 8•12 years ago
|
||
(In reply to Ben Francis [:benfrancis] from comment #6)
> Created attachment 699092 [details] [review]
> https://github.com/mozilla-b2g/gaia/pull/7365
>
> Is this what you meant Jed?
>
> Please confirm domain change before landing.
Hi, Ben, thanks for your help! Please see comments on the PR; and we'll wait for DNS before pulling. Cheers!
Comment 9•12 years ago
|
||
Jed - Can you link to a bug that ops is tracking for the DNS switch? We need mark that blocking-basecamp as well.
Reporter | ||
Comment 10•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #9)
> Jed - Can you link to a bug that ops is tracking for the DNS switch? We need
> mark that blocking-basecamp as well.
I just sent Gene this one. We'll make it clear in the comments here when it's been done.
Comment 11•12 years ago
|
||
Jason, I've linked the ticket with IT requesting the DNS be setup ( Bug 827944 )
Reporter | ||
Comment 12•12 years ago
|
||
That's awesome - Gene, you and cturra did that at an amazing speed.
Now we've got to get an SSL cert. I'm on it.
Assignee | ||
Comment 13•12 years ago
|
||
Do you have a bug number or an ETA for getting the SSL certificate set up Jed? Is that the only thing still blocking this basecamp blocker from landing?
Thanks
Reporter | ||
Comment 14•12 years ago
|
||
Created bug 828486 to track SSL cert
Comment 15•12 years ago
|
||
We've got the cert and I'm requesting approval from OpSec on installing the private key for this cert on the box : Bug 828726
Comment 16•12 years ago
|
||
a=me if this gets done in time, but we won't block basecamp on this. If this doesn't land in time, we will have to send a follow-on patch.
blocking-basecamp: + → -
Comment 17•12 years ago
|
||
(In reply to Andreas Gal :gal from comment #16)
> a=me if this gets done in time, but we won't block basecamp on this. If this
> doesn't land in time, we will have to send a follow-on patch.
Then that's a tef+, blocking- then. Given how we're triaging right now, I'll renom to get this on Gaia triage radar to take the right steps here.
We *do* need to do this before 1.0 goes out the door, no question about it. But I agree this is probably something we can land after Jan 15th.
blocking-b2g: --- → tef?
blocking-basecamp: - → ?
Comment 18•12 years ago
|
||
(In reply to Andreas Gal :gal from comment #16)
> a=me if this gets done in time, but we won't block basecamp on this. If this
> doesn't land in time, we will have to send a follow-on patch.
I recommend we keep this blcoking+. This is not a cosmetic change, it's a necessary change to move the phone to a production hostname. We cannot guarantee uptime on the personatest.org hostname, because it is the root domain for all of our integration testing. That means QA will depend on this, for identity and marketplace.
Given how small a change this is on the client, we should put this back to basecamp+.
back to basecamp? so Andreas and Jason can consider this ASAP.
blocking-b2g: tef? → ---
Comment 19•12 years ago
|
||
I spoke with Dietrich about this at breakfast - this is likely a tef+, but not a basecamp blocker. Configuration changes can land after Jan 15th.
Note - tef+ = we're blocking 1.0 for it, but it doesn't need to be done by Jan 15th.
Make sense?
blocking-b2g: --- → tef?
Assignee | ||
Comment 20•12 years ago
|
||
Is the new domain all set set up and ready for Gaia to switch over? Bug 828726 sounds resolved, is it?
Updated•12 years ago
|
Comment 21•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #19)
> I spoke with Dietrich about this at breakfast - this is likely a tef+, but
> not a basecamp blocker. Configuration changes can land after Jan 15th.
>
> Note - tef+ = we're blocking 1.0 for it, but it doesn't need to be done by
> Jan 15th.
>
> Make sense?
Ah, maybe I don't understand the new tef+ tag.
The one thing I want to make clear is that we might be, at some point very soon, forced to switch very rapidly to native-persona.org to keep things working. If we don't have the ability to do that rapidly, if we're gated by some other administrative process, that could handicap identity & marketplace.
As long as that's clear, and the tef+ tag still makes sense to you Jason, then that's fine with me.
Reporter | ||
Comment 22•12 years ago
|
||
I think I'd like to switch this over this weekend. Since the url is hard-coded in gaia, I'm going to suggest we land the gaia patch today, and as soon as it shows up in the next latest build of b2g, I'll swap the certs. That should result in minimal disruption for testers.
I'll coordinate this with marketplace and identity today (devs and QA)
Reporter | ||
Comment 23•12 years ago
|
||
Actually I take that back. Working with Lloyd and Gene, we've found a way to make the transition seamless.
Reporter | ||
Comment 24•12 years ago
|
||
Once the DNS is reconfigured, this will be good to land. notoriousb2g will redirect to native-persona as long as we need it, which i think will just be through the beginning of next week (however long it takes the gaia patch to make it into everyone's desktop/device/simulator build).
Reporter | ||
Comment 25•12 years ago
|
||
Ok, thanks to Gene, Lloyd, and the amazing IT team for its super speedy action, we now have native-identity.org up, and notoriousb2g redirecting/proxying to it.
Kumar, Krupa, jrgm, and I have verified that thing are working for desktop and phone. So I think we can land this.
Thanks to everyone who helped out on this!
Reporter | ||
Comment 26•12 years ago
|
||
Comment on attachment 699092 [details] [review]
https://github.com/mozilla-b2g/gaia/pull/7365
Thanks for the patch, Ben!
r=me. There's a nit in the comments that would be great to address, but it's not crucial; let's just get this landed :)
Attachment #699092 -
Flags: review?(jparsons) → review+
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-b2g18:
--- → fixed
Comment 27•12 years ago
|
||
Landed on mozilla-b2g18/gaia master prior to the 1/25 branching to mozilla-b2g18_v1_0_0/v1.0.0, updating status-b2g-v1.0.0 to fixed.
status-b2g18-v1.0.0:
--- → fixed
Comment 29•12 years ago
|
||
Can you please provide steps to verify this fix as we will blackbox test from the UI?
Reporter | ||
Comment 30•11 years ago
|
||
Sorry this has gone unanswered for so long. The native-persona.org domain is not used on FirefoxOS. The device is hard-coded to go to firefoxos.persona.org, which is a cname for login.persona.org. The way to verify this is to toggle on the pref toolkit.identity.debug=true, which enables verbose logging of the persona flows, and look for 'persona uri' in the output.
Flags: needinfo?(jparsons)
Updated•11 years ago
|
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in
before you can comment on or make changes to this bug.
Description
•