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.

Sign up for GitHub

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

Jump to bottom

A central operational documentation #2539

Open
7 tasks
fridex opened this issue Apr 29, 2022 · 3 comments
Open
7 tasks

A central operational documentation #2539

fridex opened this issue Apr 29, 2022 · 3 comments
Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Apr 29, 2022

Is your feature request related to a problem? Please describe.

As Thoth's deployment and resolver is starting to be large, it might be a good idea to provide a central place that would document what to do when. This documentation would be more "operational" centric and could state things that need to be done on certain events. For instance:

  • purging and updating database entries for new and old environments
  • adding new solvers to support environments (also monitoring new Fedora and UBI/RHEL releases)
  • database updates and migration across deployments
  • updating TensorFlow API as aggregated by tensorflow-symbols on a new TensorFlow release
  • releasing prescriptions and propagating them with a new adviser release to deployments
  • adjusting solver rules - ex. now we block packages that are older than 2016 and do not occur in any application our consumers use
  • ...

Some of these docs already exist, it might be a good idea to have them in one central place (or at least link them from one central place).
@fridex fridex added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 29, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Apr 29, 2022
@goern
Copy link
Member

goern commented May 2, 2022

/sig devsecops

@sesheta sesheta added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label May 2, 2022
@goern
Copy link
Member

goern commented May 16, 2022

/priority critical-urgent

@sesheta sesheta added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label May 16, 2022
@harshad16
Copy link
Member

/triage accepted
/lifecycle frozen
/area documentation

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on. area/documentation Issues or PRs related to documentation, tutorials, examples, ... and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jun 6, 2022
@VannTen VannTen mentioned this issue Jul 19, 2022
Open
@harshad16 harshad16 moved this to New in SIG-DevSecOps Sep 22, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 🆕 New
SIG-DevSecOps
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @fridex @harshad16 @sesheta