Optimize GitHub + Gitea Dynamics for Ops+Devs #107

New Issue

mik-tf · 2024-10-11T17:13:10Z

mik-tf commented

2024-10-11 17:13:10 +00:00

Situation

TF as an organization uses currently GitHub (threefoldtech, threefoldfoundation) and Gitea (git.ourworld.tf, tfgrid, etc.) for hosting git repos.
There are ongoing work to make sure the work between the platforms is effortless
- #81
Currently, processes are highly streamlined and clearly defined for GitHub work, e.g. ops and devs managing the grid stack
Currently, Gitea management is working correctly but can be improved

Specs

Ops should have proper access to manage Gitea as they have currently with github, @sabrinasadik
The process should ensure that we avoid duplicates between GH and Gitea issues
The gitea instance should have redundant instances and sufficient backups
- Currently, we have 1 server hosting the website and we do regular backups
- See this issue for ideas on how to make redundant deployments
Monitor gitea instances health and have procedures+escalation matrix when issues arise (e.g. site goes down)
- Use the tools and procedures developed for 99.9% uptime project (see issue here)
- Know who manage/supervise the gitea instances health
  - main supervisor
  - 2nd supervisor if main supervisor is unavailable
- If supervisors can't fix, escalate to Ops leader

References

As discussed in meetings. Anything else missing in this Story? It can be turned into smaller stories too.

# Situation - TF as an organization uses currently GitHub (threefoldtech, threefoldfoundation) and Gitea (git.ourworld.tf, tfgrid, etc.) for hosting git repos. - There are ongoing work to make sure the work between the platforms is effortless - https://git.ourworld.tf/tfgrid/circle_engineering/issues/81 - Currently, processes are highly streamlined and clearly defined for GitHub work, e.g. ops and devs managing the grid stack - Currently, Gitea management is working correctly but can be improved # Specs - Ops should have proper access to manage Gitea as they have currently with github, @sabrinasadik - The process should ensure that we avoid duplicates between GH and Gitea issues - The gitea instance should have redundant instances and sufficient backups - Currently, we have 1 server hosting the website and we do regular backups - See this [issue](https://git.ourworld.tf/tfgrid/circle_engineering/issues/96) for ideas on how to make redundant deployments - Monitor gitea instances health and have procedures+escalation matrix when issues arise (e.g. site goes down) - Use the tools and procedures developed for 99.9% uptime project (see issue [here](https://git.ourworld.tf/tfgrid/circle_engineering/issues/74)) - Know who manage/supervise the gitea instances health - main supervisor - 2nd supervisor if main supervisor is unavailable - If supervisors can't fix, escalate to Ops leader # References - As discussed in meetings. Anything else missing in this Story? It can be turned into smaller stories too.

mik-tf added the

Story

label 2024-10-11 17:13:10 +00:00

mik-tf added this to the tfgrid_3_17 project 2024-10-11 17:13:10 +00:00

Sign in to join this conversation.