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

O+M 2024-07-29 #4828

Closed
5 of 14 tasks
hkdctol opened this issue Jul 24, 2024 · 2 comments
Closed
5 of 14 tasks

O+M 2024-07-29 #4828

hkdctol opened this issue Jul 24, 2024 · 2 comments
Assignees
Labels
O&M Operations and maintenance tasks for the Data.gov platform

Comments

@hkdctol
Copy link
Contributor

hkdctol commented Jul 24, 2024

As part of day-to-day operation of Data.gov, there are many Operation and Maintenance (O&M) responsibilities. Instead of having the entire team watching notifications and risking some notifications slipping through the cracks, we have created an O&M Triage role. One person on the team is assigned the Triage role which rotates each sprint. This is not meant to be a 24/7 responsibility, only East Coast business hours. If you are unavailable, please note when you will be unavailable in Slack and ask for someone to take on the role for that time.

Check the O&M Rotation Schedule for future planning.

Acceptance criteria

You are responsible for all O&M responsibilities this week. We've highlighted a few so they're not forgotten. You can copy each checklist into your daily report.

Daily Checklist

Note: Catalog Auto Tasks
You will need to update the chart values manually. Click the Action link in each issue and grab the values from monitor task output and check runtime.

Weekly Checklist

Monthly Checklist

ad-hoc checklist

  • audit/review applications on cloud foundry and determine what can be stopped and/or deleted.

Reference

@hkdctol hkdctol moved this to 📟 Sprint Backlog [7] in data.gov team board Jul 24, 2024
@hkdctol hkdctol added the O&M Operations and maintenance tasks for the Data.gov platform label Jul 24, 2024
@rshewitt rshewitt moved this from 📟 Sprint Backlog [7] to 🏗 In Progress [8] in data.gov team board Jul 29, 2024
@rshewitt
Copy link
Contributor

rshewitt commented Jul 30, 2024

cypress test checking for feedback button visibility on catalog on commit keeps failing. looks good in prod. will keep an eye on it.

Image

update. commit here seems to have fixed the issue. commit badge for catalog is passing.

@rshewitt
Copy link
Contributor

there's some critical vulnerabilities with the python 3.10 base image we use in harvesting logic. looks like all the alternatives have at least 1 critical error. the dockerfile is only used for local development so probably not a big priority

Image

@Jin-Sun-tts Jin-Sun-tts moved this from 🏗 In Progress [8] to ✔ Done in data.gov team board Aug 5, 2024
@Bagesary Bagesary moved this from ✔ Done to 🗄 Closed in data.gov team board Aug 9, 2024
@github-project-automation github-project-automation bot moved this from 🗄 Closed to ✔ Done in data.gov team board Sep 3, 2024
@btylerburton btylerburton moved this from ✔ Done to 🗄 Closed in data.gov team board Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O&M Operations and maintenance tasks for the Data.gov platform
Projects
Archived in project
Development

No branches or pull requests

3 participants