Wednesday, 2022-07-20

*** dviroel|out is now known as dviroel00:33
*** dviroel is now known as dviroel|out01:00
*** ysandeep|out is now known as ysandeep01:52
opendevreviewMerged openstack/openstack-ansible stable/wallaby: Fix facts gathering for zun  https://review.opendev.org/c/openstack/openstack-ansible/+/84963101:56
*** ysandeep is now known as ysandeep|afk03:23
noonedeadpunkmornings07:58
noonedeadpunkand also bump mariadb version as https://zuul.opendev.org/t/openstack/build/97fee39bdbff41868a608475b50dc3db/log/job-output.txt#1243908:04
noonedeadpunkhm, seems my previous message was lost08:04
noonedeadpunkand, I was talking that if we want to backport https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/850350  we also need to backport rally 08:05
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_rally stable/ussuri: Control rally-openstack installed version  https://review.opendev.org/c/openstack/openstack-ansible-os_rally/+/85047708:06
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_rally stable/ussuri: Control rally-openstack installed version  https://review.opendev.org/c/openstack/openstack-ansible-os_rally/+/85047708:08
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_rally stable/ussuri: Control rally-openstack installed version  https://review.opendev.org/c/openstack/openstack-ansible-os_rally/+/85047708:09
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: Set minimum and maximum microversions for manila api  https://review.opendev.org/c/openstack/openstack-ansible/+/85047808:23
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: Set minimum and maximum microversions for manila api  https://review.opendev.org/c/openstack/openstack-ansible/+/85047808:23
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_manila stable/xena: Create backends when running against manila_share  https://review.opendev.org/c/openstack/openstack-ansible-os_manila/+/84799308:23
jrossermorning08:49
damiandabrowskihi!08:51
opendevreviewMerged openstack/openstack-ansible-galera_server stable/xena: Bump mariadb version.  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/84743509:27
opendevreviewMerged openstack/openstack-ansible-os_tempest stable/xena: Drop tripleo c7 job definition  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/84997709:28
opendevreviewMerged openstack/openstack-ansible-os_tempest stable/wallaby: Remove tripleo jobs from stable/wallaby  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/84997009:28
opendevreviewMerged openstack/openstack-ansible-os_tempest stable/victoria: Remove tripleo jobs from stable/victoria branch  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/84997109:34
opendevreviewMerged openstack/openstack-ansible stable/wallaby: Switch ARA report type from html to database for openstack-ansible jobs  https://review.opendev.org/c/openstack/openstack-ansible/+/84981209:53
opendevreviewMerged openstack/openstack-ansible stable/victoria: Switch ARA report type from html to database for openstack-ansible jobs  https://review.opendev.org/c/openstack/openstack-ansible/+/84979810:05
*** ysandeep|afk is now known as ysandeep10:14
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_rally stable/ussuri: Control rally-openstack installed version  https://review.opendev.org/c/openstack/openstack-ansible-os_rally/+/85047710:23
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_rally stable/ussuri: Control rally-openstack installed version  https://review.opendev.org/c/openstack/openstack-ansible-os_rally/+/85047710:24
*** anbanerj is now known as frenzy_friday11:33
*** dviroel|out is now known as dviroel11:34
*** anbanerj is now known as frenzy_friday11:58
opendevreviewMarc Gariépy proposed openstack/openstack-ansible-rabbitmq_server stable/ussuri: Use cloudsmith repo for rabbit and erlang  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/85035012:05
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server stable/xena: Don't restrict haproxy tunable options  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/85048013:09
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon stable/xena: Fix ALLOWED_HOSTS  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/84800413:09
noonedeadpunkI'm not sure if it's good idea to backport https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/85048013:11
noonedeadpunkbut defining tune.maxrewrite is required13:11
noonedeadpunkmaybe I should instead just push simple patch to add tune.maxrewrite 1280 as a default thing...13:12
mgariepyjrosser, with gluster if i started aio with 1 repo and want to scale it to 3, was that supposed to work ?13:29
jrosserthats an interesting question13:29
mgariepyhaha13:29
jrosserso it doesnt need gluster at all in a single repo server setup, but it always deploys it even with just one13:30
mgariepyhttps://paste.openstack.org/show/bdcpnRs8LlRUTjaTprPC/13:30
jrosseri've tried replacing a repo server when there are 3 and that should be ok13:31
mgariepyyeah but adding one after is kinda.. broken now.13:31
jrosserwell it may never have worked13:31
jrosserthe gluster role i wrote is very simple13:32
mgariepyyeah, seems like we cannot add peers when there is already a volume.13:32
jrosserthere is some data about the cluster stored in /var/<somewhere>13:32
jrosserand there is a uuid that represents the cluster13:32
jrosseras the error is "is either already part of another cluster" i might look at that first13:33
jrossertbh i expect that the playbook just can't handle this situation13:34
jrosserbut it doesnt look too difficult https://www.cyberciti.biz/faq/howto-add-new-brick-to-existing-glusterfs-replicated-volume/13:34
*** ysandeep is now known as ysandeep|afk13:37
mgariepyok i'll take a look.13:38
jrossermgariepy: you also need to be careful googling for how to do gluster stuff because it's changed over time in the later versions13:38
mgariepywell it's AIO ahha13:38
jrosseroh well i mean the commands may have "modern" and old ways to do things13:39
jrosserit took a lot of effort to find proper docs for this https://github.com/openstack/openstack-ansible-plugins/blob/master/roles/glusterfs/tasks/main.yml#L129-L14113:39
mgariepyit was only missing the correct peer probe i think13:40
jrosserright - looking at the code it feels like it might be really close already13:40
mgariepyyeah13:40
mgariepyneeds to do peer probe from the working node intead of the other.13:41
mgariepynot too far :D13:41
jrosserdelegate_to: <any-host-except-this-one>13:41
jrosser^ hmm13:41
mgariepyhaha yep13:42
mgariepyit needs a host already in the cluster to probe the other.13:42
mgariepythanks for your help. i'll patchup the role to fix this usecase13:43
jrosserexcellent - no problem13:44
jrosseryou can probably find that reliably in the output of https://github.com/openstack/openstack-ansible-plugins/blob/master/roles/glusterfs/tasks/main.yml#L122-L12713:44
*** ysandeep|afk is now known as ysandeep14:13
mgariepyjrosser, was there a reason why you used the last_play_host? 15:03
mgariepysince all the tasks are ran on all node one by one, the first one would have been quite equivalent15:03
jrosserare they run one by one?15:04
jrosseri think its not serial15:04
mgariepythey run in parrallel i thing15:04
mgariepythink*15:04
mgariepymy point being that when executing the task that add gluster peers they are all at the same step./15:06
mgariepyeither one would be ok to use at this point. you only want the ones with the service up.15:07
mgariepytasks are run on each node one tasks a the time**15:10
opendevreviewMarc Gariépy proposed openstack/openstack-ansible-plugins master: Fix gluster play_hosts  https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/85054015:14
mgariepyjrosser, something like this ^^15:14
mgariepythis way i don't have to parse the output of the commands and it works to grow from 1 to 3 in affinity, i guess it would also work if you scale up your infra servers from 1 to 3. since the inventory would probably keep the order they were added.15:20
jrosseroh sorry i'm confusing what you said there15:27
jrosseri suspect what happened here was i was originally writing the role when the gluster deployment happened in the same play as the rest of the repo server deployment15:27
jrosserwhich is always serial=115:27
jrosserbut now it's not like that at all15:28
jrosserso it should not matter at all if it's first or last host in the play, you are right15:28
mgariepywould it matter on switching from not gluster to gluster?15:29
jrosseri would guess not - as the gluster stuff is done as one play before the repo stuff starts another play15:51
jrosserunfortunatley the upgrade job that tests that will be on stable/yoga15:52
mgariepywe should backport anyway :)15:52
jrosserjamesdenton: have you ever used networking-generic-switch with nxos?15:55
jamesdentoni think so, but been a while. actively using with a catalyst15:55
jamesdentonnow that i think about it, might've only been arista and not nexus15:56
jamesdentonbut either way, i think cisco driver will handle nxos15:56
jrosseryeah, i was looking at the lldp autodiscovery15:58
jrosserand that looks kind of nice for auto-enrolment15:58
jrosserhowever /o\ nxos gives a unique chassis id per port which is super unhelpful15:59
jrosserso setting ngs_mac_address isnt possible https://docs.openstack.org/networking-generic-switch/latest/configuration.html 16:00
jamesdentoni hadn't seen anything about lldp auto discovery16:02
jrosseri think that ngs_mac_address lets you set the switch mac address, which inspector then finds and reports back16:03
jrosserso you don't have to initially configure that at all when making a new node16:03
jamesdentonahhh gotcha16:04
jrosseror rather, if you've defned a bunch of switches up front by their mac address, it can select the right one based on the info from inspector16:04
*** dviroel is now known as dviroel|lunch16:06
jamesdentonas in, it would auto-populate local-link-connection based on lldp info during discovery16:06
admin1noonedeadpunk, cherry pick of that patch worked perfectly for the mysql upgrade, and the issue of not enough hosts is gone 16:06
jamesdentoni haven't looked at that; we haven't used inspector much up to this point16:06
jrosserjamesdenton: yes i think thats what it should do16:09
jamesdentonseems like there could be a chicken/egg situation there, especially if you're using NGS to tweak the VLAN and drop it into the 'inspection' vlan. the baremetal port would need to have those switchport properties defined already (i would think)16:11
*** ysandeep is now known as ysandeep|out16:11
jrosserwell - lldp should work regardless of the VLAN configuration i think?16:13
jrosserit's a different protocol so kind of 'out of band'16:14
jamesdentontrue, but you still need to be in the PXE vlan16:14
jrosserhmm yes16:15
jamesdentonFWIW, this Cisco catalyst also has hardware MAC per switchport, but the switch itself has a base MAC identified in 'show ver'. That's the one I use; I need to see what LLDP returns16:18
jrosserwell this is super early days - we are just starting to mess with this16:18
jrosser`sudo tcpdump -i ens1f0 ether proto 0x88cc -vv`16:18
jrossercompare that between two hosts16:18
anskiyjrosser: is cisco's proprietary LLDP known as CDP dead? Or you're just not all cisco?16:20
jrosserit has both LLDP and CDP16:21
jamesdenton@jrosser Looking at a 9372PX here, I see what you mean16:49
jamesdentonchassis id is unique per port.16:50
jrosserit’s odd isn’t it16:50
jamesdentonI could see that being problematic if you use inspector to auto-populate that16:50
jamesdentonyes, seems odd16:52
jamesdentonhttps://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/102x/configuration/system-management/cisco-nexus-9000-series-nx-os-system-management-configuration-guide-102x/m-configuring-lldp-10x.html16:53
jamesdentonBeginning with Cisco NX-OS Release 10.2(3)F, the Correctly Advertise LLDP Chassis-ID feature introduces a new global configuration command—lldp chassis-id switch —to advertise the switch chassis MAC address instead of the port MAC address, that is, all the ports will publish only the MAC address of the switch chassis. This feature is supported on all Cisco Nexus 9000 series platform switches.16:54
jamesdentonthere you go16:54
jamesdentonJust Upgrade™ :D16:54
jrosserargh17:10
jrosserwhat they actually meant to say is "This feature is supported on all Cisco Nexus 9000 series platform switches which can run nxos 10.x"17:11
jrosseri wonder if thats fixed in a newer 9.x17:12
*** dviroel|lunch is now known as dviroel17:23
*** dviroel is now known as dviroel|afk19:34
opendevreviewMerged openstack/openstack-ansible-os_neutron stable/xena: Allow to provide custom configuration for VPNaaS  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/84806621:01

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