Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decommission OJS #5752

Closed
8 tasks done
kelynch opened this issue Jan 16, 2025 · 3 comments · Fixed by #5758
Closed
8 tasks done

Decommission OJS #5752

kelynch opened this issue Jan 16, 2025 · 3 comments · Fixed by #5758
Assignees

Comments

@kelynch
Copy link
Contributor

kelynch commented Jan 16, 2025

What maintenance needs to be done?

Decommission ojs-prod{1,2}.princeton.edu and ojs-staging{1,2}.princeton.edu.

Why is this maintenance needed?

Open Publishing, previously under development as an OJS site, has been replaced with Manifold. Note that https://openpublishing.princeton.edu/ now points to the Manifold instance.

Acceptance criteria

  • These VMs are not referenced in load balancer configurations
  • These VMs are not in the inventory
  • delete ojs-prod1.princeton.edu vm
  • delete ojs-prod2.princeton.edu vm
  • delete ojs-staging1.princeton.edu vm
  • delete ojs-staging2.princeton.edu vm
  • delete DNS for the VMs
  • delete firewall rules
@dphillips-39
Copy link
Contributor

dphillips-39 commented Jan 16, 2025

Action Taken:

  • Disconnected servers (VMs - ojs-prod1, ojs-staging2) from the network for 30 days.
  • Powered down the VMs as part of the disconnection process.

Next Steps:

  • Plan to delete the VMs from disk after the 30-day period.

@kayiwa
Copy link
Member

kayiwa commented Jan 16, 2025

Image

Please add closing the noisy alerts

@kayiwa
Copy link
Member

kayiwa commented Jan 16, 2025

we do not need to hold these for 30 days. They were barely used and has effectively been unused all fall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants