<div dir="ltr">I have to be able to find all of them (including the tested directory) when I am checking which package version is available for OST for example. Nothing there is CI only, developers need all of them when bug is found by those systems and investigation is needed.<div><br></div><div>Guys, we need to know how CI works, what packages it consumes and how we can reproduce a test to be able to solve bugs found by CI.</div><div><br></div><div>Martin</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri <span dir="ltr"><<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I just noticed we have couple of different places for the same kind of<br>
content (packages):<br>
<br>
/pub/ - includes new releases and snapshots repos<br></blockquote><div><br></div></span><div>This is the official place for oVirt releases and what any user should use.</div><div>The official repositories </div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
/repos/ovirt/{experimental,tes<wbr>ted}/ - experimental seems pretty close<br>
to snapshots<br></blockquote><div><br></div></span><div>Experimental - internal repo for CI, no one should use it.</div><div>Tested - official verified repos with packages that passed OST, we recommend anyone to use that repo if he wants latest and greatest packages and can't wait to an official release</div><div>Snapshots - from next week, ovirt-snapshot-master will be a nightly snapshot of tested repo, this is ideal for QE or anyone who wants to test oVirt, but can't have the repo refreshed all the time. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
/releases - old releases<br></blockquote><div><br></div><div>We don't maintain this, probably kept for history purposes </div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The /repos prefix by itself is incredibly messy, there are bunch of<br>
private directories and ovirt among them.<br></blockquote><div><br></div></span><div>Please open a ticket on <a href="http://jira.ovirt.org" target="_blank">jira.ovirt.org</a> with details and we'll look into it, but I don't think that each directory on a release server should matter.</div><div>There is official documentation for oVirt users and release rpms which provides you with exactly which repos you should use.</div><div><br></div><div>We do need to add documentation on what each repo means and its usage, can you please open a ticket on it so we won't forget?</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Can you please unify the structure so it is easier to navigate? We<br>
should at least have one top level dir for all official public<br></blockquote><div><br></div><div> </div></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
content.<br>
<br>
Something like<br>
<br>
/ovirt/{releases,experimental,<wbr>tested}/<version>/<arch><br>
<br>
and<br>
<br>
/ovirt/yum-repos/release.rpm<br>
<br>
would work well enough I think.<br>
<br>
Thanks<br>
<br>
Martin<br></span>
______________________________<wbr>_________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org" target="_blank">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/infra</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="m_5848713317278098918gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><p style="font-family:overpass,sans-serif;margin:0px;padding:0px;font-size:14px;text-transform:uppercase;font-weight:bold"><font color="#cc0000">Eyal edri</font></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><br></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">ASSOCIATE MANAGER</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">RHV DevOps</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">EMEA VIRTUALIZATION R&D</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><br></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat EMEA</a></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png" width="90" height="auto"></a></td><td style="font-size:10px"><a href="https://redhat.com/trusted" style="color:rgb(204,0,0);font-weight:bold" target="_blank">TRIED. TESTED. TRUSTED.</a></td></tr></tbody></table></div><div>phone: <a href="tel:+972%209-769-2018" value="+97297692018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div></div></div>
</div></div>
</blockquote></div><br></div>