Opened 21 months ago

#29304 new project

Manage the lifecycle of systems

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


During the sysadmin meeting in Brussels we discussed our infrastructure. Systems are managed by service admins/owners. They sometimes disappear or services become irrelevant. This means we have systems without proper owner which are rotting over time.

To better handle such systems we decided that systems like $ should have an expiration date which is initially one or two years in the future. When the expiration date is near the service owner receives an email informing about the possible shutdown and the means to prevent it (write an email answer to tpa). If the mail is answered the expiration date will be prolonged. If not, the system will be deactivated. The deactivation can easily be revoked. However after some more time without any feedback the host will be decommissioned.

This ticket is to track the several steps for implementing this new policy.

Child Tickets

#29305newtpaAdapt LDAP to have expiration date and unix groupsInternal Services/Tor Sysadmin Team
#29306assignedweaselWrite a script to mail people informing them about expiration of their serviceInternal Services/Tor Sysadmin Team
#29379newtpaMaybe shut down VM's automatically when they expire?Internal Services/Tor Sysadmin Team
#29380newtpaLink to db.tpo from infrastructure page, for service expiration datesInternal Services/Tor Sysadmin Team
#29381newtpaAdd to LDAP expiration date and list of "stakeholders"Internal Services/Tor Sysadmin Team
#29385assignedweaselAdapt LDAP scripts to honour expiration datesInternal Services/Tor Sysadmin Team
#29386assignedweaselImplement and deploy script for spamming people about account, group and host expirationInternal Services/Tor Sysadmin Team
#30273newtpaimprove inventory of hardware resourcesInternal Services/Tor Sysadmin Team

Change History (0)

Note: See TracTickets for help on using tickets.