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

Move TRSS to OpenShift #1689

Open
7 tasks
aahlenst opened this issue Nov 18, 2020 · 2 comments
Open
7 tasks

Move TRSS to OpenShift #1689

aahlenst opened this issue Nov 18, 2020 · 2 comments

Comments

@aahlenst
Copy link
Contributor

In light of #1679, we should investigate moving TRSS to OpenShift which is our main platform for production applications. It already runs the API and jlink.online. Currently, TRSS is hosted on a EC2 machine at AWS in an ad-hoc fashion.

  • Investigate whether TRSS can be run on OpenShift. If not, initiate the necessary adjustments.
  • Ensure TRSS provides endpoints for health checks (indicate whether TRSS is up, MongoDB is operational).
  • Codify the deployment of OpenShift (Dockerfile, Ansible, ...).
  • Create staging environment.
  • Work out backup strategy and implement it.
  • Create production environment.
  • Monitor SSL certificate, reachability, health endpoints and resources of TRSS.
@llxia
Copy link

llxia commented Nov 18, 2020

Thanks @aahlenst Does OpenShift provide any backup support? Or is there any server we can use to back up the data?

@aahlenst
Copy link
Contributor Author

Haven't seen a "backup now" button but I'm sure we'll find a solution.

@sxa sxa added this to the Icebox / On Hold milestone Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

4 participants