Wednesday, 2021-12-08

mnasiadkaMorning07:15
mnasiadkaUpdating URL in meetings.opendev.org for Kolla (point to docs instead of Wiki) - https://review.opendev.org/c/opendev/irc-meetings/+/82098107:15
yoctozeptogood morning!07:27
yoctozeptomnasiadka: good catch, I have updated the wiki to point to docs but it seems sensible to have fewer mentions of wiki (as it is supposed to go)07:27
jingvaradmin1: look at kolla/kayobe source code template files, I've faced with the same when upgrade config from victoria to xena08:29
fricklermnasiadka: finally something I could +2 ;)08:52
frickleralso, could you have another look at https://review.opendev.org/c/openstack/kolla-ansible/+/820400 and indicate if and how you would like to have it variablized?08:53
guesswhatguys? how i can submit issue to openstack-kolla ? 09:08
mnasiadkaguesswhat: https://docs.openstack.org/kolla/latest/contributor/contributing.html#reporting-a-bug09:10
mnasiadkafrickler: make both (delay and retries) configurable, put them in role defaults and be done with it :)09:11
pescobarChecking the kolla release notes for Victoria I see latest version is "11.1.0-13" but checking dockerhub the latest 11.x tag is "11.1.0". Is there any reason why there is no docker tag "11.1.0-13" available in dockerhub? 09:26
kepskyy_Hello. I read the Contributor Guide and couldn't find a way to add the Operating System to the supported operating systems.09:30
kepskyy_Please tell me where to start and how to implement it. Thanks for the help.09:30
RoyHello there, anyone here knows how to use monasca's libvirt plugin with kolla ? It tries to communicate with nova which (ofc) isn't in the container and thus not possible. 09:33
hrwmorning09:36
hrwkepskyy_: which OS you would like to add?09:36
RoyI'm using an kolla openstack train and willing to get metrics of instances (being ubuntu/centos/rhel)09:39
hrwRoy: sorry, I do not have idea09:41
kepskyy_hrw: https://en.euro-linux.com/eurolinux/09:41
hrweurolinux... wasn't it yet-another-rhel-rebuild?09:42
hrwyeah09:42
hrwkepskyy_: we already have CentOS Stream 8 support. Use it?09:44
hrwkepskyy_: and do you want to use eurolinux as host OS? as in-container OS? both?09:45
hrwif host OS then kolla-ansible - check https://review.opendev.org/c/openstack/kolla-ansible/+/815104 for start.09:46
hrwkepskyy_: if in-container OS then you may look at https://review.opendev.org/c/openstack/kolla/+/809001 but we would rather reject idea of adding yet another distro09:47
kepskyy_i khnow abaut CentOS Stream but a lot of clients do not want to use CentOS Stream in produktion and switch to LTS supported OS09:48
hrwI do love that mess people have about CentOS Stream ;d09:49
hrwCentOS is EOL. CentOS Stream is LTS09:49
kepskyy_hrw: first i wont to use EL a host OS09:49
hrwkepskyy_: then look at k-a patch for Rocky Linux.09:49
hrwkepskyy_: you need ansible, python3-docker, docker-ce in repos and maybe few more components.09:50
hrwkepskyy_: and you probably end with 'yeah, we are euro linux but use centos repos' as usual09:50
kepskyy_hrw: no EL uses its own repo https://fbi.cdn.euro-linux.com/dist/eurolinux/server/8/09:55
guesswhatI created https://bugs.launchpad.net/kolla/+bug/1953601 , hope its ok09:56
kepskyy_hrw: I understand that this is not resolved on this channel, but which path needs to be taken for the OS to appear in Supported OS?09:57
guesswhatwhy is this abandoned https://review.opendev.org/c/openstack/kolla-ansible/+/816363 ?10:00
jingvarguesswhat: because you don't have +2 :)10:12
hrwkepskyy_: that is just base set of repos. no openstack packages, no ceph, no docker10:17
hrwkepskyy_: I will reply to your email10:18
kepskyy_hrw: thanks a lot.10:20
hrwreplied10:32
hrwkepskyy_: in short: good luck10:32
kepskyy_hrw: thanks :)11:12
hrwkevko: you gave +2 as second core so give it +W too https://review.opendev.org/c/openstack/kolla/+/818095 ;d11:13
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: Import baremetal role from kolla-ansible  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82016811:13
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: CI: add initial deploy jobs  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82090711:13
hrwkepskyy_: CI will be biggest issue imho.11:13
darmachjoin kayobe11:15
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: some small tidy ups  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82100311:16
hrwmgoddard, mnasiadka, kevko: https://review.opendev.org/c/openstack/kolla/+/820045 deprecates qdrouterd and needs your +2+w11:46
opendevreviewMerged openstack/kolla master: qdrouterd: add release note with deprecation notice  https://review.opendev.org/c/openstack/kolla/+/82004512:01
kevkohrw: going to check 12:11
kevkoah ..sorry ..merged :D i was on lunch12:11
dtantsurhi folks, could I get a 2nd +2 on https://review.opendev.org/c/openstack/kolla-ansible/+/820513 please? trying to minimize future impact on your CI.12:11
opendevreviewDr. Jens Harbott proposed openstack/kolla-ansible master: Bump timeout for grafana startup  https://review.opendev.org/c/openstack/kolla-ansible/+/82040012:28
guesswhatanyone tried to use certmanager ( DNS01 ) with kolla ? ( for internal/external ) are certificates ( crt + key ) hotreloaded when files are changed? or do i need to redeploy haproxy ?12:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor selinux config into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101412:35
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor kolla user & group creation into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101512:35
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor docker-sdk installation to a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101612:35
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docker-sdk: use become_user=kolla to create virtualenv  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101712:35
holtgreweHi, I'm seeing the same as in the following issue. https://bugs.launchpad.net/kolla-ansible/+bug/188403412:49
holtgreweI have a Xena kolla deployment, logs here: https://paste.openstack.org/show/811543/12:52
holtgreweI will try to remove the rabbitmq containers, volumes, images on all hypervisors/controllers and then "kayobe overcloud service deploy" again (docker rm -f rabbitmq ; docker volume rm rabbitmq ; docker image rm quay.io/openstack.kolla/centos-source-rabbitmq:xena)12:54
holtgreweApparently resolved my issue.13:01
opendevreviewMerged openstack/kolla-ansible master: Prepare tests for the Ironic combined service  https://review.opendev.org/c/openstack/kolla-ansible/+/82051313:38
opendevreviewMartin Hiner proposed openstack/kolla-ansible master: Refactor of kolla_docker into module_utils  https://review.opendev.org/c/openstack/kolla-ansible/+/81795413:50
mnasiadkamgoddard: actually ^^ this made me think - maybe in the longer run we also want to move Ansible modules into Kolla collection?13:55
mgoddardmnasiadka: yeah, potentially13:55
holtgreweHm, I have trouble with networking on my seed hypervisor machine... Could anyone show me their `ip l` `ip a` and `ip route` output?14:33
holtgrewethe kayobe hypervisor setup results in a working configuration but on reboot, I get weird configuration and network does not work.14:33
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor kolla user & group creation into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101514:42
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor docker-sdk installation to a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101614:42
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docker-sdk: use become_user=kolla to create virtualenv  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101714:42
opendevreviewMarcin Juszkiewicz proposed openstack/kolla master: Add HTTP proxy support for fetching APT keys  https://review.opendev.org/c/openstack/kolla/+/69202914:52
mnasiadkamgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne cosmicsound osmanlicilegi bbezak parallax Fl1nt frickler adrian-a - meeting in 314:57
yoctozeptook14:57
priteauSorry I cannot join the meeting today. Just wondering if I could get some feedback on https://review.opendev.org/c/openstack/kolla-ansible/+/81871415:00
mnasiadka#startmeeting kolla15:01
opendevmeetMeeting started Wed Dec  8 15:01:03 2021 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'kolla'15:01
yoctozeptopriteau: nice marketing15:01
mnasiadka#topic rollcall15:01
yoctozepto(priteau: is it only related? does not it fix the bug?)15:01
yoctozeptoo/15:01
mgoddard\o15:01
fricklero/15:01
mnasiadkao/15:02
parallax.15:02
osmanlicilegio/15:03
mnasiadka#topic agenda15:04
mnasiadka* Review action items from the last meeting15:04
mnasiadka* CI status15:04
mnasiadka* Release tasks15:04
mnasiadka* Current cycle planning15:04
mnasiadka* Additional agenda (from whiteboard)15:04
mnasiadka* Open discussion15:04
mnasiadka* (yoctozepto) CI - CentOS 8 images are to be gone by January 2022 http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html15:04
mnasiadka* (mnasiadka) Kolla images single distro - blockers15:04
mnasiadka(two last before Open discussion)15:05
mnasiadka#topic Review action items from the last meeting15:05
mnasiadkamnasiadka to triage security bugs and update them with resolution plan (if needed)15:05
mnasiadkayoctozepto hide properly init-runonce15:05
mnasiadkaanybody not forget to go through backports for stable branches (L248 on Whiteboard) and do stable releases afterwards.15:05
mnasiadkamnasiadka post a patch for docs - standard topics that should be discussed over PTG and then revisited in mid-cycle15:05
mnasiadkaI haven't done mine15:05
mnasiadkayoctozepto: ?15:06
mnasiadka#action mnasiadka to triage security bugs and update them with resolution plan (if needed)15:06
mnasiadka#action mnasiadka post a patch for docs - standard topics that should be discussed over PTG and then revisited in mid-cycle15:06
mnasiadka#action anybody not forget to go through backports for stable branches (L248 on Whiteboard) and do stable releases afterwards.15:06
yoctozeptomnasiadka15:07
yoctozeptoI posted a patch15:07
yoctozeptolet me find it15:07
yoctozepto#link https://review.opendev.org/c/openstack/kolla-ansible/+/82094015:08
yoctozeptoI think we could go more aggressive but it's a good first step to increase awareness15:08
mnasiadkaok then, at least one off the table15:08
mnasiadka#topic CI status15:08
yoctozeptoas this action point was made because people were following init-runonce as a mandatory step15:08
opendevreviewDr. Jens Harbott proposed openstack/kolla-ansible master: Bump timeout for grafana startup  https://review.opendev.org/c/openstack/kolla-ansible/+/82040015:09
yoctozeptook :-)15:09
mnasiadkaSo, how's the CI?15:09
mnasiadkaKolla Ussuri is red on centos15:09
yoctozeptok&k-a on regularly supported branches seemed ok15:09
yoctozeptobut yeah, em ussuri kolla is red15:09
yoctozeptografana does not like something15:09
mnasiadkais there a volunteer to look into it?15:10
yoctozeptonot me15:10
parallaxI might15:11
mnasiadka#action parallax look into Grafana Kolla build failures on Ussuri/CentOS15:11
mnasiadkalet's move on15:11
mnasiadkathanks parallax 15:11
mnasiadka#topic Release tasks15:11
mnasiadkaHow are we with those R-17 jobs?15:12
mnasiadkaall three projects switched?15:12
yoctozeptono idea15:12
yoctozeptolet's take a look15:12
yoctozepto#link https://review.opendev.org/c/openstack/kolla/+/82004315:13
yoctozepto^ kolla needs merging this15:13
mnasiadkaok then, +w15:13
yoctozeptoI wonder if we should just kill vmtp15:13
yoctozeptobtw15:14
mnasiadkawatcher and vmtp are not probably very popular15:14
yoctozeptohttps://review.opendev.org/q/project:x%252Fvmtp15:14
yoctozeptoseems unmaintained15:14
yoctozeptois k-a doing something with vmtp?15:14
mnasiadkaI would ask what is vmtp useful for?15:14
mnasiadkaah, data path performance tool - but it seems it's at least abandoned for a year15:15
yoctozeptomnasiadka: well, that's a paraphrase 15:15
yoctozeptomnasiadka: yeah15:15
yoctozeptoI think it's broken anyway15:15
yoctozeptolooking at the contents of the vmtp role15:16
yoctozeptoI would refrain from touching it15:16
yoctozeptomaybe just drop? project unsupported, in x/, and we bid farewell?15:16
mnasiadkaProbably that's the case - but shouldn't we at least send a mail to openstack ML and wait a week for any replies?15:17
yoctozeptowatcher is at least in openstack/ and has some movement15:17
yoctozeptomnasiadka: sure thing, but it's likely we are forced to drop it anyway15:17
mnasiadkasure, just want to have it communicated so we don't have more angry supporters ;-)15:17
mnasiadkayoctozepto: will you send the mail?15:18
yoctozeptomnasiadka: ok15:18
mnasiadka#action yoctozepto to send mail to openstack ML about dropping vmtp15:18
mnasiadkaso, kolla-ansible and kayobe patches for R-17 are merged?15:18
yoctozeptoabout kayobe I don't know15:18
yoctozeptok-a seems so, but you could verify15:18
mnasiadkaseems it is15:20
yoctozeptook then15:20
yoctozepto:-)15:20
mnasiadkalet's go with the additional topics now, since they impact some planning.15:21
mnasiadka#topic (yoctozepto) CI - CentOS 8 images are to be gone by January 2022 http://lists.opendev.org/pipermail/service-announce/2021-December/000029.html15:21
yoctozeptoyeah, we need to get rid of jobs using them15:22
mnasiadkaThat means we should cease centos8 (non-stream) based jobs in January15:22
yoctozeptoindeed15:22
yoctozeptoand possibly notify the world we are doing it15:22
mnasiadkaOk, mail to openstack ML + a reno?15:23
yoctozeptoI guess?15:23
mnasiadkaOk, makes sense.15:23
mnasiadkaShould we also think about EOL for stable/train in the process?15:24
yoctozeptohmm, maybe? though it seems yet another topic15:24
mnasiadkaOk, so let's first carry on dropping of CentOS jobs15:25
mnasiadkaIs there a volunteer?15:25
mgoddardwhy EOL train?15:25
mgoddardCentOS isn't the only distro15:26
yoctozeptomnasiadka: I can do it15:27
mnasiadka#action yoctozepto to remove CentOS 8 based CI jobs and manage communication (ML and renos)15:27
mnasiadkaActually, what about CentOS7?15:29
yoctozeptostill supported till 202415:29
yoctozepto(-:15:29
mnasiadkaso we only remove the python3 CentOS8 jobs? fantastic15:29
yoctozeptoyeah, the joke is big15:29
mnasiadkaAnyway15:30
mnasiadkamgoddard: right, I know there are other distros - just asking15:30
mnasiadkanext topic15:30
mnasiadka#topic (mnasiadka) Kolla images single distro - blockers15:31
mnasiadkaWe've had this discussion initially last week - but mgoddard was absent - and we agreed to continue today15:31
mnasiadkaWe've also had an internal StackHPC meeting, and given that on our roadmap we have FIPS certification and SELinux/AppArmor support - we can't unfortunately agree with the goal of going to single distro...15:32
yoctozeptowill debian images fail to support these reqs?15:33
yoctozeptoselinux/apparmor is supported well15:34
yoctozeptocertification for our images is tricky anyway15:34
yoctozeptofips* certification ;-) 15:34
mnasiadkaWe don't want to close doors for that ;-)15:35
yoctozeptowill using debian close these doors? is using ubuntu better? we can decide on ubuntu instead15:36
yoctozeptoin fact that's the most tested distro anyway...15:36
mnasiadkaAround SELinux and AppArmor - I'm sure it's going to be more complicated to implement it when having different host os and in-container os15:36
yoctozeptomnasiadka: re selinux and apparmor - you need custom policies anyway - better write them for one setup15:37
mnasiadkaWe need support for both CentOS/RHEL/etc and Ubuntu on the Host OS, and there are customers that want to have the same ,,flavor'' on the Host OS and in the containers - it's not that we dictate what you get - we don't want to loose customers this way.15:38
mnasiadkaAnd I - as a PTL - am worried with users/operators wandering off somewhere else, because we do this - or because of issues that we'll bring on them ;-)15:39
mnasiadkaI think for most users dropping binary is a change, let's not push it to the limits.15:39
fricklerso that means you want to build CS9 support?15:40
mnasiadkaThat's up for discussion, for now we'd like to stick to CS8 as long as it's possible.15:40
yoctozeptonot much longer beyond the Yoga cycle15:41
yoctozepto;-)15:41
mnasiadkaonce RHEL9 is out, there might be other options viable than CentOS Stream 915:41
mgoddardwe have a few related research items15:41
yoctozeptoI *think* long term you, as a company, would benefit more from streamlining clients to the same set of images15:41
mgoddard1. libvirt on the host15:42
yoctozeptoas you support them, they don't have to worry about discrepancies as you solve them15:42
mgoddard2. py3.9 in cs8 images15:42
yoctozeptobut surely short-term this sounds like some extra work15:42
mgoddardthere is certainly an argument for single distro - it hasn't been an easy call to make15:43
yoctozeptoad 1) seemingly libvirt in container is quite fine with different kernels, though it may need some extra verification15:43
yoctozeptoad 2) that we can try to extedn the life of it15:43
mgoddardwe have seen issues with mixing libvirt versions15:44
yoctozeptosince we don't have to have support for python-selinux/python-dnf inside15:44
yoctozeptomgoddard: yeah, mixing is problematic; but still it contributes to making it better by controlling the version in the container15:44
mnasiadkaWell, we already allowed libvirt 6.9.0 in stream images, which has a peculiar bug spamming the logs with one message constantly ;-)15:45
mgoddardor just run it on the host and don't worry :)15:45
mnasiadkaWe can have both options I guess.15:46
bbezaklibvirt 7.9 ;)15:46
mnasiadkaah, 7.915:46
yoctozeptomnasiadka: what does it say?15:46
mnasiadkayoctozepto: https://www.mail-archive.com/libvir-list@redhat.com/msg222970.html this - but not only on power915:46
mnasiadkait's patched in 7.10 and doesn't exist in 7.615:46
bbezakI got this on some dell x86 as well15:47
yoctozeptowell, the issue with having both supported means more to support :D15:47
yoctozeptomnasiadka: eh :D15:47
mnasiadkayoctozepto: that's what we get with stream ;-)15:47
mnasiadkaAnd we probably get those messages every week that nobody wants to use stream.15:48
yoctozeptowell, it's odd they let this kind of issue slip in, seems quite widespread15:48
mnasiadkawell, RHEL sticks to 7.615:48
mnasiadkaI think15:48
yoctozeptoeh15:49
mnasiadkaAnyway, we're diverting - is there anything more to add to this topic?15:49
yoctozeptorocky linux in images instead?15:49
yoctozeptobut I don't want to do it15:49
mnasiadkaI think if our company wants to continue current path, we need to take this - but let's see how the situation evolves with the research activities mgoddard mentioned15:50
mnasiadkaand if Rocky Linux doesn't die before RHEL 9 gets out ;-)15:50
yoctozeptohah, true that15:51
mnasiadkaOk, I crossed out the single distro from the priorities for now.15:51
mnasiadkaAround it, let's try to grasp what is missing for deprecating source.15:51
mnasiadka#topic Current cycle planning15:52
bbezakbinary?15:52
mnasiadkabinary, yes15:52
mnasiadkamy mind is not best today.15:52
mnasiadkaKolla whiteboard L31615:52
yoctozeptodon't worry, I'm struggling these days too15:52
mnasiadka#link https://etherpad.opendev.org/p/KollaWhiteBoard15:52
mnasiadkaTODO(): better document the differences between them, so that users can make an educated decision transition more easily15:53
mnasiadkaIs there a volunteer to do that? Do we still think we need to do that?15:53
yoctozeptohmm15:54
yoctozeptosounds nice to have, but not volunteering15:54
mgoddardI think we could use some more info about what source images are - there seems to be a general lack of understanding15:55
yoctozeptoindeed15:55
mnasiadkaYes, agreed15:55
mnasiadkaBut there's no volunteer - I will keep asking on next meetings.15:55
mnasiadkafrickler: did you have any progress with your task?15:56
mnasiadkaDo you need any help?15:56
fricklermnasiadka: well I found that osism has some framework around it https://github.com/osism/container-images-kolla15:56
fricklerwith options to add patches and things into image builds15:56
fricklerbut I haven't used it myself yet, so only basic understanding so far15:57
mnasiadkaYes, but I think kevko was a special case here - especially around overriding pip packages versions and uppper-constraints15:57
mnasiadkaSo if that's possible - we'd need some improved docs on overriding these, if not - we need to think how to implement it.15:57
mnasiadkaAnd I think that's most important task from all those that we have in this ,,priority item''15:58
mnasiadkaAnyway, time's up - let's try to at least iron out what needs to be done in this ;-)15:59
mnasiadkaThanks for attending.15:59
mnasiadka#endmeeting15:59
opendevmeetMeeting ended Wed Dec  8 15:59:39 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-12-08-15.01.html15:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-12-08-15.01.txt15:59
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-12-08-15.01.log.html15:59
fricklero.k., can someone (kevko?) specify what exactly is the requirement there?15:59
yoctozeptothanks mnasiadka16:00
mnasiadkaLet's try to catch kevko when he will be online and add some details to that task16:00
kevkomnasiadka, frickler: I will reach you on discuss email .. I have vacation ..I just accidentaly check irc :) 16:02
mnasiadkafrickler: here you go ^^ ;)16:03
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor kolla user & group creation into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101516:03
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor docker-sdk installation to a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101616:03
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docker-sdk: use become_user=kolla to create virtualenv  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101716:03
mnasiadkamgoddard: feel free to add your collection work to Yoga priorities and post change links there when it's ready to review16:04
mgoddardmnasiadka: will do16:04
yoctozeptomgoddard/mnasiadka: https://review.opendev.org/c/openstack/kolla/+/81478316:26
mgoddarddone16:32
opendevreviewMerged openstack/kolla master: switch source images to follow master branches  https://review.opendev.org/c/openstack/kolla/+/82004316:38
hrwhttps://bugs.launchpad.net/kolla/+bug/1758374 - wontfix or how to solve it?17:14
mnasiadkawell, wontfix - you can't, since the image is not there17:15
mnasiadkaif you set invalid - it will be closed after the timeout, which is 30 or 90 days - don't remember17:15
hrwmarked wontfix17:15
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor docker-sdk installation to a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101617:23
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docker-sdk: use become_user=kolla to create virtualenv  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101717:23
yoctozeptomgoddard: thanks17:29
yoctozeptomnasiadka: you are describing "incomplete"17:29
mnasiadkaah, maybe17:29
yoctozepto"invalid" is fine if it no longer applies17:30
yoctozepto"won't fix" if we don't want to fix it or can't :D 17:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: Sync basics with kolla-ansible  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82016717:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docs: remove most boilerplate, initialise contributor guide  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82056017:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: CI: run ansible-test sanity checks  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82090217:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: Import baremetal role from kolla-ansible  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82016817:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: CI: add initial deploy jobs  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82090717:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: some small tidy ups  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82100317:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor selinux config into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101417:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor kolla user & group creation into a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101517:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: baremetal: refactor docker-sdk installation to a separate role  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101617:30
opendevreviewMark Goddard proposed openstack/ansible-collection-kolla master: docker-sdk: use become_user=kolla to create virtualenv  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/82101717:30
yoctozeptooh what a spam17:30
hrwmeh. kevko is on vacations but -1 on https://review.opendev.org/c/openstack/kolla/+/795054 keeps.17:31
mnasiadkaso invalid seems to fit better, Won't Fix: this is acknowledged as a genuine bug but the project has no plans to fix it.17:31
hrwanyone to review ^^?17:31
holtgreweCould anyone help me with my seed hypervisor network settings? Somehow I made kayobe generate configuration such that traffic does not travel to/from the hypervisor to the outside (I can ping the seed from the hypervisor, though). https://paste.openstack.org/show/811555/17:34
priteauholtgrewe: looks like your brbond0 interface, which is your default route, doesn't have any physical interface attached to it17:43
priteauBased on the naming, I am guessing you should have a bond0 bond interface, with members ens3f0 and ens3f117:44
priteauAnd then the brbond0 bridge would be have bond0 as a child interface. Kayobe will also automatically add p-brbond0-phy to it17:46
holtgrewepriteau, that is correct... I forgot to paste the ifcfg-* files that kayobe created17:46
holtgrewehttps://paste.openstack.org/show/811557/17:46
priteauSo where does vnet0 come from?17:46
holtgrewehttps://paste.openstack.org/show/811558/ here is the kayobe config17:47
holtgrewegood question about vnet0, I believe this is created by libvirt/virsh17:47
priteauseed_hypervisor_network_interfaces:17:49
priteau  - private_net17:49
priteauThis may be the issue17:49
holtgreweMaybe the private_net_interface should not be a bridbe but the bond itself?17:50
priteauTry seed_hypervisor_extra_network_interfaces instead17:50
holtgrewegood pointer17:50
priteauI have to go now, sorry17:50
holtgreweno worries, this was already very useful!17:50
holtgrewethank you a lot!17:50
guesswhatanyone tried to use certmanager ( DNS01 ) with kolla ? ( for internal/external ) are certificates ( crt + key ) hotreloaded when files are changed? or do i need to redeploy haproxy ?17:53
holtgreweNow I'm getting funny other network issuses. "brbond0: received packet on bond0 with own address as source address (addr:6e:3d:9d:54:08:a5, vlan:0)"17:54
* hrw out17:58
opendevreviewVerification of a change to openstack/kolla master failed: Debian: enable building Bifrost images on x86-64  https://review.opendev.org/c/openstack/kolla/+/81478318:00
opendevreviewDr. Jens Harbott proposed openstack/kolla-ansible master: Bump timeout for grafana startup  https://review.opendev.org/c/openstack/kolla-ansible/+/82040018:29
opendevreviewMerged openstack/kolla master: Ensure nvme-cli is present in nova-compute images  https://review.opendev.org/c/openstack/kolla/+/82089218:44
opendevreviewMichal Nasiadka proposed openstack/kayobe master: ipa: Use openstack_branch instead of master  https://review.opendev.org/c/openstack/kayobe/+/82111518:45
*** bodgix3 is now known as bodgix20:10
*** EugenMayer3 is now known as EugenMayer20:10
opendevreviewMaksim Malchuk proposed openstack/kayobe master: Skip IP address allocation and configuration if needed  https://review.opendev.org/c/openstack/kayobe/+/82112921:01
opendevreviewMaksim Malchuk proposed openstack/kayobe master: Skip IP address allocation and configuration if needed  https://review.opendev.org/c/openstack/kayobe/+/82112921:03
opendevreviewMerged openstack/kolla master: Debian: enable building Bifrost images on x86-64  https://review.opendev.org/c/openstack/kolla/+/81478321:07
opendevreviewPierre Riteau proposed openstack/kolla stable/xena: Ensure nvme-cli is present in nova-compute images  https://review.opendev.org/c/openstack/kolla/+/82104421:55
opendevreviewPierre Riteau proposed openstack/kolla stable/wallaby: Ensure nvme-cli is present in nova-compute images  https://review.opendev.org/c/openstack/kolla/+/82104521:55
opendevreviewPierre Riteau proposed openstack/kolla stable/victoria: Ensure nvme-cli is present in nova-compute images  https://review.opendev.org/c/openstack/kolla/+/82104621:55

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