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

Outage tasks for 2023-01-12 #811

Closed
9 tasks done
kltm opened this issue Dec 14, 2022 · 4 comments
Closed
9 tasks done

Outage tasks for 2023-01-12 #811

kltm opened this issue Dec 14, 2022 · 4 comments

Comments

@kltm
Copy link
Member

kltm commented Dec 14, 2022

  • Send reminder email to go-consortium mailing list
  • Run noctua-models-migration pipeline for @vanaukenk (day before? morning of?) to get report
    http://skyhook.berkeleybop.org/noctua-models-migrations/reports/
  • Refresh minerva code with latest from minerva master
  • Run replaced_by term update on blazegraph (@vanaukenk)
  • Cycle minerva to get latest ontology
  • Cycle minerva dev to get latest ontology
  • Cycle noctua dev to get latest relations cache
  • Update NEO
  • Prep ticket for next outage
@vanaukenk
Copy link

@kltm - following up from today's managers call, just a note that we will also cycle noctua-dev on tomorrow's outage.
Thx.

@kltm
Copy link
Member Author

kltm commented Jan 11, 2023

@vanaukenk Added above.

@kltm
Copy link
Member Author

kltm commented Jan 11, 2023

@vanaukenk Diff now available.

@vanaukenk
Copy link

Checked the diff; all changes make sense in light of recent GO ontology work.

@kltm kltm moved this from TODO to Working in Ongoing data QC and pipeline maintenance Jan 12, 2023
@kltm kltm closed this as completed Jan 13, 2023
@kltm kltm changed the title Outage tasks for 2022-01-12 Outage tasks for 2023-01-12 Jan 25, 2023
@kltm kltm moved this from Working to Done in Ongoing data QC and pipeline maintenance Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants