771728 - Get SeaMonkey off parallels1 already..

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

There are three VMs left on parallels1:
 cb-seamonkey-linux-01
 cb-seamonkey-linux64-01
 cb-seamonkey-linuxmaster-01

the options for these are to migrate them to one of parallels{2,3}, which are mini servers, or replace them with their Linux equivalents if that's close to happening.

I'd like to retire parallels1 soon, before it retires itself.

Let me know which option seems most expedient?

Comment 1

[Edmund Wong (:ewong)]

Well we do have a linux64 and linux32 slaves in the works of being switched on 
(I think the machines are 'ready'..just needs a reboot iiuc).  

So if we do switch these machines on and migrate the linux-01 and linux64-01 to
something (assuming we use parallels2/3), then we'd have an extra linux64
and linux32.  

The situation with the master is confusing.(as in I'm not too clear as to
what is cb-seamonkey-linuxmaster-01 and sea-master1..)  I use sea-master1.
IIUC, sea-master1 is actually cb-seamonkey-linuxmaster-01 but for scl3.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

I think your master has several names, but that's it.

cb-seamonkey-linuxmaster-01.mozilla.org. 600 IN   CNAME sea-master1.community.scl3.mozilla.com.

but the VM in parallels hasn't been renamed.

For the linux/linx64 slaves, the idea has been to *replace* these hosts with ESX, so these aren't "extra".  We can migrate them to parallels2/3 if their replacements aren't ready yet, but otherwise we should just turn them off.

As for timeline, I was hoping this would be done before or about the time we moved the xserve to scl3, so I want to make sure we're progressing toward the objective expediently.

Comment 3

[Justin Wood (:Callek)]

parallels1 is dead we never did a proper migration but everything is off it.