Closed Bug 863275 Opened 11 years ago Closed 11 years ago

decommission old puppet servers

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: dustin)

References

Details

The following host needs to move off of kvm in scl3:

scl3-production-puppet.srv.releng.scl3.mozilla.com

Likely the better route is to convert the machines in scl3 that use it over to using puppetagain.  This includes:

* The few remaining bld-centos5 vmware vms (which are slated to be decommissioned)
* dev-stage01.srv.releng.scl3.mozilla.com (which is slated for replacement)
* preproduction-stage.srv.releng.scl3.mozilla.com (which should also be slated for replacement as well as dev-stage01 since we're re-architecting the product delivery chain).
* bld-lion-r5-* which we've been discussing dissecting and redoing the image of since we have no way to modify the image as things stand now
Puppet on scl3-production-puppet is now disabled, so likely we can consider this done.  The host is still running in case we need it.
bld-lion-r5-* is now using the puppet 3.x servers.
bld-centos5 vmware vms are unmanaged
dev-stage01.srv.releng.scl3.mozilla.com is unmanaged
preproduction-stage.srv.releng.scl3.mozilla.com is unmanaged

We should set a date to delete this server.  Does it have any needed information on it that's not already in hg?
Summary: move scl3-production-puppet.srv.releng.scl3.mozilla.com off of kvm or change scl3 hosts to use puppetagain → decommission scl3-production-puppet.srv.releng.scl3.mozilla.com
Assignee: server-ops-releng → arich
Flags: needinfo?(coop)
Answered in email: Dustin backed up the rpms, so we're good to go here.
Flags: needinfo?(coop)
Morphing this bug to be a decommissioning bug for all old puppet servers.  The following machines are now shut down and awaiting deletion.  If no problems arise, they will be deleted on 2013-07-15:

scl3-production-puppet.srv.releng.scl3.mozilla.com
staging-puppet.srv.releng.scl3.mozilla.com

scl-production-puppet.build.scl1.mozilla.com
master-puppet1.build.scl1.mozilla.com

releng-puppet1.build.mtv1.mozilla.com
mv-production-puppet
Summary: decommission scl3-production-puppet.srv.releng.scl3.mozilla.com → decommission old puppet servers
Blocks: 884472
For the record: I backed up /N and /etc/puppet on all of the old production masters.  There's nothing to back up on releng-puppet1.build.mtv1 (I was just lazy and didn't delete it).
Assignee: arich → dustin
And I'd like to leave scl-production-puppet turned off but not deleted until KVM dies, in case it can be useful in restoring an r3 refimage.
Component: Server Operations: RelEng → RelOps: Puppet
Product: mozilla.org → Infrastructure & Operations
QA Contact: arich → dustin
(In reply to Amy Rich [:arich] [:arr] from comment #4)
> Morphing this bug to be a decommissioning bug for all old puppet servers. 
> The following machines are now shut down and awaiting deletion.  If no
> problems arise, they will be deleted on 2013-07-15:
> 
> scl3-production-puppet.srv.releng.scl3.mozilla.com
removed, DNS/inventory deleted

> staging-puppet.srv.releng.scl3.mozilla.com
removed, DNS/inventory deleted

> scl-production-puppet.build.scl1.mozilla.com
stopped (this can just die with the KVM servers when scl1 goes away)

> master-puppet1.build.scl1.mozilla.com
removed, DNS/inventory deleted

> releng-puppet1.build.mtv1.mozilla.com
DNS/inventory deleted

> mv-production-puppet
removed, DNS/inventory deleted
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.