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

Create lightweight database dumps for testing purposes #2648

Open
mayaCostantini opened this issue Jun 9, 2022 · 4 comments
Open

Create lightweight database dumps for testing purposes #2648

mayaCostantini opened this issue Jun 9, 2022 · 4 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps.

Comments

@mayaCostantini
Copy link
Contributor

Problem statement

As a developer of Thoth, I would like to test components using a local database instance without having to consume too many resources on my machine.
The current database backups generated in ocp4-stage/graph-backup/ are currently more than 11GiB, which represents a lot of memory resources to allocate and of overhead for loading tables and writing WALs.

Proposal description

Generate database backups for testing purposes with a limited number of entries in the tables containing the more entries, and where the risk of having missing entries would not disrupt too much the testing of components querying the database.

@mayaCostantini mayaCostantini added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 9, 2022
@mayaCostantini
Copy link
Contributor Author

/priority important-soon
/sig devsecops

@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. labels Jun 9, 2022
@mayaCostantini
Copy link
Contributor Author

/good-first-issue

@sesheta
Copy link
Member

sesheta commented Jun 9, 2022

@mayaCostantini:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jun 9, 2022
@sesheta
Copy link
Member

sesheta commented Sep 7, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2022
@mayaCostantini mayaCostantini removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps.
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants