TPA team issueshttps://gitlab.torproject.org/tpo/tpa/team/-/issues2022-05-03T17:45:36Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/29305Adapt LDAP to have expiration date and unix groups2022-05-03T17:45:36ZJens KubiezielAdapt LDAP to have expiration date and unix groupsLDAP needs more fields which track the expiration time and has the unix groups for stakeholders. weasel agreed to extend LDAP.
Furthermore someone needs to go over LDAP and add information about the stakeholders plus an expiration date.LDAP needs more fields which track the expiration time and has the unix groups for stakeholders. weasel agreed to extend LDAP.
Furthermore someone needs to go over LDAP and add information about the stakeholders plus an expiration date.https://gitlab.torproject.org/tpo/tpa/team/-/issues/29304Manage the lifecycle of systems2022-12-20T19:25:37ZJens KubiezielManage the lifecycle of systemsDuring 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 rott...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 `$host.torproject.org` 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.