420772 - Migrate sea-mozbuild-win32-tbox to community VM host

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Chris Cooper [:coop] (he/him)]

We brought up the new SeaMonkey win32 ref VM on an internal Moz VM host because the community host is at capacity. Now that the build output from the new VM has been verified, we'd like to move it to the community VM host and disable the old VM.

Can we schedule this move? KaiRo can let you know if there are any scheduling issues around an outage, although I imagine if users are still relying on the old builds, they shouldn't notice much if anything.

The new VM already has the standard root and seabld user credentials for use in the community network. KaiRo *should* be able to login as soon as the VM hits the network.

Can we also get the VM renamed at the same time to match the old machine (sea-win32-tbox) for continuity?

Comment 1

[Chris Cooper [:coop] (he/him)]

NOTE: the tinderbox is running with a locally-modified copy of tinder-config.pl to send the builds to experimental/. We'll need to remove that file (and indeed all of SeaMonkey-Trunk/tinderbox-configs) when the move is made and re-checkout to pickup the canonical config.

Comment 2

[matthew zeier [:mrz]]

1. I need to shutdown this VM to move it.
2. Community Build doesn't use DHCP - I'll need to statically assign IP info.  Can I get root or a root-like login?

Comment 3

[matthew zeier [:mrz]]

(In reply to comment #0)
> Can we also get the VM renamed at the same time to match the old machine
> (sea-win32-tbox) for continuity?

What do you want me to do with that current VM?  Shutdown?

Comment 4

[Robert Kaiser]

Yes, take the old one down, it should be obsoleted by the new one.

Comment 5

[matthew zeier [:mrz]]

Can I go so far as to delete it?

Comment 6

[Robert Kaiser]

As long as the new one works well on the community machine and we don't need to bring the old one back, you can delete the old one.

Comment 7

[matthew zeier [:mrz]]

Still stuck on #1 & #2 then :)

Comment 8

[Robert Kaiser]

We somehow managed to get that done for the Linux machine though, and could even bring back the old one in between for a bit, have things grown so different since then?

Comment 9

[matthew zeier [:mrz]]

Clone keeps failing with some unknown error message.  Manually scp'd the VM over and tried to register it:

[root@cb-vmware01 sea-mozbuild-win32-tbox]# vmware-cmd -s register /vmfs/volumes/4613b86c-af03ef11-6e92-0016353c919a/sea-mozbuild-win32-tbox/sea-mozbuild-win32-tbox.vmx
VMControl error -999: Unknown error

Opening case with vendor.

Comment 10

[matthew zeier [:mrz]]

Case resolved, have some other config work to do still.

Comment 11

[matthew zeier [:mrz]]

(In reply to comment #4)
> Yes, take the old one down, it should be obsoleted by the new one.
> 

Can I shut the old one (the current one) down at any time and bring up the new one or does that require something on your end?  I'm ready to do it now but I don't want to break anything that might be depending on this host.

Comment 12

[Robert Kaiser]

You can take down the old one at any time, there's nothing depending on the machine specifically.
The only requirement is that we have a Windows tinderbox generating nightlies - and we'll have that with the new one after the change as well :)

Comment 13

[matthew zeier [:mrz]]

New VM is up (old is powered down).  Same IP and hostname.

Comment 14

[Robert Kaiser]

The VM is there and I took over control of it, thanks.

Comment 15

[matthew zeier [:mrz]]

The old VM is still there but powered off.  Let me know when you think it's fine to delete it to recover disk space (no rush though).

Comment 16

[Robert Kaiser]

OK, everything seems to be alright with the new machine, so feel free to delete the old one. Thanks a lot for your work on this.