| *** lemko has quit IRC | 00:08 | |
| *** sdake_ has quit IRC | 00:08 | |
| *** sdake has joined #openstack-loci | 00:24 | |
| *** sdake has quit IRC | 01:44 | |
| *** sdake has joined #openstack-loci | 01:46 | |
| *** sdake has quit IRC | 02:32 | |
| *** sdake has joined #openstack-loci | 02:34 | |
| *** sdake has quit IRC | 02:38 | |
| *** sdake_ has joined #openstack-loci | 02:39 | |
| *** sdake_ has quit IRC | 03:03 | |
| *** sdake has joined #openstack-loci | 03:09 | |
| *** sdake has quit IRC | 03:33 | |
| *** lemko has joined #openstack-loci | 05:50 | |
| *** sdake has joined #openstack-loci | 07:00 | |
| *** e0ne has joined #openstack-loci | 07:29 | |
| *** sdake has quit IRC | 07:33 | |
| *** e0ne has quit IRC | 07:43 | |
| *** e0ne has joined #openstack-loci | 07:44 | |
| *** e0ne has quit IRC | 07:44 | |
| *** itxaka has joined #openstack-loci | 07:50 | |
| *** e0ne has joined #openstack-loci | 07:50 | |
| *** lemko has quit IRC | 08:00 | |
| *** e0ne has quit IRC | 08:10 | |
| *** sdake has joined #openstack-loci | 08:19 | |
| *** lemko has joined #openstack-loci | 08:21 | |
| *** sdake has quit IRC | 09:26 | |
| *** e0ne has joined #openstack-loci | 10:19 | |
| evrardjp | is there a simple way to extract the files of the requirements image results into a mountpoint? | 10:28 |
|---|---|---|
| *** itxaka has quit IRC | 11:09 | |
| *** sdake has joined #openstack-loci | 11:12 | |
| *** sdake has quit IRC | 12:03 | |
| *** sdake_ has joined #openstack-loci | 12:03 | |
| portdirect | Podman can do this I believe | 13:07 |
| portdirect | Podman create; podman mount | 13:08 |
| *** sdake_ has quit IRC | 13:51 | |
| *** sdake has joined #openstack-loci | 14:17 | |
| *** sdake has quit IRC | 14:43 | |
| *** sdake has joined #openstack-loci | 14:45 | |
| evrardjp | ahah :) | 14:55 |
| evrardjp | who is available today? | 14:57 |
| e0ne | hi | 15:01 |
| hrw | o/ | 15:08 |
| evrardjp | so I would totally love to talk about what we are seeing | 15:08 |
| hrw | just nothing new to say compared to previous one | 15:08 |
| evrardjp | / doing | 15:08 |
| evrardjp | to see if we are doing it wrong -- I am thinking that the project building can consume a local path, so I was wondering if anyone else was building wheels and then, instead of publishing those in a docker container on a registry, was simply using them locally | 15:09 |
| evrardjp | portdirect: don't you think this would be nice for OSH? ^ | 15:10 |
| evrardjp | I think it would make the builds far easier | 15:10 |
| *** sdake has quit IRC | 15:21 | |
| *** sdake has joined #openstack-loci | 15:22 | |
| portdirect | Why not just serve them locally? | 15:23 |
| portdirect | That's what Sam and I do | 15:23 |
| evrardjp | what do you mean? | 15:35 |
| evrardjp | so you build the requirement image, and then... ? | 15:36 |
| evrardjp | you still have to get them out of the container I mean | 15:36 |
| portdirect | Serve the wheels via a webserver | 15:36 |
| evrardjp | yeah I understood that part | 15:37 |
| portdirect | Docker create, docker cp | 15:37 |
| evrardjp | mmm | 15:37 |
| portdirect | Essentially just what I do here for kubectl | 15:38 |
| portdirect | https://github.com/portdirect/nc-helpers/blob/master/things.sh | 15:38 |
| evrardjp | I see | 15:39 |
| hrw | meeting anyone? or not today? | 16:10 |
| *** e0ne has quit IRC | 16:11 | |
| evrardjp | portdirect: could you explain why it would be advantageous to serve on a webserver vs copying the wheels, or alternatively, getting the wheels from the overlay2 folder? | 16:12 |
| portdirect | Not saying its advantageous, just one way to do it without needing a docker registry | 16:13 |
| hogepodge | evrardjp: there is, it's built in to loci | 16:17 |
| hogepodge | I haven't tried it, but let me dig up the code path | 16:18 |
| hogepodge | evrardjp: if you specify the wheels parameter with an absolute path, it will mount it directly without downloading. https://github.com/openstack/loci/blob/master/scripts/fetch_wheels.py#L102 | 16:20 |
| *** e0ne has joined #openstack-loci | 16:20 | |
| hogepodge | note that it's treating the wheels like a docker container either way, so you don't have to worry about extracting it on your own (again, just from reading the code that's how I think it works). We set up to pull wheels from a docker registry to help manage parallel builds in gate. It's actually not a great idea to have that be your default behavior tbh. You shouldn't pull every instance of it since you can get it | 16:23 |
| hogepodge | locally through docker commands. | 16:23 |
| hogepodge | sorry I was late everyone, overslept | 16:23 |
| evrardjp | hogepodge: I know I wanted to leverage that in fact | 16:23 |
| evrardjp | hogepodge: yeah I agree it's not a good idea, that's why in OSH-images the wrapper shell script builds LOCI requirements, pushes to local registry, then run the other builds in parallel | 16:24 |
| evrardjp | but I would like to skip the "push to registry" | 16:25 |
| *** e0ne has quit IRC | 16:31 | |
| hogepodge | It should be entirely optional, use the docker image inspect to figure out where the image is. | 16:53 |
| *** evrardjp is now known as gatersaregonnaga | 16:58 | |
| *** gatersaregonnaga is now known as evrardjp | 17:00 | |
| *** sdake has quit IRC | 17:54 | |
| *** sdake has joined #openstack-loci | 17:55 | |
| *** lemko has quit IRC | 18:40 | |
| *** e0ne has joined #openstack-loci | 19:18 | |
| *** lemko has joined #openstack-loci | 19:27 | |
| *** sdake has quit IRC | 19:31 | |
| *** e0ne has quit IRC | 20:08 | |
| *** sdake has joined #openstack-loci | 22:37 | |
| *** lemko has quit IRC | 23:06 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!