Wednesday, 2021-06-23

opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Modernize the swift role  https://review.opendev.org/c/openstack/kolla-ansible/+/79749802:52
opendevreviewMerged openstack/kolla-ansible stable/wallaby: Add missing region_name in keystoneauth sections  https://review.opendev.org/c/openstack/kolla-ansible/+/79747702:55
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Remove unused region_name option  https://review.opendev.org/c/openstack/kolla-ansible/+/79756004:55
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Modernize the swift role  https://review.opendev.org/c/openstack/kolla-ansible/+/79749805:00
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: horizon: Support custom themes  https://review.opendev.org/c/openstack/kolla-ansible/+/76136405:48
*** rpittau|afk is now known as rpittau07:07
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: horizon: Support custom themes  https://review.opendev.org/c/openstack/kolla-ansible/+/76136407:14
jingvar_I've added # Server inventory for Bifrost. and have servers.yaml into Bifrost container, but I don't have automatic enroll this nodes, barematal node list is empty -  if run manual enroll as described in Bifrost docs - nodes appear07:19
lichunexcuse me, I ask one question.08:06
lichunwhen I run "kolla-ansible deploy", the target host report "Not continuing with pull after error: context canceled"08:08
lichunthen, The pull session cancelled. how do I fix it?08:09
opendevreviewMark Goddard proposed openstack/kolla stable/wallaby: tox: Use allowlist_externals instead of whitelist_externals  https://review.opendev.org/c/openstack/kolla/+/79757408:09
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Modernize the swift role  https://review.opendev.org/c/openstack/kolla-ansible/+/79749808:15
mgoddardhi lichun, I haven't seen that error before08:18
mgoddardlichun: you could check docker logs08:18
lichunmgoddard: there is no container yet.08:21
mgoddardlichun: I mean logs for the docker daemon08:21
mgoddardjingvar_: I have found someone who recently had this working08:22
mgoddardjingvar_: they will join shortly08:23
jingvar_great news08:25
lichunmgoddard: docker daemon no complaints anything. Could it be a internet problem?08:25
lichunmgoddard: I was wrong, dockerd complained "Pull session cancelled" and "Not continuing with pull after error: context canceled"08:29
luk4sHi jingvar_ 08:30
jingvar_Hi luk4s08:31
luk4sAre you looking for some examples on using static inventory in bifrost?08:32
jingvar_yes08:32
luk4sLet me dig out the config and commands. Give me couple of minutes08:33
jingvar_i have coorrect servers.yaml and can manully use it for enreoll inside bifrost08:34
jingvar_do you know what is command prompt - tc@box ? storage node has this strange message08:36
jingvar_it looks like tine.core but it happens in deploy phase 08:39
luk4sjingvar_, please see https://gist.github.com/m4ge/2d4070889a51d08ca5a98ec151dd6c9a for  sample configuration.08:51
jingvar_I have something like that , but without unnecessary parameters08:55
jingvar_uuid, properties, ipv4_address, 08:57
jingvar_question is why it doesnt work with bootstrp bifrost08:58
jingvar_to enroll baremetal you need driver=ipmi, ipmi_user, ipmi_password, ipmi_ip, and probably boot_mac 09:05
luk4sjingvar_, are you getting errors importing the servers.yml into bifrost?09:10
jingvar_Sorry, which step do you mean?09:11
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777209:12
jingvar_I have no errors09:12
luk4sSo you can import the static inventory into bifrost without any issue?09:12
jingvar_yes09:12
mgoddardsorry luk4s, I must have been behind on the state of jingvar_'s deployment09:13
luk4smgoddard, no worries :)09:13
mgoddardluk4s: at least you're setup on OFTC now :)09:14
jingvar_I't turn back few minutes09:15
opendevreviewMerged openstack/kolla-ansible stable/victoria: Add missing region_name in keystoneauth sections  https://review.opendev.org/c/openstack/kolla-ansible/+/79747809:16
opendevreviewMerged openstack/kolla-ansible stable/ussuri: Add missing region_name in keystoneauth sections  https://review.opendev.org/c/openstack/kolla-ansible/+/79747909:16
opendevreviewMerged openstack/kolla stable/wallaby: tox: Use allowlist_externals instead of whitelist_externals  https://review.opendev.org/c/openstack/kolla/+/79757409:16
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777209:16
luk4smgoddard, yup  all reconfigured and ready to go from now on09:17
opendevreviewMark Goddard proposed openstack/kolla-ansible master: magnum: Add CA certificate configuration for internal TLS  https://review.opendev.org/c/openstack/kolla-ansible/+/78106209:19
opendevreviewMerged openstack/kayobe stable/wallaby: Fix url to ansible site in kolla-ansible.rst  https://review.opendev.org/c/openstack/kayobe/+/79739209:33
opendevreviewMerged openstack/kayobe master: Remove outdated upgrade step  https://review.opendev.org/c/openstack/kayobe/+/79684809:35
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Use ansible_facts to reference facts  https://review.opendev.org/c/openstack/kolla-ansible/+/79127609:39
opendevreviewMark Goddard proposed openstack/kolla-ansible master: CI: Don't generate certificates before upgrade  https://review.opendev.org/c/openstack/kolla-ansible/+/79279309:40
jingvar_I'm here10:00
jingvar_I have correct servers.yaml (bacaue it works by manual run inside Befrost), but I don't have automatic enroll via kayobe seed service deploy, only deliverivng servers.yaml to Befrost10:03
jingvar_I will remove container and restart service deploy and collect logs10:05
wuchunyanghi, i refactored the swift role In the last few days, And now, the CI all pass. need cores to review.10:10
yoctozeptowuchunyang: hi; did you test upgrades?10:15
wuchunyangyoctozepto : yes, just smoke test. run passed.  i am not very sure the logic of rolling_upgrade 10:19
jingvar_service deploy full log here http://paste.openstack.org/show/806879/10:21
opendevreviewMerged openstack/kolla-ansible stable/victoria: Fix host bootstrap pkg removal on Debian  https://review.opendev.org/c/openstack/kolla-ansible/+/79739310:22
opendevreviewMerged openstack/kolla-ansible stable/ussuri: Fix host bootstrap pkg removal on Debian  https://review.opendev.org/c/openstack/kolla-ansible/+/79739410:23
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777210:27
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777210:30
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777210:32
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777210:34
jingvar_manual enroll is here http://paste.openstack.org/show/806880/10:43
mgoddardjingvar_: seed service deploy should not enroll nodes10:55
mgoddardjingvar_: possibly we need a new command to do it10:55
jingvar_hmm, but it brings servers.yaml 11:00
jingvar_starnge11:00
mgoddardjingvar_: yes. This whole flow has not really been designed11:02
mgoddardjingvar_: I would suggest that you work around the shortcomings of this approach and make it work. If you decide to go with kayobe we can look at how to improve it. It's on the backlog anyway11:03
jingvar_I ready to try your way with autodiscovery11:04
mgoddardok11:04
jingvar_could someone explain how do you do this11:05
mgoddardjingvar_: use ipmitool to boot from PXE & power on nodes11:10
jingvar_how to enable autodicovery mode11:30
jingvar_and what I'll see in baremetal node list? random names?11:31
jingvar_like MAAS do11:31
mgoddardjingvar_: the nodes will have no name by default, but we often setup inspector to use the switch LLDP port description to set node names11:34
mgoddardjingvar_: tbh, we are considering moving to an enrollment approach11:34
jingvar_After inspection, Are you manually rename nodes related to ansible inventory (controller0 , etc)11:36
mgoddardjingvar_: no, we use the approach I just mentioned11:37
opendevreviewMark Goddard proposed openstack/kayobe master: Support Ansible collections  https://review.opendev.org/c/openstack/kayobe/+/79749711:37
opendevreviewMichal Arbet proposed openstack/kolla-ansible stable/wallaby: Make rabbitmq cluster_partition_handling configurable  https://review.opendev.org/c/openstack/kolla-ansible/+/79757611:37
jingvar_do you have some deployment sricpt?11:37
jingvar_i don't undertand how works kayobe overcloud inventory discover 11:38
mgoddardjingvar_: https://www.stackhpc.com/ironic-idrac-ztp.html11:38
jingvar_it should link barematal node and ansible host11:39
mgoddardsome info about it there11:39
jingvar_I've read it. Thanks11:51
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Repalce auth_uri with www_authenticate_uri  https://review.opendev.org/c/openstack/kolla-ansible/+/79762512:10
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: Replace auth_uri with www_authenticate_uri  https://review.opendev.org/c/openstack/kolla-ansible/+/79762512:11
opendevreviewMark Goddard proposed openstack/kayobe master: Ubuntu: add upgrade jobs in CI  https://review.opendev.org/c/openstack/kayobe/+/79762612:12
opendevreviewPierre Riteau proposed openstack/kolla-ansible master: Replace auth_uri with www_authenticate_uri  https://review.opendev.org/c/openstack/kolla-ansible/+/79762512:23
opendevreviewPierre Riteau proposed openstack/kayobe stable/wallaby: Remove outdated upgrade step  https://review.opendev.org/c/openstack/kayobe/+/79757812:25
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/victoria: CI: Move to centos-8-stream  https://review.opendev.org/c/openstack/kolla-ansible/+/79701712:26
opendevreviewPierre Riteau proposed openstack/kayobe stable/victoria: Remove outdated upgrade step  https://review.opendev.org/c/openstack/kayobe/+/79757912:26
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/victoria: CI: Add centos-8-stream jobs  https://review.opendev.org/c/openstack/kolla-ansible/+/79701712:26
opendevreviewPierre Riteau proposed openstack/kayobe stable/ussuri: Remove outdated upgrade step  https://review.opendev.org/c/openstack/kayobe/+/79762912:28
opendevreviewPierre Riteau proposed openstack/kayobe stable/victoria: Fix url to ansible site in kolla-ansible.rst  https://review.opendev.org/c/openstack/kayobe/+/79758012:30
opendevreviewMark Goddard proposed openstack/kayobe master: Ubuntu: add upgrade jobs in CI  https://review.opendev.org/c/openstack/kayobe/+/79762612:55
opendevreviewMerged openstack/kolla-ansible master: Make it possible to override automatic fluentd version detection  https://review.opendev.org/c/openstack/kolla-ansible/+/77126013:02
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Do not try to get container facts on localhost  https://review.opendev.org/c/openstack/kolla-ansible/+/79764613:33
kevko^trivial13:33
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Do not try to get container facts on deployment host  https://review.opendev.org/c/openstack/kolla-ansible/+/79764613:47
opendevreviewMichal Arbet proposed openstack/kolla-ansible stable/wallaby: Do not try to get container facts on deployment host  https://review.opendev.org/c/openstack/kolla-ansible/+/79758413:52
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/train: baremetal: Don't start Docker after install on Debian/Ubuntu  https://review.opendev.org/c/openstack/kolla-ansible/+/79158213:55
opendevreviewMerged openstack/kolla-ansible master: Allow user to set sysctl_net_ipv4_tcp_retries2  https://review.opendev.org/c/openstack/kolla-ansible/+/77777213:57
born2bakeHey guys, I am trying to run - kolla-ansible octavia-certificates & getting "ERROR: Ansible version should be between 2.9 and 2.9. Current version is  which is not supported."; pip seems to be fine - http://paste.openstack.org/show/806883/14:10
born2bakeActually, I cant use kolla-ansible at all14:12
born2bakeBasically, following docs -  2001  source kolla/bin/activate14:18
born2bake 2002  pip install -U pip14:18
born2bake 2003  pip install 'ansible<3.0'14:18
born2bake 2004  pip install kolla-ansible14:18
born2bakeYou get - ERROR: Ansible version should be between 2.9 and 2.9. Current version is  which is not supported.14:18
mgoddardborn2bake: which release, which docs?14:27
born2bakemgoddard I think my bad cause I was using "latest" docs rather than victoria one. Wallaby is not supported yet, right?14:29
mgoddardborn2bake: wallaby should be released today or tomorrow14:29
born2bakeoh wow so then I am just on time lol ; I will wait then14:30
mgoddardborn2bake: always use a version constraint to install kolla-ansible14:30
mgoddardborn2bake: you can use 12.0.0.0rc2 for now14:30
born2bakemgoddard I also wanted to ask one more question related to Octavia networking https://docs.openstack.org/kolla-ansible/wallaby/reference/networking/octavia.html#networking ; In case if my network setup does not have vlan configured, and I have 2 flat network cables connected therefore, I am going to use eth0 for "network_interface" & eth1 for "neutron_external_interface"; Can I use the same eth0 or eth1 for "octavia_network_interface"? (for 14:40
born2bakeeth1 pref)14:40
mgoddardborn2bake: would recommend against it14:46
mgoddardborn2bake: you can use a vxlan in wallaby, although we don't really recommend it for production14:47
born2bakeso eth0 then; what could be a reason of not using it this way? I am not planning to use it in prod though14:47
opendevreviewMerged openstack/kayobe-config-dev stable/ussuri: Sync configs with kayobe @ cf8869eecd669df411696e78bd90d0b9a02f429f  https://review.opendev.org/c/openstack/kayobe-config-dev/+/79552614:49
mgoddardmgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne cosmicsound osmanlicilegi bbezak parallax Fl1nt14:54
mgoddard^ meeting in 614:54
jingvar_born2bake: I had the same error,  have found some variables like min_version and changed it14:59
mgoddardthose variables are there for a reason :)14:59
mgoddard#startmeeting kolla15:00
opendevmeetMeeting started Wed Jun 23 15:00:10 2021 UTC and is due to finish in 60 minutes.  The chair is mgoddard. 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 'kolla'15:00
mgoddard#topic rollcall15:00
yoctozepto\o/15:00
mgoddard \o/15:00
headphoneJameso/15:00
ohorecny2Hi all, I am first time on this meeting so in case that I am doing something wrong please correct me.15:02
yoctozeptowelcome ohorecny215:02
headphoneJameswelcome 15:02
mgoddardwelcome ohorecny2, thanks for joining15:03
mgoddard#topic agenda15:04
mgoddard* Roll-call15:04
mgoddard* Agenda15:04
mgoddard* Announcements15:04
mgoddard* Review action items from the last meeting15:04
mgoddard* CI status15:04
mgoddard* Wallaby release planning15:04
mgoddard  ** libvirt/OVMF bug15:04
mgoddard* Xena cycle planning15:04
mgoddard  ** podman (ohorecny)15:04
mgoddard* Open discussion15:04
mgoddard#topic Announcements15:04
yoctozeptothat agenda needed updating15:04
mgoddard#info Kolla Wallaby should be released this week15:05
yoctozepto\o/15:05
mgoddardcloser to the deadline than I'd hoped, but alas it always ends up this way15:05
yoctozeptoit's actually just going through the release team15:05
yoctozeptoyeah15:05
yoctozeptolet's try better next time15:05
mgoddardthe main blockers have been out of our control, as usual15:06
yoctozeptoyeah, sadly15:07
mgoddardone problem is that we hold new releases to a higher standard than existing ones15:07
mgoddardanyway15:07
mgoddard#topic Review action items from the last meeting15:07
yoctozeptothat is a quality of ours15:08
mgoddardThere were none15:08
mgoddard#topic CI status15:08
yoctozeptokolla and kolla ansible fully green15:09
mgoddardUssuri fails sporadically on Ubuntu due to Neutron migrations failing15:09
yoctozeptoyeah, it somehow got more common recently; and only affects ubuntu15:09
mgoddardweird15:09
yoctozeptono idea what changed; some lib? kernel?15:09
mgoddardsome difference in mariadb?15:09
yoctozeptoi checked mariadb and neutron15:09
yoctozeptoand no version coincidence15:10
yoctozeptono15:10
yoctozeptowe even have the same mariadb in centos815:10
yoctozeptoit just started popping15:10
yoctozeptolooks like a race condition15:10
mnasiadkaLate again, eh15:10
yoctozeptoI updated the description15:11
mgoddardk15:11
yoctozeptoit should be "upgrades to Ussuri fail..."15:11
yoctozeptoclean deploys do not15:11
mgoddardis it multinode only?15:11
yoctozeptono, singlenode too15:12
yoctozeptothat's why we got so many gate rechecks15:12
mgoddardkk15:12
mgoddard#topic Wallaby release planning15:12
mgoddardlibvirt/OVMF bug now fixed15:13
yoctozeptoyeah, and libvirt 7.4.0 in stream15:13
yoctozepto7.0 in non-stream15:13
mgoddardwallaby on its way out of the door15:13
yoctozeptotherefore we got 7.0 in stable branches too15:13
yoctozeptomind that15:13
mgoddarddoes that break them?15:14
yoctozeptono, they work15:14
mgoddardgoood15:14
yoctozeptojust watch out in production15:14
mgoddardso we can just leave wallaby alone until we need to add support for CentOS stream 9 :D15:14
yoctozeptoI actually had a thought about it15:15
mgoddardplease share15:15
yoctozeptoand I think we should not follow rdo steps since we containerise15:15
yoctozeptojust apply the trick we do with debuntu15:15
yoctozeptocheck if it works15:15
yoctozeptoand live happily15:15
mgoddardI had a similar thought15:15
yoctozeptothen it's sealed15:15
mgoddardwell15:16
yoctozeptoit depends on whether it works15:16
yoctozeptoI just want to avoid the backporting circus15:16
mgoddardactually mine was about CentOS Linux to CentOS stream, where there is an in-place upgrade15:16
mgoddardthere won't necessarily be one for CS8 to CS915:16
yoctozeptoahm15:16
mgoddardin which case we're back to a rolling reinstall15:17
yoctozeptoI meant more like allowing Xena to deploy on CentOS Stream 8 still15:17
yoctozeptoand have 9 in containers15:17
yoctozeptothat's what we allow on debuntu, except for a slight version reversal15:17
mgoddardcould do that15:17
yoctozeptobut then you could tell15:17
yoctozeptocs8 + wallaby -> cs8 + xena -> cs9 + xena15:18
yoctozeptoroll as you wish15:18
mgoddardalthough I think ideally containers should be ahead of hosts15:18
yoctozeptoyeah, they will be15:18
mgoddardsorry, other way around15:18
yoctozeptoI think we are fine15:18
mgoddardhttps://access.redhat.com/support/policy/rhel-container-compatibility15:19
yoctozeptopeople been running focal on bionic for a year now15:19
mgoddardmaybe15:19
mgoddardwe can speculate15:19
yoctozeptotier 3 is fine for what we don't have anyway15:19
mgoddardbut it needs to be tested15:19
yoctozeptoyes, that's the goal15:19
yoctozeptotest - if it works, go with it15:19
yoctozeptoif not - cry and adapt15:20
mgoddardperhaps centos will have imploded by then15:20
yoctozeptothat could work too15:20
mnasiadkaWonder if stream Victoria gives us 7.4 as well15:20
yoctozeptomnasiadka: yes, it does imho15:20
yoctozeptobecause it's just adv virt repo for stream15:20
yoctozeptobut yeah, check it please15:21
mgoddardlet us move on15:21
mgoddard#topic podman (ohorecny)15:21
yoctozeptoohorecny2, the floor is yours15:21
ohorecny2hi all again15:21
ohorecny2ok, thanks15:21
yoctozeptohi ohorecny2 again15:21
ohorecny2mayve I can quickly introduce myself15:21
yoctozeptoplease go ahead15:21
ohorecny2my name is Oliver and I am working in TietoEvry. In our company we are interested in support of Podman in kolla-ansible.15:22
ohorecny2The main reason is that docker isn't supported by RedHat since Rhel8.15:22
ohorecny2In our company we decided to invest some time for implementation of this support.15:23
ohorecny2I am leader of this project and for now we are in stage that we are able to deploy basic all-in-one deployment based on Podman containers.15:24
ohorecny2These containers are running as services and it seems that OpenStack is functional (we are able to spawn new VM, etc.)15:24
ohorecny2For now we are testing only on CentOS 815:25
ohorecny2Regarding code we are using master og kolla-ansible, where we added new option to globals.yml fro user to choose contaner engine (Docker / Podman).15:26
ohorecny2So each service has its own tasks for Docker and also for Podman.15:26
ohorecny2This means that whole change is quite big.15:26
ohorecny2The biggest challenge was replacement of kolla-docker module, which is mostly replaced by existing ansible modules for Podman.15:27
ohorecny2Unfortunately it was not possible to replace everything and we needed to use also podman-py library for API calls (for getting some container facts)15:28
ohorecny2I guess that this can be replaced somehow in future.15:28
ohorecny2We would like to propose this change for review as soon as possible. We need to firstly do some internal review and do squash of commits.15:29
ohorecny2I just want to know what do you think about it and few other questions.15:30
mgoddardThank you for the overview ohorecny2 15:30
mgoddardI think people will want to see the code to get a feel for the approach15:30
yoctozepto++15:30
mgoddardare you using systemd to run the containers?15:30
ohorecny2sure, as I mentioned we would like to propose this change in next few days. But it is quite big so reviewing will be so complicated. Also CI checks will be needed to adapt for this.15:31
yoctozeptobtw, debian now supports podman with systemd natively as well, ubuntu will in 22.0415:32
ohorecny2mgoddard: yes, each container has its own service file15:32
mgoddardohorecny2: did you see this PoC? https://github.com/stackhpc/kolla-ansible/commit/e44d4b028e3aa24955dd12271783287ae43a560315:32
yoctozeptoI think we might be able to save some complexity by applying some refactoring we have in proposals15:32
ohorecny2yoctozepto: yes that is right, we did not consider Ubuntu or Debian yet15:34
yoctozeptono problem15:34
ohorecny2mgoddard: yes, I saw it some time ago15:34
mgoddardok15:35
yoctozeptojust mentioning we could test portability with debian15:35
mgoddardohorecny2: it is possible to push a patch chain to gerrit. If the commits are already cleanly separated then no need to squash them15:35
ohorecny2mgoddard: by that way how it is possible to start / restart containers during some actions, but not possible to create new containers.15:36
ohorecny2so, ansible modules for podman are used for container creatin15:36
ohorecny2*creation15:36
mgoddardL20 of the unit file does a docker/podman run15:37
mgoddardwhich creates a container15:37
mgoddardI did not test it very much15:38
mgoddardI just wanted to get the concept into a commit15:38
mnasiadkaCeph uses the same approach for a long time, so I guess not a lot of testing needed15:39
mgoddardmnasiadka: LOL15:39
mgoddardjust chuck it in15:39
mnasiadkamgoddard: I mean just running docker/podman run --rm from a systemd unit, not the whole functionality :D15:40
yoctozeptolol15:40
yoctozeptomeh15:40
ohorecny2mgoddard: right, but what about pulling images and etc?15:40
mnasiadkaCan't wait to see the proposal, and then we can discuss :)15:40
mgoddardohorecny2: yeah, there will be cases where systemd is not enough15:41
mgoddardI would like to see a short spec on this15:41
ohorecny2mgoddard: yes, there are several cases, that it is not possible to do by that way I think15:41
ohorecny2mnasiadka: sure, as I mentioned, it is on the way :)15:42
mgoddardit is a large enough change that we should do some up front thinking/design15:42
mgoddardso I would suggest this as a rough plan15:42
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/train: baremetal: Don't start Docker after install on Debian/Ubuntu  https://review.opendev.org/c/openstack/kolla-ansible/+/79158215:42
mnasiadkamgoddard: agree, we don't normally do specs - but that's core functionality15:42
mgoddard1. ohorecny2 to share current state of code with community via gerrit15:43
mgoddard2. community reads code and does some thinking15:43
ohorecny2mgoddard: yes, exactly, this change is huge I think. For few basic services it was more than 255 files changed and around 9000 insertions 15:43
mgoddard3. community discusses the approach and agrees a rough direction15:43
mgoddard4. ohorecny2 & colleagues write a spec describing the agreed direction15:44
mgoddard5.adapt code to spec & iterate15:44
yoctozepto++15:45
mgoddardwhat I would like to know is, do ohorecny2 & team have the capacity to drive this through to completion?15:45
ohorecny2regarding #5 yes, when this will be in review we will definitely need to adapt it, because we have there some workarounds which needs to be changed15:46
mgoddardwe are very limited on review resources, and I would hate to see us put in a *lot* of review time for this patch then not see it completed15:46
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/victoria: CI: Fix nfv job with kolla dependency  https://review.opendev.org/c/openstack/kolla-ansible/+/79769815:47
ohorecny2mgoddard: yes, I discussed this with management and we would like to finish this till end. It is agreed at least till end of this year.15:47
mgoddardgreat!15:48
ohorecny2I hope that it is possible to finalize.15:48
ohorecny2we would like to even adapt kolla to image build base on podman 15:48
mgoddardit will be important to find out answers to important questions early15:49
ohorecny2yes that is right15:49
ohorecny2that is the reason why I am here :D15:49
mgoddardin particular, do all distros supported by kolla have support for podman15:49
ohorecny2maybe also, which version of ansible is planned for next release15:50
mgoddardprobably min 2.10, max 2.11 15:50
mnasiadkaaround podman - remember each distro basically has a different version15:50
mnasiadkamgoddard: there is no 2.11, unless you're speaking about ansible-base :)15:51
mgoddardyes15:51
yoctozeptoI think we want to go ansible-2.11 and choose the installed modules15:51
yoctozeptoneed to discuss that15:51
ohorecny2so far we are testing with ansible 2.915:51
mnasiadkaI think we discussed that already on the PTG, and agreed we start with that approach with kolla-toolbox, and see how it goes.15:52
mnasiadkayoctozepto: ^^15:52
yoctozeptosomething like that indeed15:52
yoctozeptoyes, I am here15:52
mnasiadkasorry, too many calls today discussing network packet processing ;)15:52
yoctozeptomnasiadka: did you mention "encapsulation"?15:53
mnasiadkayoctozepto: I even started that, but then we also need to move to FQCNs most probably15:53
mgoddarddoes anyone have any more questions for ohorecny2 ?15:53
yoctozeptomnasiadka: we should; I think there is a tool to migrate that15:53
yoctozeptomgoddard: I need to see the code; and test on debian15:54
yoctozeptoI can help with CI15:54
mgoddardok, then let's move on15:55
mnasiadkanevermind the podman versions, seems now it's 3.0 everywhere15:55
mnasiadkaso we should be ok15:56
mgoddardThanks ohorecny2 that was a helpful discussion15:56
yoctozepto++15:56
mgoddardIf you'd like to discuss again, feel free to ping one of us or add an item to the agenda on the wiki15:56
ohorecny2thank you too15:56
mgoddard#topic Open discussion15:56
mgoddardDoes anyone have anything today?15:56
yoctozeptoI believe podman is able to be less problematic than docker15:56
yoctozeptobut we will see15:56
headphoneJamesyes - I have a basic question15:56
yoctozeptoI have a lot of local stuff atm15:57
headphoneJamesIt seems like DevStack and tripleo use cloud.yaml to define the initial openstack users with scope.15:57
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/victoria: [CI] Fix the NFV scenario  https://review.opendev.org/c/openstack/kolla-ansible/+/79770215:57
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/victoria: CI: Fix nfv job with kolla dependency  https://review.opendev.org/c/openstack/kolla-ansible/+/79769815:58
headphoneJamesKA creates users using OpenStack Ansible modules like "os_user" - those modules do not accept scope as an argument.15:58
mgoddardheadphoneJames: users for what purpose?15:58
headphoneJamesinitial roles + users 15:58
headphoneJamesto admin the cloud15:58
mnasiadkaheadphoneJames: have you checked if ansible collection does? https://github.com/openstack/ansible-collections-openstack/15:59
headphoneJamesmnasiadka: not yet - so I can start there15:59
mgoddardheadphoneJames: do you mean for tasks using the kolla_toolbox module to register endpoints, users, etc?16:00
headphoneJamesyes16:00
mgoddardthe downside of that is that you have to put some full admin creds on disk16:00
yoctozeptowe can use a ramdisk16:01
mgoddardwhereas we specify them on demand16:01
opendevreviewMark Goddard proposed openstack/kayobe master: Ubuntu: add upgrade jobs in CI  https://review.opendev.org/c/openstack/kayobe/+/79762616:01
mgoddardwe could use a ramdisk, but it's still accessible always16:02
headphoneJameshowever, we may not be able to specify the scope of a user/role using kolla_toolbox approach?16:02
mgoddardah, openstack modules don't provide the option?16:02
headphoneJamesor really I'm just not sure how we do that16:02
mnasiadkathey don't provide the option, even the latest ones in the collection16:03
mnasiadkaso first it would need to be added there16:03
headphoneJames it didn't look that way from my initial digging, but I haven't looked at the code in https://github.com/openstack/ansible-collections-openstack/16:03
headphoneJames so the first step is to update the ansible modules for openstack?16:04
mnasiadkawe already update the Ansible modules for OVS, so you can follow the approach16:04
mgoddardit might be worth looking into - now the modules are in a collection we could potentially pull in a newer version in the kolla-toolbox image16:04
mnasiadkaheadphoneJames: https://review.opendev.org/c/openstack/kolla/+/78290616:05
mgoddardanyways, we should wrap up16:05
mgoddardthanks all16:05
mnasiadkathanks mgoddard 16:05
mgoddard#endmeeting16:05
opendevmeetMeeting ended Wed Jun 23 16:05:44 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-06-23-15.00.html16:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-06-23-15.00.txt16:05
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-06-23-15.00.log.html16:05
yoctozeptothanks mgoddard16:06
headphoneJamesthanks16:07
*** rpittau is now known as rpittau|afk16:08
opendevreviewMerged openstack/kayobe stable/ussuri: Update seed VM image to CentOS 8.4  https://review.opendev.org/c/openstack/kayobe/+/79667016:30
opendevreviewVerification of a change to openstack/kayobe failed: Prevent matching unrelated images  https://review.opendev.org/c/openstack/kayobe/+/79583116:30
*** gfidente is now known as gfidente|afk16:34
*** samcat11_ is now known as samcat116_18:09
opendevreviewAlbert Braden proposed openstack/kolla-ansible master: Added upgrade note for separate nova and cinder keys.  https://review.opendev.org/c/openstack/kolla-ansible/+/79694818:50
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/train: baremetal: Don't start Docker after install on Debian/Ubuntu  https://review.opendev.org/c/openstack/kolla-ansible/+/79158219:25
*** gilou_ is now known as Gilou22:48

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