08:02:45 <yasufum> #startmeeting tacker
08:02:45 <opendevmeet> Meeting 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:45 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:45 <opendevmeet> The meeting name has been set to 'tacker'
08:03:11 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:03:29 <yasufum> So, let's start the meeting.
08:04:16 <yasufum> No update on the first item. Sorry for the late.
08:04:39 <yasufum> I'm going to upload some fixes this week.
08:05:01 <yasufum> The second item,
08:05:58 <yasufum> one spec is still remained to be reviewed.
08:06:48 <takahashi-tsc> I'll do it today. It looks good.
08:06:53 <yasufum> thx
08:07:26 <hi-koba> hello. thank you.
08:07:30 <yasufum> hi
08:07:44 <yasufum> Go to the next topic.
08:08:10 <yasufum> shivam: is there any update on the third topic?
08:08:17 <shivam> yes
08:09:12 <shivam> Regarding 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:47 <shivam> Kubernetes 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:10:12 <shivam> A tacker patch has been created for fixing this issue: https://review.opendev.org/c/openstack/tacker/+/955882
08:11:09 <shivam> OpenStack 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:51 <shivam> Invalid 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:12:15 <shivam> A python-tackerclient patch has been created for the same: https://review.opendev.org/c/openstack/python-tackerclient/+/955869
08:12:48 <shivam> Regarding 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/+/955882
08:13:17 <shivam> In conclusion, the fix for all four issues is now identified which will resolve this zuul build issues once the fixes are merged.
08:13:29 <shivam> Thanks
08:14:34 <yasufum> Thanks
08:14:39 <yasufum> Any comment?
08:15:28 <yasufum> good
08:15:50 <yasufum> I'll review uploaded patches passed the tests, thanks.
08:16:10 <shivam> Thank you
08:16:48 <yasufum> move on to the next topic.
08:16:59 <yasufum> Proposal for Automation Script to Install Tacker via OpenStack-Helm
08:17:31 <shivam> ok
08:17:52 <shivam> Objective of this topic is to propose a Python-based automation script to automate the Tacker installation process via OpenStack-Helm
08:18:26 <shivam> The manual installation involves multiple complex steps, making it error-prone and time-consuming.
08:18:39 <shivam> For reference, please see the current documentation: https://docs.openstack.org/tacker/latest/install/openstack_helm.html
08:19:04 <shivam> This script will automate environment setup, prerequisite installation, and deployment of Tacker and its dependencies using OpenStack-Helm.
08:19:24 <shivam> It aims to simplify installation and provide better user experience with clear logging and error handling.
08:19:44 <shivam> I would like to hear feedback and suggestions from the community members on our proposal.
08:20:13 <shivam> Also, 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:24 <shivam> Thanks
08:20:45 <yasufum> thanks
08:22:10 <yasufum> Do you have any idea where the script will be placed?
08:22:12 <takahashi-tsc> In 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:32 <yasufum> fine
08:23:04 <takahashi-tsc> If we make the scripts, it would also allow us to provide them to other communities with similar requirements in the future.
08:23:32 <takahashi-tsc> That's all from my side. I'd like to know Tacker team's opinions.
08:24:52 <yasufum> hmm
08:26:38 <yasufum> I wonder if we need to test the script, on zuul for example, to keep it healthy?
08:27:16 <yasufum> or no need to take care for that?
08:29:57 <yasufum> nothing?
08:30:14 <takahashi-tsc> In my personal opinion, If possible, yes. However, we do not want to increase test cases due to resource amount issue...
08:31:46 <takahashi-tsc> I suggest to start from firstly put scripts in tools folder, and discuss how to maintain.
08:32:43 <yasufum> It's acceptable some scripts have no tests for CI/CDif it's not critical for running tacker,
08:33:00 <takahashi-tsc> We can obtain many options after test improvement completed, such as weekly testing, manual testing, experimantal testing etc.
08:33:06 <yasufum> or some failure can be found easily.
08:33:37 <yasufum> OK, thanks.
08:35:35 <takahashi-tsc> By the way, this discussion is also related to the next topic. OpenStack-Helm documentation sometimes becomes "broken"...
08:35:50 <takahashi-tsc> I'd like to discuss how to maintain openstack-helm files and docs.
08:36:05 <yasufum> oko
08:36:07 <yasufum> ok
08:36:44 <shivam> ok, so the next topic is regarding update of Tacker Documentation "Install Tacker via Openstack-Helm"
08:37:20 <shivam> Currently, external reference links in the official documentation return 404 errors, causing confusion and potential deployment failures.
08:37:45 <shivam> For reference, please see the current documentation: https://docs.openstack.org/tacker/latest/install/openstack_helm.html
08:38:26 <shivam> Hence, we are suggesting to update the outdated or broken URLs to enhance clarity and usability.
08:39:07 <shivam> A patch is raised for updating the document: https://review.opendev.org/c/openstack/tacker/+/955774
08:39:36 <shivam> I would like to hear feedback and suggestions from the community on this proposed update.
08:39:54 <shivam> Also, to prevent similar issues in future, what practices should we adopt?
08:40:08 <shivam> thank you
08:41:03 <yasufum> thanks
08:42:16 <yasufum> LGTM for the fix patch.
08:43:03 <shivam> thanks
08:43:11 <yasufum> However, I have no idea for avoiding such a dead link.
08:44:54 <takahashi-tsc> One 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:54 <yasufum> Simply, we can create a simple tool for checking all the links if it's useful for our maintenance.
08:45:37 <takahashi-tsc> Yes, my suggestion is very "active" approach and might not be needed, and yasufum-san's proposal might be better.
08:46:02 <takahashi-tsc> So, I'd like to discuss this topic with Tacker members...
08:46:12 <yasufum> OK
08:46:49 <yasufum> takahashi-tsc: Any idea who will be the owner of the issue?
08:47:56 <takahashi-tsc> My team can be the owner, this is a little long-term discussion.
08:48:35 <yasufum> thanks
08:48:53 <yasufum> Any other comment, everyone?
08:49:47 <yasufum> good
08:50:55 <yasufum> shivam: I'd appreciate if you add the conclusions of your topics on the etherpad shortly. Thanks.
08:51:20 <yasufum> All the topics done.
08:51:26 <shivam> ok
08:51:29 <yasufum> thx
08:51:34 <shivam> thank you
08:51:43 <yasufum> So, let's close this meeting.
08:51:52 <yasufum> Thank you for joining, bye!
08:52:22 <takahashi-tsc> thanks
08:52:31 <yasufum> #endmeeting