Decommission figgy-edge.lib.princeton.edu

[acozine]

What maintenance needs to be done?

Decommission the figgy-edge project.

Level of urgency

• [ ] High
• [ ] Moderate
• [x] Low

Why is this maintenance needed?

When we worked on upgrading PostgreSQL for figgy, we created all-new infrastructure for testing the migration. That migration is complete, and we no longer need the infrastructure.

Acceptance criteria

• [x] all figgy-edge VMs are deleted (we do not need backups of these VMs)
• [x] all firewall objects and rules for figgy-edge are deleted (requires ServiceNow ticket)
• [x] any certificates for figgy-edge.lib.princeton.edu are revoked
• [x] any load-balancer configs or other artifacts of this project and deleted/removed

Implementation notes, if any

According to ServiceNow, the certificate expires on June 29, 2024. See also https://github.com/pulibrary/princeton_ansible/pull/4008.

[Beck-Davis]

No figgy-edge VMs found in vSphere or objects/rules in Panorama. Nothing found load-balancer Network delete requests submitted for figgy-edge Nothing found in princeton_ansible.