| @amberdev:matrix.org | Hi all. I'm trying to follow quick-start. Could it be that `zuul-ci/zuul-executor` image does not contain `ansible-playbook` executable by default? | 09:56 |
|---|---|---|
| @amberdev:matrix.org | I am aiming to convert docker-compose.yaml into Podman deployment.yaml. | 09:58 |
| @amberdev:matrix.org | Also, when you look at https://quay.io/repository/zuul-ci/zuul-executor?tab=info it is not clear where does the corresponding `Containerfile` is located. | 10:04 |
| @fungicide:matrix.org | > <@amberdev:matrix.org> Hi all. I'm trying to follow quick-start. Could it be that `zuul-ci/zuul-executor` image does not contain `ansible-playbook` executable by default? | 12:20 |
| the dockerfile runs the zuul-manage-ansible command to build the relevant ansible venv(s) in the image: https://opendev.org/zuul/zuul/src/branch/master/Dockerfile#L43 | ||
| @fungicide:matrix.org | the command is described here in the docs: https://zuul-ci.org/docs/zuul/latest/installation.html#executor-deployment | 12:20 |
| @fungicide:matrix.org | > <@amberdev:matrix.org> I am aiming to convert docker-compose.yaml into Podman deployment.yaml. | 12:21 |
| reviews welcome on https://review.opendev.org/687135 | ||
| @fungicide:matrix.org | there's a series of changes, and ongoing work to figure out solutions for the various functional differences between docker-compose and podman-compose | 12:22 |
| @amberdev:matrix.org | Oh... interesting. | 12:23 |
| @fungicide:matrix.org | collaborating on that would probably be more efficient that retreading the same ground | 12:23 |
| @amberdev:matrix.org | I'm new in all this, so i'm actively doing my own "research". I just finished Quay, Keycloak and Gerrit setup behind the HAProxy and now trying to get into Zuul. | 12:24 |
| @fungicide:matrix.org | yeah, there had been prior interest in better podman support, but very recently we discovered that the model we'd conceived for speculative container image builds relied on a rather insidious vendor lock-in baked into the docker client. basically it only allows fallback from mirrors to dockerhub, not to any other container registry. we found that out the hard way when we moved images to quay and were suddenly not testing the container changes we thought we were | 12:27 |
| @fungicide:matrix.org | so in order to get speculative container builds back to working order we've increased priority on switching everything over to podman | 12:28 |
| @amberdev:matrix.org | Got it. Which areas currently are in higher priority? So that i could probably share my findings? | 12:29 |
| @fungicide:matrix.org | the change i mentioned, and this one it depends on: https://review.opendev.org/883593 | 12:30 |
| @fungicide:matrix.org | also https://review.opendev.org/883446 | 12:30 |
| @fungicide:matrix.org | which depends on it | 12:30 |
| @fungicide:matrix.org | Clark and corvus can probably give a superior overview once they're around in a few hours | 12:30 |
| @amberdev:matrix.org | Ok. Thank you for pointers. Will read it through now. | 12:31 |
| @amberdev:matrix.org | Just a "first impression" OPINION: AFAIK Podman is leaning towards "K8s native" manifests. And thus `podman-compose` IMHO is more like an temporary "hack". `podman kube play` already supports `deployment.yaml`, `pvc.yaml` and `pod.yaml`. | 12:46 |
| @fungicide:matrix.org | and that can start containers without needing kubernetes? | 12:47 |
| @amberdev:matrix.org | Yeees | 12:47 |
| @fungicide:matrix.org | interesting | 12:48 |
| @amberdev:matrix.org | root-less | 12:48 |
| @amberdev:matrix.org | Not all K8s stanzas are supported, but most important ones are. https://docs.podman.io/en/latest/markdown/podman-kube-play.1.html (it is little bit outdated, but...). `initContainers` also are supported. | 12:52 |
| @amberdev:matrix.org | ```yaml | 12:54 |
| --- | ||
| apiVersion: apps/v1 | ||
| kind: Deployment | ||
| metadata: | ||
| name: db | ||
| namespace: example | ||
| labels: | ||
| app: db | ||
| spec: | ||
| replicas: 1 | ||
| selector: | ||
| matchLabels: | ||
| app: db | ||
| template: | ||
| metadata: | ||
| labels: | ||
| app: db | ||
| spec: | ||
| restartPolicy: Never | ||
| containers: | ||
| - name: mariadb | ||
| image: docker.io/mariadb:latest | ||
| imagePullPolicy: IfNotPresent | ||
| env: | ||
| - name: MYSQL_ROOT_PASSWORD | ||
| value: secret | ||
| - name: MYSQL_USER | ||
| value: gerrit | ||
| - name: MYSQL_PASSWORD | ||
| value: gerritsecret | ||
| - name: MYSQL_DATABASE | ||
| value: gerritdb | ||
| volumeMounts: | ||
| - name: db-pvc-mysql | ||
| mountPath: /var/lib/mysql | ||
| volumes: | ||
| - name: db-pvc-mysql | ||
| persistentVolumeClaim: | ||
| claimName: db-pvc-mysql | ||
| ... | ||
| ``` | ||
| @amberdev:matrix.org | `podman kube play deployment.yaml` | 12:54 |
| @amberdev:matrix.org | `podman kube play secret.yaml` also is supported. The point and my opinion is that it is worth to explore this area. | 13:03 |
| @jim:acmegating.com | that's cool, and we should keep an eye on that, but we should maintain compatibility with docker-compose; the point of the quick-start is not to be an actual deployment method (though it can be the start of one) it's to help people get started as easily as possible. despite our work to make it podman-compatible, i expect many people to still use it with docker-compose. | 13:32 |
| @amberdev:matrix.org | Agree. I will go `podman kube play` path and will share later what I came up with. It's not a big deal to create separate directory in the `examples/`. :) | 13:52 |
| @jim:acmegating.com | amberdev: just to set your expectations, we have taken a stance that the quick-start has just one path through it (a fully tested and guaranteed path) because we really want people to have a consistent working first experience with the quick-start (which is really more about *using* zuul than deploying it); so i don't expect us to suggest to people that there are too many options in the documentation. so i hope we can find a place for the kube play, but it's probably not going to be in the mainline quickstart (more of a "contrib" kind of thing); at least to start. | 13:56 |
| @amberdev:matrix.org | That's absolutely fine. | 13:57 |
| @jim:acmegating.com | cool :) | 13:57 |
| -@gerrit:opendev.org- Clark Boylan proposed on behalf of Tristan Cacqueray: [zuul/zuul] 687135: Replace docker by podman for quick-start https://review.opendev.org/c/zuul/zuul/+/687135 | 15:33 | |
| @jpew:matrix.org | There is not 8.3.1 tag for nodepool? | 15:46 |
| @jpew:matrix.org | (or 8.3.0 for that matter) | 15:46 |
| @clarkb:matrix.org | Coreect | 15:52 |
| @clarkb:matrix.org | I'd have to look and see if one should be made but the focus recently was a zuul release | 15:52 |
| @fungicide:matrix.org | 45 changes have landed in nodepool since 8.2.0 so it's probably time-ish | 16:02 |
| -@gerrit:opendev.org- Clark Boylan proposed on behalf of Tristan Cacqueray: [zuul/zuul] 687135: Replace docker by podman for quick-start https://review.opendev.org/c/zuul/zuul/+/687135 | 16:40 | |
| @clarkb:matrix.org | That just passed the quick start job | 17:06 |
| @fungicide:matrix.org | awesome! | 17:11 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!