| *** d34dh0r53 has quit IRC | 03:22 | |
| *** d34dh0r53 has joined #openstack-loci | 03:38 | |
| *** irclogbot_0 has quit IRC | 03:41 | |
| *** irclogbot_2 has joined #openstack-loci | 03:42 | |
| *** e0ne has joined #openstack-loci | 05:21 | |
| *** dpawlik has joined #openstack-loci | 06:04 | |
| *** e0ne has quit IRC | 07:35 | |
| *** e0ne has joined #openstack-loci | 09:08 | |
| evrardjp | parasitid: mmm yes indeed. | 13:55 |
|---|---|---|
| *** e0ne has quit IRC | 14:13 | |
| *** dpawlik has quit IRC | 14:17 | |
| parasitid | evrardjp: im trying something ill push as WIP | 14:41 |
| evrardjp | thanks! | 14:48 |
| evrardjp | sorry I was quite busy the last days | 14:48 |
| openstackgerrit | yann degat proposed openstack/loci master: Add basic auth support for wheels registry https://review.opendev.org/661242 | 14:54 |
| parasitid | evrardjp: done | 14:55 |
| parasitid | evrardjp: it still wip, but i dont think ill go further if ever this approach is not suitable | 14:56 |
| parasitid | evrardjp: we'd keep a downstream patch instead | 14:56 |
| *** e0ne has joined #openstack-loci | 14:57 | |
| *** e0ne has quit IRC | 15:00 | |
| hogepodge | hi everybody | 15:03 |
| hogepodge | any topics for todya? | 15:03 |
| evrardjp | I have a topic | 15:04 |
| evrardjp | but I am not sure about the format | 15:05 |
| evrardjp | So, maybe I should just start it here. | 15:05 |
| hogepodge | sure | 15:05 |
| evrardjp | I have an idea that is through my mind for a certain time | 15:05 |
| evrardjp | (bear with me) | 15:05 |
| evrardjp | Currently most, if not all, the openstack projects have their own bindep file | 15:06 |
| evrardjp | we are carrying bindep files, that sounds like a lot of overlap | 15:06 |
| evrardjp | I thought we could have a cross-project community work to handle bindep files in a "common" way | 15:07 |
| evrardjp | So I thought of starting a SIG for containers building, for which one of the first deliverables would be a common agreement on bindep file management | 15:07 |
| evrardjp | I will not start this work until ppl in here are in agreement | 15:08 |
| evrardjp | hogepodge: opinion? | 15:08 |
| evrardjp | maybe the meeting is not the appropriate place to talk about that either | 15:08 |
| hogepodge | I'm in favor of collecting common work across projects | 15:09 |
| portdirect | evrardjp: I think that would be a great initiative | 15:09 |
| evrardjp | because of that would be a common agreement, it would bind multiple projects, like LOCI/Kolla/OSH | 15:09 |
| evrardjp | "bind" | 15:09 |
| evrardjp | I mean "help" ofc | 15:10 |
| evrardjp | without the quotes | 15:10 |
| evrardjp | hahah | 15:10 |
| evrardjp | anyway | 15:10 |
| evrardjp | ok I will start this then | 15:10 |
| evrardjp | nothing else | 15:12 |
| hogepodge | Some of the zuul team is asking about a lighter-weight way of installing openstack, and though loci might be an answer | 15:13 |
| hogepodge | They're ok with using a set of pre-built containers, and just need something that comes up quickly. | 15:14 |
| evrardjp | hogepodge: you are thinking of a docker-compose thing? | 15:14 |
| hogepodge | I'm still refactoring locistack, but it could be a solution. | 15:14 |
| evrardjp | or locistack? | 15:14 |
| evrardjp | ok | 15:14 |
| hogepodge | The problem we have is stock loci containers on their own can't really run openstack, they typically need additional binaries installed, which is the major impact on installation time. | 15:15 |
| *** e0ne has joined #openstack-loci | 15:15 | |
| evrardjp | does those need to be part of the default installs? | 15:16 |
| evrardjp | I mean I get we don't want to go deep into the opinion, so we can be reused by the many (like OSH) | 15:16 |
| evrardjp | but maybe there are overlap there | 15:17 |
| hogepodge | not always, like cinder doesnt need tgt if its using different storage services | 15:17 |
| evrardjp | overlaps* | 15:17 |
| hogepodge | there's a balance between too much and too little. | 15:17 |
| evrardjp | yup | 15:18 |
| hogepodge | But if there is overlap, and things we all need, I'm ok with refining what stock means. Maybe the solution is to include more in "stock" builds but have the option to pare builds down | 15:19 |
| hogepodge | We can do this with profiles. | 15:19 |
| evrardjp | yes | 15:19 |
| hogepodge | One of my bigger needs is I use python-openstackclient as part of my orchestration tooling, so lots of containers need it but it isn't a strict requirment. Those pull in quite a few packages | 15:20 |
| evrardjp | hogepodge: funny you say that, because OSH just added it to some of its containers | 15:20 |
| *** e0ne has quit IRC | 15:21 | |
| evrardjp | oh wait we didn't merge that yet | 15:21 |
| hogepodge | speaking of osh, another thing that's been on my mind is loci governance | 15:22 |
| evrardjp | do you have somethign in mind? | 15:22 |
| evrardjp | (like nova?) | 15:22 |
| hogepodge | if osh is the largest consumer, to me it might make sense to fold loci into osh governance | 15:22 |
| *** e0ne has joined #openstack-loci | 15:24 | |
| hogepodge | evrardjp: portdirect: do you have opinions on that thought? | 15:25 |
| *** e0ne has quit IRC | 15:27 | |
| *** e0ne has joined #openstack-loci | 15:29 | |
| hogepodge | by the power of lazy consensus... ;-) | 15:30 |
| evrardjp | I can't really judge that. | 15:30 |
| evrardjp | let me rephrase that | 15:30 |
| evrardjp | TC hat only: I think I'll be okay for whatever the projects decide, as they are deciding together | 15:31 |
| evrardjp | As a LOCI core: I don't really mind, as I am contributing to OSH anyway. I would lose my core status on that move, but I think it's not a big deal, less reviews for me :p | 15:32 |
| evrardjp | As a OSH contributor: It's not up to me, it's up to higher :p | 15:32 |
| evrardjp | sorry for the long answer :) | 15:32 |
| hogepodge | Repositories can still have sub-cores. I think it would in the long run be healthier, but it's up to portdirect and the rest of the OSH team. | 15:33 |
| hogepodge | to decide together | 15:33 |
| evrardjp | correct that's what I meant | 15:33 |
| evrardjp | at least you have offered | 15:33 |
| *** e0ne has quit IRC | 15:33 | |
| evrardjp | :) | 15:33 |
| evrardjp | what would locistack be? | 15:35 |
| evrardjp | in that case? You don't want to have it in governance? Or you want it to be part of infra? | 15:36 |
| hogepodge | not sure, I've always dreamed it would be functional testing for loci | 15:37 |
| evrardjp | it's noble :) | 15:38 |
| evrardjp | hogepodge: my point about the osh/loci core aspect is not a problem for me, but I was expecting it could be different for you | 15:39 |
| hogepodge | I try not to invest too much in my status in a project. I want to do what's best for a project. | 15:40 |
| evrardjp | it's not about status | 15:41 |
| evrardjp | it's about commitment | 15:41 |
| evrardjp | you would now have to commit to new things that may not be aligned with your goals | 15:41 |
| evrardjp | and losing reviewers is not nice :/ | 15:42 |
| hogepodge | I can keep reviewing :-) | 15:42 |
| evrardjp | :) | 15:42 |
| hogepodge | loci is my main vehicle for running openstack. Part of my responsibilities of the OSF technical staff is to run our software and talk about all the cool things it can do. | 15:43 |
| evrardjp | got it | 15:43 |
| evrardjp | I have nothing to add :) | 15:46 |
| evrardjp | I am fine with that move if you think it's the best for the project :) | 15:46 |
| hogepodge | something to think about, I'm in no rush | 15:48 |
| hogepodge | thanks | 15:48 |
| *** e0ne has joined #openstack-loci | 17:41 | |
| *** e0ne has quit IRC | 17:46 | |
| *** dpawlik has joined #openstack-loci | 18:34 | |
| *** e0ne has joined #openstack-loci | 18:42 | |
| *** e0ne has quit IRC | 19:16 | |
| *** e0ne has joined #openstack-loci | 19:16 | |
| *** e0ne has quit IRC | 19:21 | |
| *** e0ne has joined #openstack-loci | 19:23 | |
| *** e0ne has quit IRC | 19:33 | |
| *** dpawlik has quit IRC | 22:29 | |
| *** dpawlik has joined #openstack-loci | 22:45 | |
| *** dpawlik has quit IRC | 22:50 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!