Tuesday, 2021-12-21

opendevreviewMerged openstack/openstack-ansible stable/xena: Bump OpenStack-Ansible for Xena RC2 and release  https://review.opendev.org/c/openstack/openstack-ansible/+/82225900:45
noonedeadpunkat least now I know whom to ask question about ironic when they arise :p02:04
noonedeadpunkwould be great to get vote for EOL of Ocata at least https://review.opendev.org/c/openstack/openstack-ansible/+/79569002:09
jrosser_would be nice to get ARA fixed - i pushed this after we talked about the runtime venv constraints the other day https://review.opendev.org/c/openstack/openstack-ansible/+/822088/307:44
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_keystone master: DNM - test db setup with logging enabled  https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/82239107:44
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: [WIP] Update ansible-core to 2.12.1  https://review.opendev.org/c/openstack/openstack-ansible/+/82206307:44
jrosser_noonedeadpunk: you are right it is missing selinux https://paste.openstack.org/show/811790/08:21
noonedeadpunktbh I'm surpised it went that long08:37
noonedeadpunkhave you reproduced that in aio?08:38
jrosser_no, not done an AIO for this08:41
noonedeadpunkok, will spawn then :) 08:41
noonedeadpunkwonder if that selinux module would jsut work....08:41
jrosser_I think our current patches already use rsync for selinux in the runtime venv08:42
noonedeadpunkwell, there're no selinux for 3.8?08:42
noonedeadpunk*python selinux bindings08:42
noonedeadpunkso we need either to build one or dunno08:43
noonedeadpunk(eventually centos explicitly said in docs they won't provide binding for 3.8)08:44
jrosser_noonedeadpunk: as the db setup is delegated to oslodb_setup_host and uses oslodb_ansible_python_interpreter this looks more about the target python / selinux rather than the ansible controller?09:27
noonedeadpunkit's failing also for metal?09:28
noonedeadpunkwell, yeah, might be. eventually we need to run services also in 3.8 python...09:28
noonedeadpunk3.6 EOLing in 2 days09:28
jrosser_super odd policy from RH again on this09:29
jrosser_it was just the same with python3 on centos-709:30
noonedeadpunkyeah, and it's same09:43
*** dviroel_ is now known as dviroel11:19
noonedeadpunkjrosser_: do you think we should have https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/816531 or just abandon as it brings a lot of complexity for arguable profit?12:04
noonedeadpunkit happened to us to be handy to use templated service outside of osa12:05
opendevreviewJames Denton proposed openstack/openstack-ansible-os_ironic master: Update Ironic Documentation  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/82220314:30
noonedeadpunkdoes anybody has any idea how that works? https://opendev.org/openstack/ansible-hardening/src/branch/master/tasks/main.yml#L5514:40
noonedeadpunkshouldn't it work only with inlcude as there's a variable?14:41
noonedeadpunkah, only variables from invetory can't be used, ok 14:45
jamesdentongood to know14:55
noonedeadpunk#startmeeting openstack_ansible_meeting15:00
opendevmeetMeeting started Tue Dec 21 15:00:23 2021 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:00
noonedeadpunk#topic office hours15:00
noonedeadpunko/15:00
damiandabrowski[m]hey!15:02
spateljamesdenton morning15:04
jamesdentonhi15:04
spatelhttps://satishdotpatel.github.io/trex-load-generator/15:04
spatelblog that out 15:04
jamesdentonvery nice, thank you.15:04
jamesdentonif you want to develop a test method i am happy to reproduce, and we can compare15:04
jamesdentonhi noonedeadpunk 15:05
spatelBlog this for documentation, so i used VMware virtual machine. now i am going to do same on physical machine. 15:05
spateli am going to add TestPMD and L2fwd also so just for document.15:06
opendevreviewJeremy Stanley proposed openstack/openstack-ansible master: Prepare for stable/ocata EOL  https://review.opendev.org/c/openstack/openstack-ansible/+/82250015:08
*** dviroel is now known as dviroel|lunch15:09
noonedeadpunkSo.15:10
noonedeadpunk24.0.0 is about to be merged https://review.opendev.org/c/openstack/releases/+/822370/115:10
noonedeadpunkHopefully it will be done today, but not 100% sure15:11
noonedeadpunkalso stable/ocata branch has been dropped for roles, which results in failure of linters check https://review.opendev.org/c/openstack/openstack-ansible/+/79569015:11
jamesdenton:thumbsup:15:12
spateljamesdenton ironic question15:13
opendevreviewJeremy Stanley proposed openstack/openstack-ansible stable/ocata: Prepare for stable/ocata EOL  https://review.opendev.org/c/openstack/openstack-ansible/+/82250115:13
spatelin my dc i already have PXE vlan for kickstart. can i use same vlan for ironic pxe? 15:14
noonedeadpunkso let's merge this one ^15:14
fungiassuming it passes of course15:14
noonedeadpunkand get done with ocata finally15:15
spatelI am thinking i should shutdown older pxe but that is not going to happen soon i am thinking show i can run both together 15:15
jamesdentonspatel let's hold off on that convo15:15
spatelcopy that15:15
fungiper discussion in #opendev, odds are the new failures on stable/ocata are due to that branch already reaching eol and getting deleted from other repositories15:15
noonedeadpunkfungi: I wonder if we need noop for gates?15:15
fungii left in one template for a job which seems to be passing15:15
fungihopefully publish-openstack-sphinx-docs includes what i think it does there15:16
fungii'm checking now15:16
fungiyeah, it's running build-openstack-sphinx-docs in check so should do the same in gate15:17
noonedeadpunkyeah, at least it does in master, indeed)15:17
fungithat's the job 795690 was still able to succeed15:17
noonedeadpunkthanks for helping!15:18
fungiwell, by "it's running" i mean i can see it in progress in the status page15:18
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/ocata: Switch Ocata to EOL  https://review.opendev.org/c/openstack/openstack-ansible/+/79569015:18
*** akahat|ruck is now known as akahat|dinner15:18
noonedeadpunkok, then we can probably talk about centos stuff :)15:19
fungiand the status page indicates that ^ since rebase is now running just that one job as well15:19
noonedeadpunkas for Y we need to have py3.8 for ansible and for venvs15:20
noonedeadpunkwhich leads us to missing libselinux python bindings at very least15:20
noonedeadpunkjrosser_: epel seems better now for centos9 stream btw! https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/Packages/15:21
noonedeadpunkincluding systemd-netwrokd :)15:21
noonedeadpunkand as you might all know py3.6 EOLing in a day or so. I guess at the end we will build libselinux for python from scratch... I'd hate doing that though, but no sure there's much choice here15:23
fungiare the prebuilt packages for 3.6 going to disappear?15:24
noonedeadpunkno, I don't think so15:24
fungior you mean so that you can use newer python3-libselinux versions in the future15:24
noonedeadpunkI even not sure if they would dissapear fro pypi15:24
fungithe old versions wouldn't unless their authors explicitly hid/removed those15:25
noonedeadpunkSo if we want to run ansible-core 2.12, which requires py3.8, then we have to get somehow python3.8-libselinux15:25
noonedeadpunkwhich is not provided by centos 8-stream15:26
fungialso if the maintainers of that project declare requires_python>=3.7 then pip should just pick the newest version which still declared support for 3.615:26
noonedeadpunkand redhat explicitly said they won't15:26
opendevreviewMerged openstack/openstack-ansible stable/ocata: Prepare for stable/ocata EOL  https://review.opendev.org/c/openstack/openstack-ansible/+/82250115:26
fungiout of curiosity are you testing 3.8 because the pti says you should? because it actually says 3.6 and 3.9, doesn't mention 3.815:27
noonedeadpunkwell, mostly because ubuntu 20.04 shipped with 3.815:28
fungiyep, that makes sense then15:28
noonedeadpunkand we don't build pyenv right now as then we would need to build pretty much of pre-packaged stuff15:28
noonedeadpunkso we're trying to leverage what distros ship15:28
fungi(though you can also use 3.9 on ubuntu 20.04 lts, it's just not the default python3)15:29
noonedeadpunk(for debian it's 3.9)15:29
noonedeadpunkoh ,well...15:29
fungicurrently focal includes python3.9 (3.9.5-3ubuntu0~20.04.1) if you want to install it15:30
noonedeadpunkI wonder if they have python3.9 lxc binding hehe15:30
noonedeadpunkbut yeah you're right15:30
noonedeadpunkwe might indeed want to run py39 for focal15:30
fungipython3-lxc (1:3.0.4-1ubuntu6) requires python3 >= 3.8~ << 3.9, i don't see a separate build if it for 3.9 on focal15:31
noonedeadpunkI actually never looked how much projects are already running tests against 3.915:31
fungiso yeah, that could be a blocker15:31
noonedeadpunkbut worth looking anyway, maybe there's smth in UCA for instance...15:33
noonedeadpunkbut feels like indeed we will just run default py version there15:35
noonedeadpunkand with 22.04 it will be 3.9 or 3.10 maybe?15:35
fungi3.10 as far as i know15:37
fungithere's a 3.10.1 backport due to land in focal-updates any day now according to motu15:37
noonedeadpunkoh, that's nice actually15:38
noonedeadpunkI still can't get used to that short life period of python versions after 2.7 :D15:38
fungithey didn't want to backport 3.10.0 to focal and were waiting for 3.10.1 to become available, which released a couple of weeks ago15:38
opendevreviewMerged openstack/openstack-ansible stable/ocata: Switch Ocata to EOL  https://review.opendev.org/c/openstack/openstack-ansible/+/79569015:38
noonedeadpunknice! ^15:39
fungicongrats! out with the old, in with the new15:39
noonedeadpunkyeah, we haven't eol-ed stuff for a while15:43
*** akahat|dinner is now known as akahat|ruck15:45
noonedeadpunk #endmeeting15:51
noonedeadpunk#endmeeting15:51
opendevmeetMeeting ended Tue Dec 21 15:51:39 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-21-15.00.html15:51
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-21-15.00.txt15:51
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-12-21-15.00.log.html15:51
jamesdentonspatel i would recommend not overlapping the two PXE environments. 15:54
spatelok 15:54
spateli have to spun up new vlan then 15:55
jamesdentonon the ironic side, best i can tell, is that without any sort of ML2 driver or external automation, you're looking at needing a 'flat' setup where cleaning, provisioning, inspection, and post-deployment (i.e. tenant) use will occur on the same vlan/network15:55
spatelhmm 15:56
spateli am planning to play on VMware so i can do quick POC how does vlan and networking will look 15:57
jamesdentonsure15:57
spateljamesdenton quick question related my neutron-server memory consumption issue, look at this output and tel me what is wrong? - https://paste.opendev.org/show/811805/15:57
spatelwhy i have duplicates proc, does it looks ok ? 15:57
jamesdentoni use the 'neutron' setup w/ networking-generic-switch plugin, so the cleaning, provisioning, inspection networks are all different neutron provider networks, and the switchport config is managed automatically.15:57
spateljamesdenton could you please blog that how about how do you running ironic :) 15:58
jamesdentonyeah, i'll get there :)15:58
spatel+115:58
jamesdentonmultiple api workers and rpc workers. looks normal15:59
spatelhmm  ok, i thought i have something weird going on16:00
jamesdentonin later releases you will see that as 'neutron-server: api worker'16:00
spatelmy neutron chewing up all 128GB memory in 2 week :(16:00
jamesdentonthat's what cron is for16:00
jamesdenton:D16:00
spatelThat is what i am planning to setup.. to kick it every week 16:01
jamesdentonwhatever it takes16:01
spateli dont' have bandwidth to debug :(16:01
jamesdentonwell you are also 5 releases behind16:01
jamesdentonso who knows16:01
jamesdenton(maybe not worth the efforts)16:02
spatelyes totally, i have Queens and wallaby running with same number of compute but they never ever hit more than 4gb16:02
*** dviroel|lunch is now known as dviroel16:07
jrosser_noonedeadpunk: epel/9 missing lsyncd :(16:10
noonedeadpunklast lsyncd release was 4 years ago....16:33
noonedeadpunkbut github seems kind of alive16:33
noonedeadpunkmost commits are kind of weeks ago16:33
noonedeadpunkI bet we had build from source code one day...17:02
noonedeadpunkhttps://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/747911/1/tasks/repo_install_lsyncd.yml17:06
noonedeadpunkso we had actually same for centos 8:)17:07
noonedeadpunkI wonder if it makes sense to reach epel folks and ask if they plan to provide lsyncd :D17:07
noonedeadpunkwe implemented with https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/70953217:08
noonedeadpunkshould be relatively easy to return that code back17:09
noonedeadpunkjrosser_: um, have you made a dnm patch for centos 9? As I can't find it for some reason...17:19
noonedeadpunkor you just played locally?17:20
*** sshnaidm is now known as sshnaidm|afk17:34
noonedeadpunkthere are interesting stuff about epel I didn't know...17:45
noonedeadpunkSo they build everything from scratch and maintainers should explicitly say they want their package to be in epel 9 for exaple before they will publish it17:45
noonedeadpunkSo the process involve pinging maintainers to publish their packages with each new release17:46
noonedeadpunkhttps://docs.fedoraproject.org/en-US/epel/epel-package-request/17:46
noonedeadpunkand that's why we saw just iptables at start :D17:46
noonedeadpunkI actually created request for lsyncd https://bugzilla.redhat.com/show_bug.cgi?id=203469317:46
noonedeadpunkand even regardles lsyncd is packaged for fedora 36, it might be absent for centos 9 epel even though centos 9 forked from fedora 34 (which also have lsyncd https://src.fedoraproject.org/rpms/lsyncd)17:48
jrosser_noonedeadpunk: i just played locally but it failed on boostrap-aio due to systemd-networkd so there were really no patches to make18:28
jrosser_gave up very quickly18:28
noonedeadpunkyeah, I do recall that... 18:33
jrosser_we're also missing the copr repo for lxc18:37
jrosser_but i expect we could get a metal deployment done with building lsync from source18:37
noonedeadpunkwell, for epel 8 it's not that bad lxc https://src.fedoraproject.org/rpms/lxc18:39
noonedeadpunklet me try to create another bug report :)18:40
noonedeadpunklet's see where this would lead us https://bugzilla.redhat.com/show_bug.cgi?id=203470918:44
*** gmann is now known as gmann_afk19:51
*** dviroel is now known as dviroel|afk19:53
spateli like the idea of using lsyncd for source, we should use same method of both ubuntu and centos/el 20:26
spatelthese guys keep changing stuff on each release 20:26

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