Opened 4 months ago

Last modified 4 months ago

#31686 new project

retire textile

Reported by: anarcat Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


textile is one of the first machines in the KVM* series. weasel proposed we move all its VM into the new FSN cluster and retire the box to start saving some money, and eventually grow the cluster.

Child Tickets

#17202assignedShut down SVN and decomission the host (gayi)Internal Services/Tor Sysadmin Team
#29399newtpaRetire host and services for tordnsel and check (chiwui)Internal Services/Tor Sysadmin Team
#31676closedweaseldecommission togashiiInternal Services/Tor Sysadmin Team
#31700closedanarcatdecomission jabber serverInternal Services/Service - jabber
#32281closedanarcatset up new IRC box to replace iranicumInternal Services/Tor Sysadmin Team

Change History (6)

comment:1 Changed 4 months ago by anarcat

i'm all for making use of the new cluster, but I'm thinking that we should also keep space on the fsn* cluster to alleviate the load on kvm4, which is suffering a bit.

i'd also like to move the bacula director off of moly, which i distrust, see also #29974.

Last edited 4 months ago by anarcat (previous) (diff)

comment:2 Changed 4 months ago by anarcat

one of those machines is chamaemoly, which will be decommissioned altogether and shouldn't be migrated, see #31700.

comment:3 Changed 4 months ago by anarcat

it's actually one two three four (!) machines that are are to eventually be retired so we shouldn't migrate those either:

this leaves us with only those machines to migrate before textile can be decommissioned, yaay!
	 - shell/irc box
	 - static content rotation
	 - Windows buildbox
	 - Windows buildbox
Last edited 4 months ago by anarcat (previous) (diff)

comment:4 Changed 4 months ago by weasel

derotated saxatile

comment:5 Changed 4 months ago by weasel

windows VMs moved to kvm4. (winklerianum is not defined in virsh, but the data is there)

comment:6 Changed 4 months ago by anarcat

saxatile removed from ldap, disks queued for removal in 7 days, removed from puppet, nothing left in DNS, entry removed from spreadsheet, nagios, tor-passwords, and scheduled backup deletion in 30 days.

saxatile is done.

Note: See TracTickets for help on using tickets.