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

Make all migrations / ontology maintenance run automatically #547

Open
kltm opened this issue Jul 26, 2024 · 1 comment
Open

Make all migrations / ontology maintenance run automatically #547

kltm opened this issue Jul 26, 2024 · 1 comment

Comments

@kltm
Copy link
Member

kltm commented Jul 26, 2024

This is likely a "bigger" ticket, but I wanted to add this as a conversation point.

Since June 2021, we have been doing a periodic manual ontology update in minerva. This procedure currently requires two people, a pre-coordinated and publically communicated time, and around 2hrs. To date, it has been done around 64 times.

Additionally, given the manual nature and the fact that this is a high-value production system, when things do inevitably go wrong, we need to be cautious, sometimes leading to longer outages, redos, and general stress; e.g.:

Finally, given that this is a production system, we try to do outages when things are "quite", typically meaning that we are encroaching on hours that would typically be considered "off" for the people performing these tasks.

Given all this, I would propose that automation would reduce errors and time spent, at least in the long-run. There are two approaches:

  • have minerva do migrations and updates automatically and internally
  • using automation scripts, create a turnkey system where a newly migrated and updated system is brought up (and automatically tested)

Tagging @vanaukenk

@kltm
Copy link
Member Author

kltm commented Aug 24, 2024

Adding to the pile:
geneontology/noctua#912

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

No branches or pull requests

1 participant