Closed Bug 409042 Opened 12 years ago Closed 12 years ago
Create image of Windows 2k3 buildbot slave
Is it possible for IT to create an image of a fresh Windows 2k3 install that we can use to reimage (new) hardware? We have 4 Win2k3 slaves that need to be setup right now (and we'll likely have more in the future), and I'd rather do it once and then use that image on the new boxes. I'm going to be installing the first of the Win2k3 machine this afternoon. We can use that one to take the initial image once it's ready.
typical fresh installs on new hardware have been straight off cd. The only difference is with the Mac minis we've been deploying but I don't know if those are purpose built for Talos or could be used for anything. VMs have all been off some build ref image.
We should be able to image these (to the same hardware) fairly easily using clonezilla. Once the main one is up, let us know and we'll image it. Note, the image can only go onto the same hardware. Windows is cool like that :/
coop - can you be sure to run sysprep when you're ready to take the image? And then let us know when you're ready to take images.
Assignee: server-ops → sean
(In reply to comment #3) > coop - can you be sure to run sysprep when you're ready to take the image? > And then let us know when you're ready to take images. Sure, will do. (In reply to comment #2) > We should be able to image these (to the same hardware) fairly easily using > clonezilla. Once the main one is up, let us know and we'll image it. Note, > the image can only go onto the same hardware. Windows is cool like that :/ This is what I feared. What is the likelihood of being able to reinstall onto exactly the same hardware, i.e. are the machines we deploy for this relatively common (e.g. minis)? Would I be better served by creating a bulletproof install/reinstall doc instead?
qm-leak-w2k3-01 is ready for imaging. I've downloaded the sysprep tool (in C:\sysprep) but I don't know what settings IT needs for fast/cheap/easy re-imaging. Does IT have docs on the required options for syspref.inf, or is this something better handled by IT directly?
Putting this back into the ServerOps queue since I won't have time to get to it before I leave for the week.
Assignee: sean → server-ops
Is this likely to happen soon, or can I turn buildbot on this slave back on for a little while?
We are a little short handed as sean is out a macworld and I'm in review times. Can this wait for a week or is it blocking work...?
Phong, can you take an image of this box?
Assignee: server-ops → phong.tran
He doesn't know how to take images...someone would have to walk him through it and given it's a one time thing, not sure it's worth the effort - back to oncall (mrz in this case).
Assignee: phong.tran → mrz
I'm wrong - phong can do this.
Assignee: mrz → phong.tran
I need the username and password to shutdown windows.
Status: NEW → ASSIGNED
Phong: the standard buildbot user and password should work. If not, ping me on IRC. I'll stop the slave now, and cleanup the slave dir in anticipation of imaging. We'd like to get this image onto the 2 waiting DL360s early next week if possible so we can start working on parallelizing unit testing, but I'll file a separate bug for that once we have an image.
Chris: The standard builbot username/password did not work. Is there another password I could use?
I just logged into that box via RDP using the standard buildbot username/password. Ping me on IRC to make sure you're using the right one.
Image was created from qm-leak-win2k3-01. The image is on IMAGE MASTER.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.