[devops] Increase lifetime for custom ISO build parameters
Bug #1361727 reported by
Dmitry Mescheryakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
Medium
|
Fuel DevOps | ||
Bug Description
Right now custom ISOs built with Jenkins are stored for two weeks. We have bugs filed for MOS, which were initially experienced on such ISOs. So we would like for info about ISO to be stored for longer time - three month. By 'info' I mean parameters with which build job was launched. Ideally we would like for built images to be stored for three month as well.
| Changed in fuel: | |
| importance: | Undecided → Medium |
Revision history for this message
| Aleksandra Fedorova (bookwar) wrote | #1 |
Revision history for this message
| Aleksandra Fedorova (bookwar) wrote | #2 |
| Changed in fuel: | |
| status: | New → Fix Committed |
| Changed in fuel: | |
| milestone: | none → 5.1 |
| Changed in fuel: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We have ~5 iso builds per day, each iso with tarball produces around 10 Gb of data.
There is a possibility to keep certain build info forever on request. For that there is a 'Keep this build forever' button on the build page. We can also increase the time to three months in general.
But I'd like to discuss the workflow which leads to the bugs filed for three months old ISO builds. How those iso appear, by which criteria they can be chosen and why version.yaml and diagnostic snapshot don't provide enough info on them.