Action plans for GitHost EOL
With the GitHost EOL coming, users are not migrating at a pace that we would like. It's possible many users are not fully aware of the EOL. Below are some suggestions/plans to get the ball rolling.
-
Create ZenDesk macro to add a "signature" at the end of all GitHost related tickets, reminding them of the EOL. -
Remove button/action that allows creation of new instances and Runners. -
Get list of contacts that have not opened EOL notification emails. -
Obtain all admin user email addresses for instances of above list. Add them to the list for May 1st email. -
Generate "exceptions" list: who is staying on after because of a long-term contract or signed (but not delivered) Professional Services SOW?
May 1
-
reminder emails.
May 15
-
place system notification banner on all instances except those who opts out.
May 31st:
-
ensure that all hosts have a backup -
remove DO API key so that new instances cannot be created -
retrieve all gitlab-secrets.json
-
shutdown all instances -
shutdown all runners
June 15th:
-
delete all instances and volumes from DO
June 31st:
-
delete all backups and gitlab-secrets.json
Edited by Lyle Kozloff