Closed Bug 467829 Opened 17 years ago Closed 17 years ago

Setup SUMO/webdev tools server

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: zzxc, Assigned: oremj)

References

Details

Sumo needs to have a server to host various tools, including sumobot (sumo's IRC bot), an instance of cgi:irc, scripts to extract metrics, and web content for special events such as Support Firefox Day. We are currently hosting these on various non-Mozilla servers owned by me, Cheng, and Nelson. These tools should be in a centralized place, rather than being hosted in various locations.
Assignee: server-ops → oremj
Mrz, did you say you had a plan for this?
Assignee: oremj → server-ops
mrz, oremj, is there a timeline for this?
Also djst asked me to add - we'd like to have this server replicate off the sumo master db, so we have an up-to-date but non production box on which to run reporting queries.
I missed oremj's comment. I don't have a plan for this - djst, can you comment on this? Sounds like you're asking for a dev server similar what webdev has. Would like an idea of machine requirements before deciding on VM vs. real hardware.
Assignee: server-ops → mrz
Yes, this would be a dev server that we can run queries on and ultimately use to generate the weekly metrics dashboard (currently we're collecting this info manually by running some queries, looking at Omniture, combining it manually, and updating a Google Doc). Today we're running custom queries on khan -- this bug would move those use cases to a dedicated server for SUMO. As Matthew says in comment 0, we would also use it for cgi:irc, the sumobot, and other various SUMO specific tools. Does that help? In terms of timing, ideally we'd want this soon, e.g. January.
(In reply to comment #5) Actually we're running queries on my computer after a 5-6 GB download and import process. I grab a new dump each week.
(In reply to comment #2) > mrz, oremj, is there a timeline for this? When do you need this by? I have hardware on order but won't likely have it up until mid-January.
Whiteboard: pending hardware
Blocks: 472182
Hardware should be here and online by the end of the week.
Whiteboard: pending hardware → ETA 01/16
Anyone have a good hostname for this? dm-sumotools01?
I don't know if you were asking the sumo team or IT, but dm-sumotools01 seems fine. As long as it's accessible via http(s), the name isn't important to us.
Phong - we're going to use the "spare" SB40 storage blade with this server. Can you move the storage blade (and possibly this one)? This server is not yet in production and can be taken offline anytime. Do we have at least 4 drives to populate the storage blade with?
Assignee: mrz → phong
We do not any drives available for the sb40c. We will need to or more.
the sb40 has been moved to slot 6 in 101.09. I have 4x72gb drives in there. I will have to replace one of the drive later because the spring frame around the drive is a little messed up. There is nothing wrong with the drive itself.
Box is up @ 10.2.11.229. Needs OpenSSH+LDAP, over server-ops. The storage array has 4x72GB SAS drives, mirrored (not yet mounted).
Assignee: phong → server-ops
Summary: support.mozilla.com needs a tools server → Setup SUMO/webdev tools server
Whiteboard: ETA 01/16
(In reply to comment #14) > Box is up @ 10.2.11.229. Needs OpenSSH+LDAP, over server-ops. The storage > array has 4x72GB SAS drives, mirrored (not yet mounted). [reed@boris ~]$ ssh 10.2.11.229 ssh: connect to host 10.2.11.229 port 22: No route to host
(In reply to comment #15) > [reed@boris ~]$ ssh 10.2.11.229 > ssh: connect to host 10.2.11.229 port 22: No route to host It's .230
Assignee: server-ops → oremj
The box is set up. Laura, right now you are the only one with sudo access. The server is called dm-sumotools01(10.2.74.133).
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
I can ssh in and have sudo. There will be a couple of flow on bugs I think, coming soon.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.