We're currently using: https://l10n-dev-sj.mozilla.org/ which is wrong in numerous ways. What we should be using is: https://l10n-dev.allizom.org I also think we should keep a redirect of the old domain name.
We do have https://elmo-dev.allizom.org/, but that's pointing to different machines. See bug 652792.
So, all we need is to correct the IP address is points to and set up Apache. Badabing! Shall I move this bug to Web Operations?
Assignee: nobody → server-ops
Component: Elmo → Server Operations: Web Operations
Product: Webtools → mozilla.org
QA Contact: elmo → cshields
Version: 1.0 → other
So... slightly confused here. Should l10n-dev-sj.mozilla.org and l10n-dev.allizom.org both redirect to elmo-dev.allizom.org ? Or does comment 0 still apply?
(In reply to Jake Maul [:jakem] from comment #3) > So... slightly confused here. Should l10n-dev-sj.mozilla.org and > l10n-dev.allizom.org both redirect to elmo-dev.allizom.org ? Or does comment > 0 still apply? l10n-dev.allizom.org should POINT to the server l10n-dev-sj.mozilla.org should REDIRECT (permanent) to l10n-dev.allizom.org I'm sorry for not noticing Axel's comment. I don't know about elmo-dev.allizom.org. The code is called "elmo" but the service is called "l10n" as we're using this code to run l10n.mozilla.org
This is all confusing. Can you re-state what you're asking for exactly?
(In reply to Shyam Mani [:fox2mike] from comment #5) > This is all confusing. Can you re-state what you're asking for exactly? Sure thing. Just the standard naming practice. LIVE: l10n.mozilla.org ---> 126.96.36.199 (already set up and working) DEV: l10n-dev.allizom.org ---> 188.8.131.52 LEGACY l10n-dev-sj.mozilla.org -R-> l10n-dev.allizom.org elmo-dev.allizom.org -R-> l10n-dev.allizom.org (or just drop it)
(In reply to Peter Bengtsson [:peterbe] from comment #6) > LIVE: l10n.mozilla.org ---> 184.108.40.206 (already set up and working) > DEV: l10n-dev.allizom.org ---> 220.127.116.11 You want dev to point to prod?
(In reply to Corey Shields [:cshields] from comment #7) > (In reply to Peter Bengtsson [:peterbe] from comment #6) > > LIVE: l10n.mozilla.org ---> 18.104.22.168 (already set up and working) > > DEV: l10n-dev.allizom.org ---> 22.214.171.124 > > You want dev to point to prod? Good catch! But yeah. It is so. Until https://bugzilla.mozilla.org/show_bug.cgi?id=652792 We're currently hosting the dev and production site on the same server. One Apache and two django repos, one in /home/dashboard/test/elmo and one in /home/dashboard/site/elmo I think #652792 got stuck in tar due to the problem with migrating its naive log files in one masssive directory. That bug has lost its momentum so I've lost track of where we're at.
Not really sure why this was left assigned to me.
Assignee: shyam → server-ops-webops
Priority: -- → P3
Whiteboard: [triaged 20120910][push-interrupt]
CORRECTION: Do not change elmo-dev.allizom.org Everything else as per comment #6.
Assignee: server-ops-webops → dmaher
Status: NEW → ASSIGNED
Priority: P3 → P4
Hi :peterbe, For the record, "l10n-dev.allizom.org" already exists : l10n-dev.allizom.org has address 126.96.36.199 That address is a Zeus VIP which points to two Seamicro nodes : node8.seamicro.phx1.mozilla.com It would therefore appear that there is a development infrastructure in place. In light of this information, perhaps we should clarify exactly what you want to have done. Is the extant dev infra used ? If so, how does that play into your request ? If not, can we go ahead and decommission it entirely ? Please clarify / amplify. Thank you.
I'm happily taking the blame for this goose chase. I wanted us to start using the more correct naming pattern for dev, stage and prod. One step at a time. Turns out, that that's already been prepared for and thought of but geared towards the new dedicated hardware. So, whilst Elmo is still hosted on the old hardware Axel and I will simply have to live with the not-so-standard domain name for the dev server. Thanks for helping out guys!
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.