Task Scheduling for depcheck

Tim Flink tflink at redhat.com
Thu May 22 19:36:24 UTC 2014

On Tue, 06 May 2014 13:10:25 +1000
Nick Coghlan <ncoghlan at redhat.com> wrote:

> Hash: SHA1
> On 05/06/2014 01:11 AM, Tim Flink wrote:
> > We will probably need a method for selecting the type of client
> > used for tasks at some point, yes. At the moment, I don't think we
> > need to worry about it, though. None of the current tasks require
> > specific fedora releases and unless I'm mistaken, there are no
> > runtime arch requirements, either - every task could be run on
> > x86_64 regardless of what we're checking against.
> It's also the case that once you hit that level of complexity, it's
> probably worth adding another layer to the onion and handing off from
> Taskotron to Beaker, rather than building a new hardware inventory
> system.

While I'm not looking to duplicate Beaker's ability to do hardware
provisioning, I do suspect that there is going to be a little
duplication of functionality here.

If we ever want get really detailed (to the point of saying "give me a
machine with Fedora 21 Alpha TC3"), it's a bit silly to duplicate all
that work between the two systems. That being said, I think it will
depend on how specific we want to get and what additional
complexity/overhead would be required for delegation to beaker vs.
doing it in Taskotron.

I'm not dismissing the idea, it's just one of those "cross that bridge
if/when we get there" kind of things. We've got enough work to do
without reinventing wheels that we don't have to :)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/qa-devel/attachments/20140522/28564dff/attachment.sig>

More information about the qa-devel mailing list