Closed Bug 779644 Opened 9 years ago Closed 7 years ago

Dev/Stage server for OrangeFactor needed

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P4)

x86
macOS

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: automatedtester, Unassigned)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/220] [triaged 20120824])

We need to have a dev/stage environment for Orange Factor for further development/testing.

orangefactor-dev.allizom.org
orangefactor.allizom.org
Please provide a link to documentation on the existing prod setup and details on the code / setup procedures for the application, including language dependencies and database needs

Thanks!
Depends on: 782939
Depends on: 782953
Whiteboard: [pending triage]
We need some more info on this... looking for information about how the prod site is set up (don't even know what the prod URL is), and ideally a mana Websites page: https://mana.mozilla.org/wiki/display/websites/Home
Priority: -- → P3
Whiteboard: [pending triage] → [triaged 20120824][waiting][ateam]
Elastic Search (the database back end) is documented here: https://mana.mozilla.org/wiki/display/websites/Elastic+Search

Orange Factor: https://intranet.mozilla.org/Auto-tools/Systems/Inventory/Applications

Dburns, can you link autolog and orange factor (which are based on brasstacks) to this mana page: https://mana.mozilla.org/wiki/display/websites/brasstacks.mozilla.com The site for orange factor is above and autolog is on the same page.
done
Reassigning P-level per newer scheme.
Priority: P3 → P4
Whiteboard: [triaged 20120824][waiting][ateam] → [triaged 20120824]
We need one page per app/website (dev/stage/prod notwithstanding). It's fine that it's based on brasstacks, but if it's not actually brasstacks then it needs a new page. We can make one and have you populate it... we need the production name of this site (whatever it may be).

Could you let us know:

1) what the prod name/domain of this is (or will be)

2) where the code lives

3) how it should be deployed (re: is git clone / git pull sufficient or is there more)


Thanks!
Whiteboard: [triaged 20120824] → [triaged 20120824][waiting][ateam]
(In reply to Jake Maul [:jakem] from comment #6)
> 
> 1) what the prod name/domain of this is (or will be)

orangefactor.mozilla.com
orangefactor-dev.allizom.org
orangefactor.allizom.org


> 2) where the code lives

http://hg.mozilla.org/automation/orangefactor/
 
> 3) how it should be deployed (re: is git clone / git pull sufficient or is
> there more)

All the details are in here http://hg.mozilla.org/automation/orangefactor/file/tip/README.txt If you can recommend any more steps to streamline let me now.
I have answered all questions from Jake. If you have any more questions just yell, more than willing to give you the info.
Whiteboard: [triaged 20120824][waiting][ateam] → [triaged 20120824]
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Whiteboard: [triaged 20120824] → [kanban:https://kanbanize.com/ctrl_board/4/77] [triaged 20120824]
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/77] [triaged 20120824] → [kanban:https://webops.kanbanize.com/ctrl_board/2/220] [triaged 20120824]
closed as we don't need it anymore since we will see about moving it to live in treeherder
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.