----- Original Message ----- > From: "Dan Callaghan" <dcall...@redhat.com> > To: "beaker-devel" <beaker-devel@lists.fedorahosted.org> > Sent: Monday, May 4, 2015 3:39:28 PM > Subject: Re: [Beaker-devel] Simplify inventorying systems in Beaker > > Excerpts from Nick Coghlan's message of 2015-05-04 15:33 +10:00: > > One thing that did occur to me is that it's likely desirable to use > > the > > latest *released* version of the relevant family, rather than the latest > > version available (since the latter might be a testing tree). > > Yes that's true, the filter criterion should be > > <distro_arch value="$thearch"/> > <distro_family value="$selectedfamily"/> > <distro_tag value="RELEASED"/> > > which reminds me that the logic also needs to pick a preferred arch when > the system supports multiple arches (should prefer 64-bit over > 32-bit/31-bit, and for PPC prefer big-endian). > > And it also needs to handle systems which don't support *any* > RHEL/CentOS/Fedora but only a RHEL-alike under a different name. For > example the internal-only aarch64 product. > > Also note that in those cases, there will probably be no RELEASED trees. > Also note that RELEASED is done by hand by admins nowadays so a fresh > Beaker installation may not have any trees with that tag. Therefore if > there are no trees in the family tagged RELEASED, it should just use the > latest available tree.
Thanks for the suggestions and comments. I have some code which now implements the above: http://fpaste.org/218852/30883888/ As far as my tests tell me, i think this does what we want as far as distro selection is concerned. The exception is for distros which are RHEL like but has a different name. I will think about it. -- Amit Saha <http://echorand.me> PnT DevOps - Developer Red Hat, Inc. _______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
