Re: Using oVirt VM pools in oVirt infra
--5uO961YFyoDlzFnP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 01/14 11:56, Anton Marchukov wrote:
> But this is the reverse of what we need, the problem is how to
make
> the slave shut down in the first place, you can`t just do it from the
> job that used it because it will make the job fail.
>
=20
Hm. I think some hybrid option is needed. Once the job is finished we
should unlabel the slave and then use some garbage collection to kill the
used slaves. I believe this can be done using system groovy script. And I
think instead of removing labels we should just add a new one, e..g. we a=
dd
"to_be_removed" and just schedule based on slaves not
having that label.
Smth like how data are purged from the database with delete flag.
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
=20
>
> But maybe we can actually use the good old 'shutdown $TIME_DELAY' to
> make the slave shut down a few seconds after the job is done...
> I can't believe I forgot you can time delay a shut down... I was
> initially thinking of 'at' and then I remebred this...
>
=20
I do not like anything that accounts on any delays as it will rise race
condition at some point. The probability is discussable, but first we
should try to design the system without it if possible.
=20
--=20
Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
--5uO961YFyoDlzFnP
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJWl3/GAAoJEEBxx+HSYmnDqUYH/im4e3UYlV2gymtt+QweoYk2
8eSqGRwKqxQJEEKPUxlh8X/i9w0FkDDVQ0Ojau9w2u9oKLGR3yn43/MeIhqJV8n3
OP+mi4ThnNxk4F4obL+FMq7GdmOxVTIvHUt7WVI8OSn4MZb7Paa0RZ3g9rXcE/PN
bJaNMU9jBZM1Z97N7kdSuiAv349ga1HcqDMy2IX5UDbcXxo8XVRZiFtxBz8w6KBN
QIwuejG+u2xCKLOaj91cvhimoIZyx10xYdb7SnbpraqtIuAxOpWe0QOzr4UbJsdF
RKPV106ZvIY5anLsV+7qrO6Fi0ix3b5Ur3mkwOb+ZhpohrhmT4L4SJnTzYA08Jg=
=JkSn
-----END PGP SIGNATURE-----
--5uO961YFyoDlzFnP--
Attachments:
- attachment.bin (multipart/signed — 2.5 KB)