Monday, 2025-07-28

*** mhen_ is now known as mhen01:19
yasufumHi, tacker team08:00
yasufumhi08:01
takahashi-tschi08:01
yasufum#startmeeting tacker08:02
opendevmeetMeeting started Mon Jul 28 08:02:45 2025 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
opendevmeetThe meeting name has been set to 'tacker'08:02
yasufum#link https://etherpad.opendev.org/p/tacker-meeting08:03
yasufumSo, let's start the meeting.08:03
yasufumNo update on the first item. Sorry for the late.08:04
yasufumI'm going to upload some fixes this week.08:04
yasufumThe second item,08:05
yasufumone spec is still remained to be reviewed.08:05
takahashi-tscI'll do it today. It looks good.08:06
yasufumthx08:06
hi-kobahello. thank you.08:07
yasufumhi08:07
yasufumGo to the next topic.08:07
yasufumshivam: is there any update on the third topic?08:08
shivamyes08:08
shivamRegarding update on zuul issues, as part of continued investigation of Zuul job failures in Tacker patches, we identified four key issues affecting DevStack setup and their fixes. 08:09
shivamKubernetes Job Failure caused by outdated setuptools (v59.6.0) due to system-wide usage in Ubuntu Jammy; can be resolved by enabling DevStack virtual environment (GLOBAL_VENV=True) to use newer setuptools.08:09
shivamA tacker patch has been created for fixing this issue: https://review.opendev.org/c/openstack/tacker/+/95588208:10
shivamOpenStack Job Failure "Neutron failed to start" and "internal server error" linked to "logger" in Q_ML2_PLUGIN_MECHANISM_DRIVERS; can be resolved by removing logger. This suggestion was from the Neutron team.08:11
shivamInvalid Formatter Error During VIM Registration: python-tackerclient used deprecated formatter functions incompatible with osc-lib v4.x; can be fixed by replacing them with DictColumn from osc_lib.cli.format_columns.08:11
shivamA python-tackerclient patch has been created for the same: https://review.opendev.org/c/openstack/python-tackerclient/+/95586908:12
shivamRegarding neutron issue fix, I will be either creating a separate patch or incorporating the fix into the existing patch for the setuptools issue:https://review.opendev.org/c/openstack/tacker/+/95588208:12
shivamIn conclusion, the fix for all four issues is now identified which will resolve this zuul build issues once the fixes are merged.08:13
shivamThanks08:13
yasufumThanks08:14
yasufumAny comment?08:14
yasufumgood08:15
yasufumI'll review uploaded patches passed the tests, thanks.08:15
shivamThank you08:16
yasufummove on to the next topic.08:16
yasufumProposal for Automation Script to Install Tacker via OpenStack-Helm08:16
shivamok08:17
shivamObjective of this topic is to propose a Python-based automation script to automate the Tacker installation process via OpenStack-Helm08:17
shivamThe manual installation involves multiple complex steps, making it error-prone and time-consuming.08:18
shivamFor reference, please see the current documentation: https://docs.openstack.org/tacker/latest/install/openstack_helm.html08:18
shivamThis script will automate environment setup, prerequisite installation, and deployment of Tacker and its dependencies using OpenStack-Helm.08:19
shivamIt aims to simplify installation and provide better user experience with clear logging and error handling.08:19
shivamI would like to hear feedback and suggestions from the community members on our proposal.08:19
shivamAlso, will it be okay to include this automation script in Tacker repository and provide a usage guide or is there any different suggestion from community?08:20
shivamThanks08:20
yasufumthanks08:20
yasufumDo you have any idea where the script will be placed?08:22
takahashi-tscIn addition, as background, we have received requests from another open-source project (communities related to O-RAN) to use scripts like this, and we have been responding to those requests.08:22
yasufumfine08:22
takahashi-tscIf we make the scripts, it would also allow us to provide them to other communities with similar requirements in the future.08:23
takahashi-tscThat's all from my side. I'd like to know Tacker team's opinions.08:23
yasufumhmm08:24
yasufumI wonder if we need to test the script, on zuul for example, to keep it healthy?08:26
yasufumor no need to take care for that?08:27
yasufumnothing?08:29
takahashi-tscIn my personal opinion, If possible, yes. However, we do not want to increase test cases due to resource amount issue...08:30
takahashi-tscI suggest to start from firstly put scripts in tools folder, and discuss how to maintain.08:31
yasufumIt's acceptable some scripts have no tests for CI/CDif it's not critical for running tacker,08:32
takahashi-tscWe can obtain many options after test improvement completed, such as weekly testing, manual testing, experimantal testing etc.08:33
yasufumor some failure can be found easily.08:33
yasufumOK, thanks.08:33
takahashi-tscBy the way, this discussion is also related to the next topic. OpenStack-Helm documentation sometimes becomes "broken"... 08:35
takahashi-tscI'd like to discuss how to maintain openstack-helm files and docs.08:35
yasufumoko08:36
yasufumok08:36
shivamok, so the next topic is regarding update of Tacker Documentation "Install Tacker via Openstack-Helm"08:36
shivamCurrently, external reference links in the official documentation return 404 errors, causing confusion and potential deployment failures.08:37
shivamFor reference, please see the current documentation: https://docs.openstack.org/tacker/latest/install/openstack_helm.html08:37
shivamHence, we are suggesting to update the outdated or broken URLs to enhance clarity and usability.08:38
shivamA patch is raised for updating the document: https://review.opendev.org/c/openstack/tacker/+/95577408:39
shivamI would like to hear feedback and suggestions from the community on this proposed update.08:39
shivamAlso, to prevent similar issues in future, what practices should we adopt?08:39
shivamthank you08:40
yasufumthanks08:41
yasufumLGTM for the fix patch.08:42
shivamthanks08:43
yasufumHowever, I have no idea for avoiding such a dead link.08:43
takahashi-tscOne apporach may be we maintain only the script with CI, and give up to include actual URL of files in docs. Docs show only high level description.08:44
yasufumSimply, we can create a simple tool for checking all the links if it's useful for our maintenance.08:44
takahashi-tscYes, my suggestion is very "active" approach and might not be needed, and yasufum-san's proposal might be better.08:45
takahashi-tscSo, I'd like to discuss this topic with Tacker members...08:46
yasufumOK08:46
yasufumtakahashi-tsc: Any idea who will be the owner of the issue?08:46
takahashi-tscMy team can be the owner, this is a little long-term discussion.08:47
yasufumthanks08:48
yasufumAny other comment, everyone?08:48
yasufumgood08:49
yasufumshivam: I'd appreciate if you add the conclusions of your topics on the etherpad shortly. Thanks.08:50
yasufumAll the topics done.08:51
shivamok08:51
yasufumthx08:51
shivamthank you08:51
yasufumSo, let's close this meeting.08:51
yasufumThank you for joining, bye!08:51
takahashi-tscthanks08:52
yasufum#endmeeting08:52
opendevmeetMeeting ended Mon Jul 28 08:52:31 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:52
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-07-28-08.02.html08:52
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-07-28-08.02.txt08:52
opendevmeetLog:            https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-07-28-08.02.log.html08:52

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