Closed Bug 773147 Opened 12 years ago Closed 12 years ago

Bring up SeaMonkey linux32 VM's based on sea-vm-linux32-2

Categories

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

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: afernandez)

References

Details

So we need to bring up more linux32 VMs for SeaMonkey based on what we proportioned out. This should be done based on sea-vm-linux32-2. As well as allowing a snapshot/backup to be taken of the image.

We need to setup a downtime (anything >12 hours from when you post here is ok), to clear yum cache, .ssh keys, /builds repeatable data, and move aside buildbot.tac (and its pw inside). Once that is done, we have to create/setup the VMs and the backup.

sea-vm-linux32-3
sea-vm-linux32-4
sea-vm-linux32-5
sea-vm-linux32-6

Will be first to be created, and once they are up, we can schedule a downtime for sea-vm-linux32-1, so that we can then delete it and replace with the generic image.

In parallel with sea-vm-linux32-1 we can determine when to downtime cn-sea-qm-centos5-01 and just get that deleted to rid ourselves of ams1.

Any Q's see me in IRC.
Blocks: 773149
Assignee: server-ops → afernandez
:Callek  as of right now lets schedule this for Monday 07/16/2012.

Thanks
This is safe to bring down/clone/etc.now, we cleaned it out
Ran into some issues with the "Clone to Template" process.
Working on fixing.

issue:
Seems VMware merged the 10GB and the 30GB disk into one 100GB =(.
Forgot to add this last night but sea-vm-linux32-2.community.scl3.mozilla.com has been ready since last night.

Callek tried to verify that all was well but work relating to Bug 774413 , hindered the process and he will verify the status of the VM today. Once the "OK" is given, i will deploy the rest of the VMs from the "sea-vm-linux32" template.
Nope not ok:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             8.3G  7.5G  337M  96% /
tmpfs                 1.5G     0  1.5G   0% /dev/shm
/dev/sdb1              30G  1.2G   27G   5% /builds

So, now I realize how we had 100GB turn out here, we need more space on /dev/sda1 I suggest 20GB (since seamonkey profile-related stuff gets placed there from running jobs)

And 80GB on /dev/sdb1

Let me know when these are increased and I'll dive back in
/dev/sda1 increased to 20GB
/dev/sdb1 increased to 80GB

Please verify that all is well, thank you.
preliminarily it looks ok, but can we try to take a new template from this again, I had to [re] change some of the file perms/groups here.
sea-vm-linux32-{2-6}.community.scl3.mozilla.com are online.

Please let me know when to downtime sea-vm-linux32-1.community.scl3.mozilla.com
sea-vm-linux32-(2..6) are up and running builds.
As per Callek, will be re-deploying sea-vm-linux32-1.community.scl3.mozilla.com tomorrow after he removes it from production cleanly.
sea-vm-linux32-1.community.scl3.mozilla.com currently being re-deployed.
Will update once back online.
sea-vm-linux32-1.community.scl3.mozilla.com online now.

As for cn-sea-qm-centos5-01 , have an actual IP so that I could locate the host? As can't seem to find anything under that name in the DNS.
CNN-sea-qm-centos5-01.Mozilla.org. it's in ams1
sea-vm-linux32-1 is up and building.
Ok found it;

cn-sea-qm-centos5-01.nl.mozilla.org (DNS)
and in inventory:
sea-qm-centos5-01

VM deleted, removed from inventory and from DNS.
Status: NEW → 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.