Tue, May 16, 2017 at 09:48:37AM CEST, olichtne(a)redhat.com wrote:
On Mon, May 15, 2017 at 05:28:30PM +0200, Jiri Pirko wrote:
> Thu, May 11, 2017 at 02:41:10PM CEST, olichtne(a)redhat.com wrote:
> >From: Ondrej Lichtner <olichtne(a)redhat.com>
> >
> >Defines the MachineMapper class. Implements a matching algorithm that
> >maps requirements to available hosts. In this specific class this is
> >implemented with backtracking, however testers are free to implement
>
> If you talk about tester, do I understand it correctly you are talking
> about person acually writing a recipe?
>
> If that is the case, how can I impelement my own matching? I have to be
> missing something. Examples would help.
>
Yeah, this is possible by implementing your own Mapper class and
providing it to the Controller constructor as an argument. For this to
work it'll need to implement the correct interface. Which I haven't
properly defined yet - the mapper interface is just part of the problem,
the second part is the SlavePoolManager interface and the interaction
between them. I want to extract abstract classes of those two to define
the interface and properly document it so that the tester has the option
to implement his own thing.
So at this point the tester kind of has the option to do this, but I'd
say it's not supported yet and this 'API' is yet to be exported to the
tester.
I'll adjust the docstring to indicate this and avoid confusion.
okay