Post-Heroku timeline (OBSOLETE)

Owned by Eddie Rubeiz
Last updated: Oct 18, 2022
1 min read

Short term

In the week or so after moving to Heroku:

  • Save the final config/local_env.rb files for staging and prod to a secure area on the P drive, for short-term reference.

  • Stop all the scihist_digicoll s3 instances. Do not delete them yet:

    • we can still switch back to them in the event of a major problem

    • we want them on hand for reference in the short term.

  • Turn off update cron jobs from the Management server

  • Continue to resolve post-launch problems with Heroku

  • Remove all ec2 snapshots and unused AMIs

  • Get Ansible ArchivesSpace build working again from our development machines (PR)

  • Remove Voices in Biotech code from Ansible (PR)

Medium term (mid-August)

Once Heroku has been stable for 4 to 6 weeks:

  • Remove

    • All the scihist_digicoll boxes (yes, actually terminate the ec2 instances)

    • Management server (ditto: terminate)

    • The elastic IP addresses digicoll-staging and digicoll-production

    • All volumes that are not in use

    • Unnecessary playbooks and roles from Ansible.

    • All capistrano code and documentation from the GitHub codebase

  • Keep

    • ArchivesSpace servers - staging and production

    • Anything in Ansible required to build the ArchivesSpace servers. The rest of Ansible can go away.

  • Review, in collaboration with Chuck and Vince

    • Security groups.

    • Reserved instances

Long term

  • Once Ansible codebase is simplified, move its contents to a new, private GitHub repository.

  • Use Terraform instead of Ansible to maintain our s3 configuration.

  • Once Sarah Newhouse is settled, invite her to convene ArchivesSpace stakeholders to discuss the future of the server and its functions.

See also

Supporting information about our post-Heroku options for aws, ArchivesSpace and Ansible.