Closed Bug 1403252 Opened 7 years ago Closed 6 years ago

re-deploy wds1.releng.ad.mozilla.com using the 2012 vmware template in scl3

Categories

(Infrastructure & Operations :: Virtualization, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: q, Assigned: cknowles)

References

Details

(Whiteboard: [vm-create:1])

Wds1 needs to match mdt02 on 2012 and new version of MDT should be redeployed using the vmware 2012 template. We will spin up the new box and IP switch the vms. Same as was done in 1364897 and 1382846
Assignee: relops → server-ops-virtualization
Component: RelOps → Virtualization
QA Contact: arich → cshields
So, temp-wds1.releng.ad.mozilla.com

Same spec as existing wds1?  

2 CPU
8G RAM
60g C drive, 
two other disks?  What size would you like those?

Let me know and we can start deploying.
Assignee: server-ops-virtualization → cknowles
Severity: critical → normal
Priority: P2 → --
Whiteboard: [vm-create:2][vm-delete:2]
Right sorry stepped on my own update:

2 CPU
8gb RAM
80 GB C drive
600 GB E Drive
300 GB G drive

Would it be possible to disconnect the E and G drives from the current  wds1 and attachment them to the new template ( then expand at least the e drive) ?
We can, but that's not a warm operation - I need to power down the original wds1 and then copy files around and we can then mount up the disks on the new wds 1.

If that's a direction you'd like to go, can you give me the disk layout on existing wds1?  

Disk 1: 60G : C:
Disk 2: 350G : ?
Disk 3: 250G : ?

Given that it's not warm, would you like me to start deploying temp-wds1 *now* with just a C:?  Then we can either add blank disks, or disks from original later...
350 E
250 G

Yes let's deploy with just a C drive and we can copy when the switch over is eminent 

Q
Alright, starting on that.  Depending on updates and the like, I expect this to be done early tomorrow at the latest.
Alright, deployed, updated, in inventory and tracking sheets.

administrator password gpg'd and sent to you.

I'm feeling like we should leave this open for the changeroo step - what with copying over the drives.  

If you have any questions, please let me know.
Whiteboard: [vm-create:1]
Latest there was a small delay of game as the storage from the old wds1 needed to be moved around to allow the disks to be attached to the new wds1. That is now done and the disks have been expanded to get us out of the storage red (thanks to gcox and ckowles) . I am updating the shares right now and the upgrade should be done today.
have renamed the VMs in vsphere. Original wds is now "old-wds1.releng.ad.mozilla.com"

Let me know when we can delete the old VM.  

And let us know if there's any concerns or questions with the new one.
Q: Just stumbled across this - can I delete the old VM?
Flags: needinfo?(q)
Re-commenting.  Q, can I delete the old VM?
I will need to either mount the c drive of this machine to another vm or keep it around until we know if XP support is actually going away ( this older 2008 machine is the only place that would support it )
Flags: needinfo?(q) → needinfo?(klibby)
We can keep the VM for now - though it's in SCL3, so it'll need a plan to move somewhere before too long.  I've added it back to our inventory and tracking sheets as "old-wds1.ad.db.scl3.mozilla.com".
Any word on whether this is going away, or if it's becoming permanent?
Kendall can we kill XP reimaging 100%?
(In reply to Q from comment #14)
> Kendall can we kill XP reimaging 100%?

Kill it dead.
Flags: needinfo?(klibby)
With the close/shutdown of SCL3, these are down.  Closing out
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.