Wednesday, 2024-01-10

gongysh_hi02:23
jeffrey4l_gongysh_ welcome 02:23
gongysh_jeffrey4l_: test02:23
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/90496303:02
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/90496303:11
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove failed to discover swift endpoint  https://review.opendev.org/c/openstack/kolla-ansible/+/90496803:49
opendevreviewDr. Jens Harbott proposed openstack/kolla-ansible master: CI: improve get_logs.sh  https://review.opendev.org/c/openstack/kolla-ansible/+/87052106:23
opendevreviewMichal Nasiadka proposed openstack/kolla master: openvswitch: Add ovs_wrapper for handling TERM  https://review.opendev.org/c/openstack/kolla/+/90518906:59
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: openvswitch: Stop using intermediate scripts  https://review.opendev.org/c/openstack/kolla-ansible/+/90511707:00
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: openvswitch: Stop using intermediate scripts  https://review.opendev.org/c/openstack/kolla-ansible/+/90511707:00
opendevreviewMichal Nasiadka proposed openstack/kolla master: openvswitch: Add ovs_wrapper for handling TERM  https://review.opendev.org/c/openstack/kolla/+/90518907:05
opendevreviewMichal Nasiadka proposed openstack/kolla master: openvswitch: Add ovs_wrapper for handling TERM  https://review.opendev.org/c/openstack/kolla/+/90518908:09
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: fail when systemd unit fails to stop  https://review.opendev.org/c/openstack/kolla-ansible/+/89178108:10
opendevreviewMartin Hiner proposed openstack/kolla-ansible master: Add container engine migration scenario  https://review.opendev.org/c/openstack/kolla-ansible/+/83694110:02
opendevreviewMerged openstack/kolla-ansible stable/2023.2: Fix Nova scp failures on Debian Bookworm  https://review.opendev.org/c/openstack/kolla-ansible/+/90508410:02
*** ironfoot_ is now known as ironfoot11:04
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: neutron: Add higher graceful timeout for server and ovs agent  https://review.opendev.org/c/openstack/kolla-ansible/+/90520811:11
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: haproxy: Use -f configdir instead of for and xargs  https://review.opendev.org/c/openstack/kolla-ansible/+/90512111:20
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: mariadb-clustercheck: Use socat wrapper  https://review.opendev.org/c/openstack/kolla-ansible/+/90513111:21
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: openvswitch: Stop using intermediate scripts  https://review.opendev.org/c/openstack/kolla-ansible/+/90511711:21
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: fail when systemd unit fails to stop  https://review.opendev.org/c/openstack/kolla-ansible/+/89178111:21
opendevreviewJake Hutchinson proposed openstack/kolla-ansible master: Ironic parameter rework and default NTP server  https://review.opendev.org/c/openstack/kolla-ansible/+/89303113:21
SvenKieskeo/14:01
SvenKieskeum14:01
mnasiadka#startmeeting kolla14:01
opendevmeetMeeting started Wed Jan 10 14:01:22 2024 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'kolla'14:01
mnasiadka#topic rollcall14:01
mnasiadkao/14:01
SvenKieskeo/14:01
SvenKieske:D14:01
mmalchuko/14:02
mhinero/14:02
bbezako/14:02
janguttero/14:03
mnasiadka#topic agenda14:03
mnasiadka* Review action items from the last meeting14:03
mnasiadka* CI status14:03
mnasiadka* Release tasks14:03
mnasiadka* Regular stable releases (first meeting in a month)14:03
mnasiadka* Current cycle planning14:03
mnasiadka* Additional agenda (from whiteboard)14:03
mnasiadka* Open discussion14:03
mnasiadka#topic CI status14:03
mnasiadkaI think the CI is overall green, with some amber here and there14:03
mnasiadkabut haven't seen any total breakage14:04
mnasiadka#topic Release tasks14:04
mnasiadkaWe've reverted the branch changes - so we're building from master now and running master in kolla-ansible14:04
mnasiadkaWhat we omitted, is that we use master a-c-k on stable/2023.2 branch14:04
mnasiadkaany volunteers to fix this?14:05
mmalchukI can try14:06
mnasiadkaok then14:06
mnasiadka#topic Regular stable releases (first meeting in a month)14:07
mnasiadkaAnybody happy to follow the regular stable releases procedure after mmalchuk fixes a-c-k in 2023.2?14:07
bbezaksure14:07
bbezakcan do14:08
mnasiadkafantastic14:10
mnasiadka#topic Current cycle planning14:10
mnasiadkaLet me check if we have Caracal priorities populated on the whiteboard14:10
mnasiadkahttps://etherpad.opendev.org/p/KollaWhiteBoard#L20714:10
mnasiadkanope, only Kayobe it seems14:10
SvenKieskeafaik there should be some stuff there, I fuzzily remember I wanted to pester the infra team with stuff to mirror?14:11
SvenKieskeshould we add stuff from https://etherpad.opendev.org/p/kolla-caracal-ptg#L111 ? not sure about the process here14:12
mnasiadkaYes, I'll populate it14:12
mnasiadkaBut not now, for the sake of the meeting14:12
mnasiadkaAnything anybody is working on?14:12
SvenKieskeokay, I see it. awesome :)14:12
mnasiadkaMaybe the quorum queues backports?14:12
SvenKieskeyeah I hope I get to that in the next weeks, I also have read your suggestions on changing things a bit14:13
SvenKieskejust currently swamped with back-from-vacation and other stuff14:13
mnasiadkaSure :)14:13
mnasiadkaOk, I see nothing fancy14:15
mnasiadkalet's go forward then14:15
mnasiadka#topic Additional agenda (from whiteboard)14:16
mnasiadkafrickler is not around, but some topics from him14:16
mnasiadkaI guess we'll talk about them next week14:16
mnasiadkaseems nothing else on the whiteboard topics14:17
mnasiadka#topic Open discussion14:17
mnasiadkaAnybody anything?14:17
SvenKieskeI worked on shellcheck end of last year, if someone is also interested14:18
mmalchuksimple question14:18
mmalchukcan we create backports along with master change14:18
mmalchukwhy cores show bad practice?14:19
mmalchukkevko what do you think?14:19
mnasiadkayou can create backports when you want, but to merge them we need the commit id from master14:20
mmalchukso creating bunch of reviews is fine?14:20
mmalchukok then, thats all from me14:21
mnasiadkammalchuk: what do you mean by creating bunch of reviews?14:24
mnasiadkacreating backports when master is not merged yet?14:24
mnasiadkaI agree it's an antipattern, and you need to refresh those backports after master gets merged14:24
mnasiadkaAnd probably it creates some mess, but core's should always check if change is merged in master already14:25
mnasiadkaseems we're done with the meeting14:26
mmalchukmnasiadka too many reviews in gerrit without WIP14:26
kevkoHi14:26
mnasiadkaAh, just last but not least - I will be off for the next two weeks - bbezak gladly agreed to manage the meetings14:26
mnasiadkaso please behave :)14:26
mmalchukafter master changes the same count of reviews in stable branches again and again14:26
mmalchukwith only source commit hash changed14:27
mmalchukthats all14:28
mmalchukmnasiadka thanks and good weekend14:28
mnasiadkakevko: the main ask is to create backports AFTER the master patch is merged14:29
mnasiadkaI agree sometimes we backport something to check if it passes upgrade jobs or whatever14:29
mmalchukyep14:29
SvenKieskeyeah, sometimes it would be nice to be able to merge backports faster. well it is what it is.14:29
mnasiadkabut that should be rather exception14:29
mmalchukSvenKieske not in all cases)14:29
mnasiadkayes, a nice reminder to core reviewers to have a look on backports section of the dashboard14:29
mnasiadkaok, enough for today14:30
mnasiadkaThank you all for coming!14:30
mnasiadka#endmeeting14:30
opendevmeetMeeting ended Wed Jan 10 14:30:41 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:30
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-01-10-14.01.html14:30
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-01-10-14.01.txt14:30
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-01-10-14.01.log.html14:30
wuchunyanghi, cores,  could you add the trove patch to review list ?14:31
mnasiadkacan you post a link?14:31
mmalchukwuchunyang it on review14:32
wuchunyangmmalchuk  ok, thanks. 14:32
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove failed to discover swift endpoint  https://review.opendev.org/c/openstack/kolla-ansible/+/90496814:35
mmalchukwuchunyang please post the link here as mnasiadka say to speedup review a bit14:36
wuchunyangok no problem.14:36
wuchunyanghttps://review.opendev.org/c/openstack/kolla-ansible/+/904968    https://review.opendev.org/c/openstack/kolla-ansible/+/904963/4  14:37
wuchunyangthese two patches are easy to review. we should merged it and back-port to  stable branches. 14:37
mnasiadkaI see logging fix is sneaked in the first one, but I guess we can survive ;)14:38
mmalchukI think it can be easily added back)14:39
mnasiadkawuchunyang: in the second one, we only have quorum queues in master and 2023.2, can you split this into two patches - with quorum queues (so L13 to L15 from https://review.opendev.org/c/openstack/kolla-ansible/+/904963/4/ansible/roles/trove/templates/trove-guestagent.conf.j2) in a separate patch stacked on top? so it's easier to backport the first one all the way to yoga, and quorum only to 2023.2?14:40
wuchunyangyes, logging fix also is needed to back-port, so i put them  together14:40
wuchunyangmnasiadka ok, i will check it on yoga. then divide them  to two patches.14:42
opendevreviewMaksim Malchuk proposed openstack/kolla-ansible stable/2023.2: Switch openstack.kolla to correct branch  https://review.opendev.org/c/openstack/kolla-ansible/+/90522714:44
mmalchukmnasiadka done ^^^14:44
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/2023.2: [2023.2 only] Switch openstack.kolla to correct branch  https://review.opendev.org/c/openstack/kolla-ansible/+/90522714:44
mnasiadkathanks14:45
mnasiadkabbezak: can you have a look at first wuchunyang's patch?14:46
bbezakwilldo14:48
bbezakin spare moment :)14:48
wuchunyanghello cores. another question. i saw  kolla pushes images to "kolla" organization in docker hub, how do we apply a "trove" organization in docker hub ? 14:52
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq[1]  https://review.opendev.org/c/openstack/kolla-ansible/+/90496314:53
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/90496314:58
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/90496315:00
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove guest agent failed to connect rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/90497215:00
wuchunyangmnasiadka bbezak  hi, I divided into two patches. https://review.opendev.org/c/openstack/kolla-ansible/+/904963/7  https://review.opendev.org/c/openstack/kolla-ansible/+/904972/115:02
mmalchukwuchunyang dockerhub not used anymore15:14
mmalchukhttps://quay.io/15:14
mmalchukhttps://quay.io/organization/openstack.kolla15:15
mmalchukis the right place for images15:15
wuchunyangmmalchuk  i saw kolla ci uses both of dockerhub and quay.io. 15:15
bbezakwuchunyang: maybe alter the name of second commit, as it is the same as previous one15:15
mmalchukwuchunyang dockerhub used for old images15:16
wuchunyangbbezak  can i just add  1 and 2 suffix ? 15:16
wuchunyangmmalchuk how do we apply a quay.io organization?  in trove project, we also need to build 4 docker images. but i don't know where to push. 15:17
mmalchukits better add something like (for stable branches)15:17
wuchunyangmmalchuk ok, no problem 15:17
mnasiadkawell, docker hub publishes seem to work now, but we publish weekly15:18
mmalchukwuchunyang just use it as the namespace15:18
mnasiadkawhile we publish daily to quay.io15:18
wuchunyangi want to know who is the owner of the  kolla docker hub organization ?15:18
mmalchukkolla project15:19
mnasiadkame15:19
mnasiadka:)15:19
mmalchukwuchunyang you shouldn't push images to quay.io yourself. just create right commits in the kolla project15:20
mnasiadkawuchunyang: basically register an account and open a free public project15:21
wuchunyangmnasiadka   you use your own docker account to apply a docker-sponsored  organization?  right ?15:21
mnasiadkathere is something called free team on Docker Hub15:22
wuchunyangmmalchuk not related to kolla images. just trove itself.  as i am also  trove PTL,  i'd like to make it more easy to use.15:22
mnasiadkabut Docker Hub has pull limits15:22
mnasiadkawuchunyang: https://www.docker.com/developers/free-team-faq/15:22
mnasiadkaso you can't sign up now for a free team15:23
wuchunyangwe only build 4-8 images in trove project, doesn't  the pull limits will affect us?15:23
mmalchukwuchunyang youre interesting how to create your own CI and push images? ok then15:24
mnasiadkawuchunyang: no, pull limit is only for pulling, not pushing ;)15:24
wuchunyangmmalchuk yes, i don't know how to do, so i read  the kolla ci code .Lol15:24
mmalchukwuchunyang you can ask help in #opendev channel15:25
mmalchukthere are more CI involved peoples15:25
mmalchukor even #opendev-infra15:26
wuchunyangok, i will ask them for help.15:27
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove failed to connect rabbitmq(stable/branch)  https://review.opendev.org/c/openstack/kolla-ansible/+/90496315:29
wuchunyangmnasiadka  hi  https://github.com/openstack/kolla/blob/master/.zuul.d/base.yaml#L19  this is your individual account ? 15:32
mnasiadkawuchunyang: that is a robot account token tied to the free team15:32
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Fix trove failed to connect rabbitmq(2023.2 branch)  https://review.opendev.org/c/openstack/kolla-ansible/+/90497215:33
wuchunyangmnasiadka  I thought about it for a while, and I thought it would be more appropriate to use quay.io 15:34
mnasiadkawuchunyang: especially that it seems you can't apply for Docker Free Team anymore15:34
wuchunyangbecause quay.io doesn't have pull limit problem15:34
mnasiadkawuchunyang: register an account, create an organisation, create a robot account inside that org for CI pushes - add secrets to zuul.yaml - and should work ;)15:35
wuchunyangyou mean  quay.io ? 15:36
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: fail when systemd unit fails to stop  https://review.opendev.org/c/openstack/kolla-ansible/+/89178115:47
opendevreviewMerged openstack/kolla-ansible master: Enable the Fluentd Plugin Systemd  https://review.opendev.org/c/openstack/kolla-ansible/+/87598316:00
opendevreviewJake Hutchinson proposed openstack/kolla-ansible master: Ironic parameter rework and default NTP server  https://review.opendev.org/c/openstack/kolla-ansible/+/89303117:02
opendevreviewMerged openstack/kolla-ansible stable/2023.2: [2023.2 only] Switch openstack.kolla to correct branch  https://review.opendev.org/c/openstack/kolla-ansible/+/90522718:52
greatgatsbyhas anyone experienced crashing computes with lots of soft-lockups?  We're running xena via kolla-ansible.  We've seen this across multiple deployments and hardware profiles.18:54
greatgatsbysorry, we're on yoga, brain fart19:32
*** jph4 is now known as jph23:48

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