Saturday, 2024-07-20

@fungicide:matrix.orgprobably at least some amount of the work on it would be transferable, i suppose you could at least get started on identifying the correct api calls and whatnot00:13
-@gerrit:opendev.org- Takashi Kajinami proposed: [zuul/zuul-jobs] 924057: Explicitly install public_suffix 5.1.1 https://review.opendev.org/c/zuul/zuul-jobs/+/92405704:04
@tristanc_:matrix.orgSpeaking of adding new nodepool drivers, we are using a fake kubernetes api called [k1s](https://pagure.io/software-factory/k1s) to run container workload directly with podman using the k8s driver, and I'm wondering if we could do the same for vms through a fake openstack api. The required endpoints for nodepool don't look very difficult to implement for a different backend like hetzner or libvirt.13:19
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed:17:15
- [zuul/nodepool] 924550: Fix cleanup process in AWS tests https://review.opendev.org/c/zuul/nodepool/+/924550
- [zuul/nodepool] 924551: Squash: Remove instance parameter from quota methods https://review.opendev.org/c/zuul/nodepool/+/924551
- [zuul/nodepool] 924552: Squash: Make a createLaunchTemplates method https://review.opendev.org/c/zuul/nodepool/+/924552
- [zuul/nodepool] 924553: Squash: use content-addressible name for launch template https://review.opendev.org/c/zuul/nodepool/+/924553
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Benedikt Löffler: [zuul/nodepool] 923506: Support EC2 Fleet API https://review.opendev.org/c/zuul/nodepool/+/92350617:15
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Benedikt Löffler: [zuul/nodepool] 923506: Support EC2 Fleet API https://review.opendev.org/c/zuul/nodepool/+/92350617:16
@sylvass:albinvass.setristanC: interesting 22:02
@clarkb:matrix.org> <@tristanc_:matrix.org> Speaking of adding new nodepool drivers, we are using a fake kubernetes api called [k1s](https://pagure.io/software-factory/k1s) to run container workload directly with podman using the k8s driver, and I'm wondering if we could do the same for vms through a fake openstack api. The required endpoints for nodepool don't look very difficult to implement for a different backend like hetzner or libvirt.22:23
Why not write a driver for libvirt or hetzner or podman? the driver state machine framework should make that fairly straightforward
@clarkb:matrix.orgThat to me seems less fragile and easier to maintain over time than a weird proxy layer that has to track changes on both sides of it22:23
@clarkb:matrix.org(my main concern would be anyone making changes to the k8s or openstack drivers is unlikely to be aware that you've got a proxy and could very easily break that by adding dependencies on APIs that are not implemented in the proxy)22:25
@clarkb:matrix.orgbut if you have a driver that implements things directly then updates to zuul/nodepool would be aware that driver also needs updating and you completely sidestep the changes adding dependencies on third party apis22:25
@tristanc_:matrix.orgClark: I find it is easier to develop an external api with a running nodepool service instead of integrating a new sdk/driver directly in nodepool.22:38

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!