Closed Bug 846332 Opened 12 years ago Closed 11 years ago

[tracking bug] migrate hosts off of KVM

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Assigned: catlee)

References

Details

(Keywords: spring-cleaning, Whiteboard: [2013Q2] [tracker][reit])

We need to migrate all our hosts off of KVM. Please file specific bugs that block this one for hosts or groups of hosts that need to be migrated off of KVM.
per last emails on this, I believe this is the list of VMs currently based on KVM: obsolete? ========= jump1.comm-build.scl1.mozilla.com (callek confirmed not being used by SeaMonkey. Is this used by IT?) talos-addon-master1.amotest.scl1.mozilla.com (confirmed obsolete by ATeam) claimed by IT: ============== mobile-services.build.scl1.mozilla.com (dustin) rabbit1-dev.build.scl1.mozilla.com (RelOps) puppet1.infra.scl1.mozilla.com dc7.releng.ad.mozilla.com dc9.releng.ad.mozilla.com ganglia1.build.scl1.mozilla.com wds2.releng.ad.mozilla.com admin1.infra.scl1.mozilla.com (to be decommissioned) wds01.winbuild.scl1.mozilla.com (to be decommissioned) claimed by RelEng, moving from kvm to ESX: ========================================== signing1.build.scl1.mozilla.com signing2.build.scl1.mozilla.com slavealloc.build.scl1.mozilla.com buildapi01.build.scl1.mozilla.com master-puppet1.build.scl1.mozilla.com releng-puppet1.build.scl1.mozilla.com scl-production-puppet.build.scl1.mozilla.com redis01.build.scl1.mozilla.com claimed by RelEng, moving from kvm to AWS: ========================================== 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 If anyone has a revised list, please adjust here.
That's only scl1. For all the kvm vms allocated to releng: https://inventory.mozilla.org/en-US/reports/ Set allocation to "release" type in the following for server model: kvm
Depends on: 847932
(In reply to John O'Duinn [:joduinn] from comment #1) > per last emails on this, I believe this is the list of VMs currently based > on KVM: > > > obsolete? > ========= > jump1.comm-build.scl1.mozilla.com (callek confirmed not being used by > SeaMonkey. Is this used by IT?) > talos-addon-master1.amotest.scl1.mozilla.com (confirmed obsolete by ATeam) In inventory, I dont see these under "release", but that doesnt mean anything. arr: can you confirm these two KVMs are deleted?
No longer depends on: 849002
Merging and de-DUP-ing lists from comment#1 and comment#2, here's the revised consolidated list of VMs on all Mozilla KVM servers in inventory. claimed by IT: ============== mobile-services.build.scl1.mozilla.com (dustin) rabbit1-dev.build.scl1.mozilla.com (RelOps) puppet1.infra.scl1.mozilla.com dc7.releng.ad.mozilla.com dc9.releng.ad.mozilla.com ganglia1.build.scl1.mozilla.com ganglia3.build.mtv1.mozilla.com wds2.releng.ad.mozilla.com admin1.infra.scl1.mozilla.com (to be decommissioned) wds01.winbuild.scl1.mozilla.com (to be decommissioned) wds2.releng.ad.mozilla.com (unknown if needed?) mobile-imaging-stage1.p127.releng.scl1.mozilla.com claimed by RelEng, moving from kvm to ESX: ========================================== signing1.build.scl1.mozilla.com signing2.build.scl1.mozilla.com signing3.srv.releng.scl3.mozilla.com slavealloc.build.scl1.mozilla.com buildapi01.build.scl1.mozilla.com redis01.build.scl1.mozilla.com releng-puppet1.build.mtv1.mozilla.com releng-puppet1.build.scl1.mozilla.com master-puppet1.build.scl1.mozilla.com scl-production-puppet.build.scl1.mozilla.com scl3-production-puppet.srv.releng.scl3.mozilla.com staging-puppet.srv.releng.scl3.mozilla.com claimed by RelEng, moving from kvm to AWS: ========================================== 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 buildbot-master10.build.mtv1.mozilla.com buildbot-master20.build.mtv1.mozilla.com buildbot-master22.build.mtv1.mozilla.com mobile-dashboard1.build.mtv1.mozilla.com buildbot-master28.build.mtv1.mozilla.com mongo1-dev.srv.releng.scl3.mozilla.com buildbot-master30.srv.releng.scl3.mozilla.com buildbot-master31.srv.releng.scl3.mozilla.com buildbot-master32.srv.releng.scl3.mozilla.com buildbot-master33.srv.releng.scl3.mozilla.com buildbot-master34.srv.releng.scl3.mozilla.com buildbot-master35.srv.releng.scl3.mozilla.com buildbot-master36.srv.releng.scl3.mozilla.com buildbot-master37.srv.releng.scl3.mozilla.com buildbot-master38.srv.releng.scl3.mozilla.com buildbot-master49.srv.releng.scl3.mozilla.com preproduction-master.srv.releng.scl3.mozilla.com preproduction-stage.srv.releng.scl3.mozilla.com
(In reply to John O'Duinn [:joduinn] from comment #4) > Merging and de-DUP-ing lists from comment#1 and comment#2, here's the > revised consolidated list of VMs on all Mozilla KVM servers in inventory. > > > claimed by IT: > ============== > mobile-services.build.scl1.mozilla.com (dustin) > rabbit1-dev.build.scl1.mozilla.com (RelOps) > puppet1.infra.scl1.mozilla.com > dc7.releng.ad.mozilla.com > dc9.releng.ad.mozilla.com > ganglia1.build.scl1.mozilla.com > ganglia3.build.mtv1.mozilla.com > wds2.releng.ad.mozilla.com > admin1.infra.scl1.mozilla.com (to be decommissioned) > wds01.winbuild.scl1.mozilla.com (to be decommissioned) > wds2.releng.ad.mozilla.com (unknown if needed?) > mobile-imaging-stage1.p127.releng.scl1.mozilla.com This work being tracked in bug#849035. > claimed by RelEng, moving from kvm to ESX: > ========================================== > signing1.build.scl1.mozilla.com > signing2.build.scl1.mozilla.com > signing3.srv.releng.scl3.mozilla.com > slavealloc.build.scl1.mozilla.com > buildapi01.build.scl1.mozilla.com > redis01.build.scl1.mozilla.com > releng-puppet1.build.mtv1.mozilla.com > releng-puppet1.build.scl1.mozilla.com > master-puppet1.build.scl1.mozilla.com > scl-production-puppet.build.scl1.mozilla.com > scl3-production-puppet.srv.releng.scl3.mozilla.com > staging-puppet.srv.releng.scl3.mozilla.com This work being tracked in bug#849037. > claimed by RelEng, moving from kvm to AWS: > ========================================== > 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 > > buildbot-master10.build.mtv1.mozilla.com > buildbot-master20.build.mtv1.mozilla.com > buildbot-master22.build.mtv1.mozilla.com > mobile-dashboard1.build.mtv1.mozilla.com > buildbot-master28.build.mtv1.mozilla.com > > mongo1-dev.srv.releng.scl3.mozilla.com > buildbot-master30.srv.releng.scl3.mozilla.com > buildbot-master31.srv.releng.scl3.mozilla.com > buildbot-master32.srv.releng.scl3.mozilla.com > buildbot-master33.srv.releng.scl3.mozilla.com > buildbot-master34.srv.releng.scl3.mozilla.com > buildbot-master35.srv.releng.scl3.mozilla.com > buildbot-master36.srv.releng.scl3.mozilla.com > buildbot-master37.srv.releng.scl3.mozilla.com > buildbot-master38.srv.releng.scl3.mozilla.com > buildbot-master49.srv.releng.scl3.mozilla.com > preproduction-master.srv.releng.scl3.mozilla.com > preproduction-stage.srv.releng.scl3.mozilla.com This work being tracked in bug#849002.
Depends on: 849035, 849037, 849002
(In reply to John O'Duinn [:joduinn] from comment #3) Those vms don't show up because they don't have anything to do with releng. You don't need to worry about them.
I'm sure that we're going to want to split this out by class of machine, not group ownership, but we can talk more about that on Wednesday.
Blocks: 855733
Whiteboard: [2013Q2] [tracker]
Depends on: 863263
Depends on: 863266
Depends on: 863268
Depends on: 863275
Depends on: 864364
Depends on: 867583
No longer blocks: 855733
Whiteboard: [2013Q2] [tracker] → [2013Q2] [tracker][reit]
Depends on: 867602
There's been a chance in plans in that not all buildbot masters are moving to KVM. We need to stand up some number of them on VMWare for enough in-house capacity for chemspills (see bug 867593).
(In reply to Amy Rich [:arich] [:arr] from comment #8) That should be "moving to AWS"
Depends on: 869498
Depends on: 869548
Product: mozilla.org → Release Engineering
For hosts that don't have their own bugs on the releng side, any news on the plans for these hosts? preproduction-master.srv.releng.scl3.mozilla.com (or should this be covered under the buildbot-master bug?) preproduction-stage.srv.releng.scl3.mozilla.com redis01.build.scl1.mozilla.com buildapi01.build.scl1.mozilla.com
(ironically I'm in the midst of a project to move -to- KVM/OpenStack...)
Depends on: 939930
Depends on: 944788
Depends on: 945751
No longer depends on: 934627
Since there have been some changes since comment 10, what's left for releng is: buildapi01.build.scl1.mozilla.com dev-master01.build.scl1.mozilla.com redis01.build.scl1.mozilla.com And supporting infrastructure vms that won't be decommissioned until we move all of the slave gear out of the datacenter and close it.
buildapi01 and redis01 are idle, and will be halted soon.
remaining: dev-master01.build.scl1.mozilla.com (bug 967538)
Blocks: 961164
That's the last of the releng owned kvm vms.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.