This is a multi-part message in MIME format... ------------=_1513708763-30796-235 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35521#comment-35521 ] Barak Korren commented on OVIRT-1811: ------------------------------------- We've discussed this multipile times in the past - making a package retention policy that works right and does not introduce various subtle issues is hard - and we lack the proper tooling for this (E.g. a tool that can remove any package older then X days while still keeping at least N versions of each package and also keeping enough yum MD files so that for the duration that yums keeps repomd.xml cached by default, users will never get 404 errors)
tested rpms piling up ---------------------
Key: OVIRT-1811 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1811 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra
/var/www/html/repos/ovirt/tested/master is now 351G This causes http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_night... to run for one hour downloading obsolete code. Do we have something cleaning up tested repos? If not, can we get one? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1513708763-30796-235 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1811?page=com.atlassian.jira.p... ]</pre> <h3>Barak Korren commented on OVIRT-1811:</h3> <p>We've discussed this multipile times in the past – making a package retention policy that works right and does not introduce various subtle issues is hard – and we lack the proper tooling for this (E.g. a tool that can remove any package older then X days while still keeping at least N versions of each package and also keeping enough yum MD files so that for the duration that yums keeps repomd.xml cached by default, users will never get 404 errors)</p> <blockquote><h3>tested rpms piling up</h3> <pre> Key: OVIRT-1811 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1811 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: sbonazzo Assignee: infra</pre> <p>/var/www/html/repos/ovirt/tested/master is now 351G This causes <a href="http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_nightly">http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_nightly</a> to run for one hour downloading obsolete code. Do we have something cleaning up tested repos? If not, can we get one? — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>>; <<a href="https://red.ht/sig">https://red.ht/sig</a>>; TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3t..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1513708763-30796-235--