resources.ovirt.org directory layout is a mess
Hi, I just noticed we have couple of different places for the same kind of content (packages): /pub/ - includes new releases and snapshots repos /repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots /releases - old releases The /repos prefix by itself is incredibly messy, there are bunch of private directories and ovirt among them. Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public content. Something like /ovirt/{releases,experimental,tested}/<version>/<arch> and /ovirt/yum-repos/release.rpm would work well enough I think. Thanks Martin
On 28 March 2017 at 12:15, Martin Sivak <msivak@redhat.com> wrote:
Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public content.
'/pub' is that place. '/repos/ovirt/tested' should only concern you if you want to write jobs that need to pull in post-OST dependencies. I guess we could do a better job of documenting which repo to use when. '/repos/ovirt/experimental' should only ever be used by stuff that is running within the experimental flow. If you see anything that links to it directly its a bug. I do agree we probably need to clean older unused stuff from '/repos'.
Hi, On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak <msivak@redhat.com> wrote:
Hi,
I just noticed we have couple of different places for the same kind of content (packages):
/pub/ - includes new releases and snapshots repos
This is the official place for oVirt releases and what any user should use. The official repositories
/repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots
Experimental - internal repo for CI, no one should use it. 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 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.
/releases - old releases
We don't maintain this, probably kept for history purposes
The /repos prefix by itself is incredibly messy, there are bunch of private directories and ovirt among them.
Please open a ticket on jira.ovirt.org with details and we'll look into it, but I don't think that each directory on a release server should matter. There is official documentation for oVirt users and release rpms which provides you with exactly which repos you should use. 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?
Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public
content.
Something like
/ovirt/{releases,experimental,tested}/<version>/<arch>
and
/ovirt/yum-repos/release.rpm
would work well enough I think.
Thanks
Martin _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
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. 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. Martin On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri <eedri@redhat.com> wrote:
Hi,
On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak <msivak@redhat.com> wrote:
Hi,
I just noticed we have couple of different places for the same kind of content (packages):
/pub/ - includes new releases and snapshots repos
This is the official place for oVirt releases and what any user should use. The official repositories
/repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots
Experimental - internal repo for CI, no one should use it. 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 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.
/releases - old releases
We don't maintain this, probably kept for history purposes
The /repos prefix by itself is incredibly messy, there are bunch of private directories and ovirt among them.
Please open a ticket on jira.ovirt.org with details and we'll look into it, but I don't think that each directory on a release server should matter. There is official documentation for oVirt users and release rpms which provides you with exactly which repos you should use.
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?
Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public
content.
Something like
/ovirt/{releases,experimental,tested}/<version>/<arch>
and
/ovirt/yum-repos/release.rpm
would work well enough I think.
Thanks
Martin _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)
On 28 March 2017 at 12:46, Martin Sivak <msivak@redhat.com> wrote:
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.
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.
This is a different request, and has nothing to do with the structure of resources.ovirt.org. The experimental flow can and does take packages directly from build artifacts jobs. It uses the 'repos/ovirt' directory as a composition space but that is just an aspect of the current implementation and will change. I agree we can do a better job of documenting how the experimental flow works. I'm afraid the way the flow works currently does not allow for easy exact repoduction because the exact tested composition only exists in 'latest.under_test' for the duration of the test (Its not hard to tell which packages were tested mind you, but building a usable repo with those exact packages will take some work). But this is indeed something we might look at as a future tooling design goal. I think that for most practical purposes, you probably don't need 100% exact reproduction. Running the manual OST job against the 'tested' repo (This is the default configuration for 'master' and can be selected for other releases), or running it locally, while adding a few extra packages via direct URLs in the extra_sources file probably allows reproducing most issues. -- Barak Korren bkorren@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/
On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri <eedri@redhat.com> wrote:
Hi,
On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak <msivak@redhat.com> wrote:
Hi,
I just noticed we have couple of different places for the same kind of content (packages):
/pub/ - includes new releases and snapshots repos
This is the official place for oVirt releases and what any user should use. The official repositories
/repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots
Experimental - internal repo for CI, no one should use it. 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
If it's now official, please move it to /pub. /repos is not meant to be used for official public content. /repos was meant to host internal, development, temporary, backup repos.
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.
/releases - old releases
We don't maintain this, probably kept for history purposes
The /repos prefix by itself is incredibly messy, there are bunch of private directories and ovirt among them.
Please open a ticket on jira.ovirt.org with details and we'll look into it, but I don't think that each directory on a release server should matter. There is official documentation for oVirt users and release rpms which provides you with exactly which repos you should use.
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?
Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public
content.
Something like
/ovirt/{releases,experimental,tested}/<version>/<arch>
and
/ovirt/yum-repos/release.rpm
would work well enough I think.
Thanks
Martin _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)
-- 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>
On 28 March 2017 at 14:21, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri <eedri@redhat.com> wrote:
Hi,
On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak <msivak@redhat.com> wrote:
Hi,
I just noticed we have couple of different places for the same kind of content (packages):
/pub/ - includes new releases and snapshots repos
This is the official place for oVirt releases and what any user should use. The official repositories
/repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots
Experimental - internal repo for CI, no one should use it. 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
If it's now official, please move it to /pub. /repos is not meant to be used for official public content. /repos was meant to host internal, development, temporary, backup repos.
I guess the description Eyal gave was misleading. The "official" cutting edge releases were and remain in the nightly "snapshot" repos under "/pub". "tested" is for use by processes that cannot wait for the nightly publishing job and needs the latest stuff that passed OST (This means most CI processes, but probably not user processes). -- Barak Korren bkorren@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/
participants (4)
-
Barak Korren -
Eyal Edri -
Martin Sivak -
Sandro Bonazzola