Closed Bug 289585 Opened 20 years ago Closed 20 years ago

Move Talkback reporting server to new machine (lounge->star)

Categories

(mozilla.org :: Talkback Server & Webtool, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jay, Assigned: jay)

References

Details

lounge is currently a huge monster taking up too much colo space, so I'll be moving all the stuff on that machine to star (which Dave should be making available soon). This bug is mostly for me to keep track of what I find on lounge and what needs to be moved over to the new machine...as well as to keep notes on new software that I will need for future Talkback reporting development. Shiva: Are there any specific requirements for the Talkback reporting server? Any limitations in terms of what software we can use? I'm guessing we have stuck with Solaris for a good reason all this time...but if it's only because of the Oracle client, I'm sure we can get that for Linux from Shaver or something. Dave: If you have the system info for both lounge and star, can you post it here, just so I know exactly what the processory, memory, os configs are for those two machines? Thanks. Chase: Since I'll be setting up the Talkback reports infrastructure from scratch on the new machine, I was also planning on preparing it for development of the release tracker/talkback admin tools (mysql, apache, tomcat, php, etc). If you have any ideas and or suggestions for the software we'll need going forward, let me know so I can get it all installed there. And although it seems like an easy task, lounge originally took me about 2 months to get up and running properly...so I wanted to know if there was any set deadline for me to complete this transfer. Give me a date and I'll try my best to have it done by then...
lounge: System Configuration: Sun Microsystems sun4u Memory size: 2048 Megabytes HD: 40 GB Status of processor 0 as of: 04/08/05 13:04:14 Processor has been on-line since 11/12/04 14:17:26. The sparcv9 processor operates at 248 MHz, and has a sparcv9 floating point processor. Status of processor 1 as of: 04/08/05 13:04:14 Processor has been on-line since 11/12/04 14:17:29. The sparcv9 processor operates at 248 MHz, and has a sparcv9 floating point processor. Status of processor 2 as of: 04/08/05 13:04:14 Processor has been on-line since 11/12/04 14:17:29. The sparcv9 processor operates at 248 MHz, and has a sparcv9 floating point processor. Status of processor 3 as of: 04/08/05 13:04:14 Processor has been on-line since 11/12/04 14:17:29. The sparcv9 processor operates at 248 MHz, and has a sparcv9 floating point processor. star: HP Proliant DL360 G4 Memory size: 4096 MB HD: 65 GB processor : 0 model name : Intel(R) Xeon(TM) CPU 3.00GHz cpu MHz : 3000.246 cache size : 1024 KB processor : 1 model name : Intel(R) Xeon(TM) CPU 3.00GHz cpu MHz : 3000.246 cache size : 1024 KB processor : 2 model name : Intel(R) Xeon(TM) CPU 3.00GHz cpu MHz : 3000.246 cache size : 1024 KB processor : 3 model name : Intel(R) Xeon(TM) CPU 3.00GHz cpu MHz : 3000.246 cache size : 1024 KB Note these are hyperthreaded CPUs, so Linux thinks there's 4 of them, but there's really only 2.
Depends on: 289581
Question: I note that star has about 3 times the horsepower of lounge and mothra combined. Would there be any drawbacks to moving both talkback and talkback-public onto star (with separate IP addresses if necessary)? We could kill off two of those E450s in one shot. The collector appears to be a binary file with a .dll suffix... is there a Linux version?
Dave: That's a good idea. I don't know enough about the repeater to give a definite answer. I'm meeting with Shiva today so we can discuss it then.
Status: NEW → ASSIGNED
star has been added to the RHAPS and Extras channels on RHN. tomcat 5, mod_jk2, IBM Java 1.4.1.2, Oracle 9.2.0.4 client libraries, Perl DBI 1.48 and Perl DBD::Oracle 1.16 have been installed. Nothing has been configured however.
I have successfully moved all Talkback reporting to star and lounge is scheduled to be shutdown soon. The new server has also been moved to our new colo space and has been running fine for a few weeks. Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.