Closed Bug 402123 Opened 13 years ago Closed 13 years ago

Clone unit test slaves for staging environment

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: sean)

References

Details

We have a staging master setup now, but need copies of the current slaves for testing code changes, etc... before they go live. 

The slaves that are currently running are:
* qm-centos5-01
* qm-xserve01
* qm-winxp01
* qm-win2k3-01

We *shouldn't* need to close the tree for this, as long as we only take down one slave at a time for cloning.
What do you want these cloned as (hostnames & vm names)?
Blocks: 397724
Er, these aren't all VMs so directly cloning I can't do. In particular,
qm-win2k3-01 is a physical HP DL360.

Infact, the only one that is a VM is qm-winxp01.  So this is a hardware request
too, right?  
I wasn't sure which were real hardware or not. Performance isn't critical in the staging environment, so I think we could get away with virtualizing them. 

We will need real hardware for the unittest+leaks boxes (bug 397724), so maybe it make sense to use real hardware throughout for the sake of consistency.

robcee/bhearsum: thoughts?
A bit of correction - 

These two are VMs and I can clone them whenever.
* qm-centos5-01
* qm-winxp01

These two are phyiscal boxes.  One's an Apple Xserve and the other is an HP DL360.  

* qm-xserve01
* qm-win2k3-01

Could you work with a Mini and a VM?
Assignee: server-ops → mrz
Yeah, I was going to suggest using a mini as a replacement for the xserve and a vm for the win2k3 machine.
Are these critical to keeping the tree open?  If so, I'd like to use hardware that is production quality and reliable (i.e. not mini's).  Comments on the criticality of these machines?
Justin: the new slaves we're asking for here are for a staging environment where we can test our code changes without(or at least before) breaking the production setup. As such, they will never be critical. 

As robcee/mrz note, they can also be a little slower or virtualized, as long as they are running the same OS/version/software as their counterpart production slave.
Okay, the two VMs will be cloned as two VMs.

The OSX and Windows box will be Minis.  Windows will be a fresh install.  I'll clone the OSX box next time I'm at the colo.
qm-vmware01 doesn't have enough disk space to make a clone.  I need a window to manually move and clone qm-winxp01 - can I shut that VM down any time?
I have qm-centos05-01 cloned but the vmware tools are stale and need updating which can only be done from the console and I can't figure out root's login.

Can someone email me out-of-band?
(In reply to comment #9)
> qm-vmware01 doesn't have enough disk space to make a clone.  I need a window to
> manually move and clone qm-winxp01 - can I shut that VM down any time?

Yes, do it when you get a chance.

Emailing you login creds for qm-centos5-01
qm-stage-centos5-01 / 10.2.73.29 is up.
(In reply to comment #11)
> (In reply to comment #9)
> > qm-vmware01 doesn't have enough disk space to make a clone.  I need a window to
> > manually move and clone qm-winxp01 - can I shut that VM down any time?
> 
> Yes, do it when you get a chance.

About two hours for the first copy to complete, about the same to clone it.  Running right now.
qm-winxp01 is back up.

qm-stage-winxp01 / 10.2.73.18 is up.
Sean - need new installs of OSX and win2k3 on Minis.
Assignee: mrz → sean
Blocks: 403636
Name was truncated to qm-stage-win2k3, but is otherwise setup as specified. Justin is going to do OSX.
Status: NEW → ASSIGNED
qm-stage-osx-01 / 10.2.73.62 is up.

qm-stage-win2k3-01 / 10.2.73.63 is up.

Logins sent to coop.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.