Closed Bug 829115 Opened 13 years ago Closed 13 years ago

migrate from kvm to vmware in scl1

Categories

(Infrastructure & Operations :: Virtualization, task)

Product:
Infrastructure & Operations
Component:
Virtualization
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: arich, Unassigned)

Details

(Whiteboard: [2013Q1])

KVM is not supported by the storage and virtualization team, so we will be replacing kvm with vmware in scl1 to start. This work will commence with purchase and installation of netapp/vmware in scl1 in Q1. mtv1 kvm will eventually go away when we move machines out of that location, and scl3 already has a vmware infrastructure to which we can migrate when ready.
I need to know how many VMs we will be supporting. This has been answered previously, but I've heard that the buildbot masters may move to AWS. With them gone, how many VMs will we need in scl1?
At minimum: dc7.releng.ad.mozilla.com dc9.releng.ad.mozilla.com ganglia1.build.scl1.mozilla.com (and possibly some more ganglia vms) puppet1.infra.scl1.mozilla.com wds2.releng.ad.mozilla.com talos-addon-master1.amotest.scl1.mozilla.com mobile-services.build.scl1.mozilla.com mobile-imaging-stage1.build.scl1.mozilla.com Possibly also (especially signing1/2, I can't imagine that will move to AWS): buildapi01.build.scl1.mozilla.com master-puppet1.build.scl1.mozilla.com rabbit1-dev.build.scl1.mozilla.com redis01.build.scl1.mozilla.com releng-puppet1.build.scl1.mozilla.com scl-production-puppet.build.scl1.mozilla.com signing1.build.scl1.mozilla.com signing2.build.scl1.mozilla.com slavealloc.build.scl1.mozilla.com And then there are the buildbot-masters, which seem to be the main ones that are up in the air: buildbot-master04.build.scl1.mozilla.com buildbot-master06.build.scl1.mozilla.com buildbot-master11.build.scl1.mozilla.com buildbot-master12.build.scl1.mozilla.com buildbot-master13.build.scl1.mozilla.com buildbot-master14.build.scl1.mozilla.com buildbot-master15.build.scl1.mozilla.com buildbot-master16.build.scl1.mozilla.com buildbot-master17.build.scl1.mozilla.com buildbot-master18.build.scl1.mozilla.com buildbot-master21.build.scl1.mozilla.com buildbot-master23.build.scl1.mozilla.com buildbot-master24.build.scl1.mozilla.com buildbot-master25.build.scl1.mozilla.com buildbot-master29.build.scl1.mozilla.com buildbot-master39.build.scl1.mozilla.com buildbot-master40.build.scl1.mozilla.com buildbot-master41.build.scl1.mozilla.com buildbot-master42.build.scl1.mozilla.com buildbot-master43.build.scl1.mozilla.com buildbot-master44.build.scl1.mozilla.com buildbot-master45.build.scl1.mozilla.com buildbot-master46.build.scl1.mozilla.com buildbot-master47.build.scl1.mozilla.com buildbot-master48.build.scl1.mozilla.com dev-master01.build.scl1.mozilla.com It would seem most unwise to move these to AWS when they're managing the machines in scl1 because of the issues buildbot has with disconnects with any network blip, but that's not my call to make.
As scl1 is being closed, WONTFIXing this.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.