Well, the plugin that barak passed before, the one that forces a slave
to be used only once, is what openstack guys use, in combination with
nodepool, a big python service to provision/manage slaves, that's what
I wanted to avoid, that extra service (as a jenkins job or not) to
exclusively handle slaves, when we already have the ovirt pool stuff


Than sounds like we need to review the plugins available. I believe there should be something. At least we cannot do that without any orchestrator and since we do not want to introduce a new service - jenkins master its the ideal place for it. If there is nothing available we should write it. This will be technically the best solution.

--
Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat