Closed
Bug 679953
Opened 14 years ago
Closed 14 years ago
Please setup VM for Case Conductor
Categories
(Mozilla QA Graveyard :: Infrastructure, defect)
Mozilla QA Graveyard
Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: camd, Assigned: abillings)
Details
Requirements:
Ubuntu 11.x (whatever is latest is fine)
4 GB RAM
50 GB HD space
MySQL 5.1 (not 5.5)
Java 1.6.x
| Assignee | ||
Comment 1•14 years ago
|
||
Does it actually need 4 GB of RAM for a specific reason? I normally default 1 GB for Ubuntu unless there is a specific need for more.
| Reporter | ||
Comment 2•14 years ago
|
||
Well, it's going to be tested for performance. I can talk to the Dev and see what he thinks. But I sure don't want to constrain it. There will be lots of sql and web activity.
We can start lower, then bump it out later, if you prefer.
| Assignee | ||
Comment 3•14 years ago
|
||
Your box, qa-case-conductor, is set up in PHX colo on qm-vmware02, the QA ESX server there. It is at 10.8.73.222. It has 1 GB of RAM configured right now but I can raise that if you need me to do so.
I have installed MySQL 5.1 on it and openjdk-6-jre is on Ubuntu by default. The box is otherwise naked.
You can ssh into the "mozilla" account there. I will e-mail you the username.
You will need to have the Mozilla-MPT VPN configured and turned on in order to connect to machines in the PHX colo. The machine is not on the public internet. See https://intranet.mozilla.org/JumpHost if you don't have VPN enabled.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•14 years ago
|
||
Oh, and the MySQL password is blank right now so you should change that as well.
| Reporter | ||
Comment 5•14 years ago
|
||
Hey Al,
This is working great, and I'm able to access this machine by it's static IP. I'm not able to access via a domain name, however. Can you set that up? maybe something simple like cc.mozqa.com?
Thanks
| Assignee | ||
Comment 6•14 years ago
|
||
Opened bug 689716 for the name issue.
This bug, itself, is fixed.
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•