| yasufum | Hi tacker team | 08:00 |
|---|---|---|
| ueha | Hi | 08:01 |
| yuta-kazato | Hi | 08:01 |
| yasufum | hi | 08:01 |
| yasufum | #startmeeting tacker | 08:01 |
| opendevmeet | Meeting started Tue Sep 20 08:01:50 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:01 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:01 |
| masaki-ueno | hi | 08:01 |
| takahashi-tsc | hi | 08:02 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:03 |
| h_asahina | hi | 08:04 |
| yasufum | It's R2 and rc1 was over, so I wonder there are not so much topic today. | 08:04 |
| yasufum | Anyway, thanks for your hard work for reviews. | 08:04 |
| yasufum | So, let's start from the first item. | 08:05 |
| yasufum | #topic Recommended versions of k8s, k8s client, and helm in Tacker Zed Release | 08:05 |
| yasufum | yota-kazato: can you share your topic? | 08:06 |
| yuta-kazato | yasufum: ok | 08:06 |
| yuta-kazato | Before that, I would like to thank everyone for your contributions to rc1 last week! | 08:06 |
| yuta-kazato | My topic is Recommended versions of k8s, k8s client, and helm in Tacker Zed Release | 08:07 |
| yuta-kazato | In Tacker, we use kubernetes (k8s), k8s client, and Helm for CNF in LCM operations. | 08:08 |
| yuta-kazato | However, I think that Tacker community do not recommend which versions to use or support. | 08:08 |
| yuta-kazato | There are some problems about their versions. | 08:09 |
| yuta-kazato | e.g. Zuul in Zed release uses Helm v3.5.4, which is older than the latest version 3.9.4. | 08:09 |
| yuta-kazato | In Devstack, there is the other same problem of k8s versions between k8s client (1.25) and k8s server (1.23). | 08:10 |
| yuta-kazato | It should not exceeds the supported minor version skew of +/-1. | 08:10 |
| yuta-kazato | As you know, k8s/helm updates and their EoLs are fast cycles.. | 08:10 |
| yasufum | sure | 08:11 |
| yuta-kazato | Therefore, we need to decide the recommended versions in Zed release and update their versions regularly to provide mutual guarantees. | 08:11 |
| yuta-kazato | Does anyone have specific opinions on what has been discussed so far? | 08:11 |
| yasufum | I don't have specific one actually... | 08:13 |
| masaki-ueno | I think we should determine recommended versions of kubernetes according to the status of k8s python client. | 08:14 |
| masaki-ueno | Sorr, I noticed that you mentioned it above.... | 08:16 |
| yuta-kazato | Thank you for your opinion! Refering k8s python client's version is good idea. | 08:17 |
| yasufum | Where can we I find the dependent version of k8s? | 08:18 |
| yasufum | https://pypi.org/project/python-tackerclient/ | 08:18 |
| yasufum | here? | 08:18 |
| yasufum | sorry, it's wrong | 08:18 |
| masaki-ueno | https://github.com/kubernetes-client/python | 08:18 |
| masaki-ueno | The above describes the supported version for each version of client libs | 08:19 |
| yasufum | ok, thanks | 08:19 |
| yuta-kazato | Thanks! | 08:21 |
| yuta-kazato | How about providing support version information in Tacker documents. | 08:22 |
| yuta-kazato | ? | 08:22 |
| yuta-kazato | For example, Kuryr-kubernetes provides their supported versions, too. (But documents are not updated..) | 08:22 |
| yuta-kazato | # link | 08:23 |
| yuta-kazato | https://docs.openstack.org/kuryr-kubernetes/latest/devref/kuryr_kubernetes_versions.html | 08:23 |
| masaki-ueno | +1, and I think we also should update the supported version per one year (= the general EoL cycle of K8s) | 08:25 |
| yasufum | yuta-kazato: Do you mean we should provide each supported versions of k8s for several Tacker versions? | 08:27 |
| yuta-kazato | yasufum: yes, it is better for users and contributers. | 08:28 |
| yuta-kazato | And there is the other problem that k8s v1.25 is already EoL.. | 08:30 |
| yuta-kazato | # link | 08:30 |
| yuta-kazato | https://kubernetes.io/releases/ | 08:30 |
| yuta-kazato | sorry the above information is not correct. | 08:31 |
| yasufum | If so, how many old versions we should support? For example, from Train, Ussuri or so. | 08:32 |
| yuta-kazato | k8s server "v1.23" is EoL. | 08:32 |
| yuta-kazato | yasufum: IMO, it would be enough that Tacker Zed release will provide their support versions. | 08:35 |
| yuta-kazato | In addition, "this is just a suggestion", but how about agreeing on support versions for the next release in PTG? | 08:36 |
| yasufum | do you have any idea? | 08:37 |
| yasufum | s/any idea/any other comment/ | 08:38 |
| yuta-kazato | That's all from my side. I would like to hear from Tacker team members, thanks. | 08:39 |
| yasufum | I agree to the suggestion basically | 08:39 |
| ueha | I think we need to change Kubernetes version [1] and Helm version [2] to see if they pass the test. | 08:40 |
| ueha | [1] https://opendev.org/openstack/tacker/src/branch/master/.zuul.yaml#L471 | 08:40 |
| ueha | [2] https://opendev.org/openstack/tacker/src/branch/master/.zuul.yaml#L531 | 08:41 |
| ueha | When testing on Zuul, I think it is important that the kuryr-kubernetes support the latest version of Kubernetes when testing on Zuul. | 08:42 |
| ueha | The default version currently installed by the kuryr-kubernetes is 1.22.3 [3]. | 08:42 |
| ueha | . | 08:42 |
| ueha | [3] https://opendev.org/openstack/kuryr-kubernetes/src/branch/master/devstack/settings#L30 | 08:42 |
| ueha | The Kubernetes environment may need to be created without the use of the kuryr-kubernetes.. | 08:43 |
| ueha | we need to be careful it. | 08:43 |
| yasufum | yeah | 08:44 |
| ueha | That's all from my side. | 08:45 |
| yuta-kazato | Thank you for your information! I agree. | 08:45 |
| ueha | Thanks for your suggestion too :) | 08:46 |
| yasufum | ok, let's continue to discussion for making a decision of the topic at the next PTG. thanks. | 08:47 |
| masaki-ueno | You mentioned about kubernetes and helm versions, but how about Prometheus? | 08:47 |
| masaki-ueno | Since we added the support of FM and PM in Zed, I think we should determine supported version of Prometheus (and Alertmanager) | 08:49 |
| yasufum | sure | 08:51 |
| masaki-ueno | Even if Prometheus is a sample of External Monitoring Tool, we should add description which version is available for the documentation. | 08:51 |
| yuta-kazato | +1, we should discuss and decide supported version of Prometheus too! thank you for your suggestion:) | 08:51 |
| yasufum | It must be the similar issue. So, we should have a slot for the topic at the PTG. | 08:52 |
| yuta-kazato | OK! thanks. | 08:53 |
| yasufum | I'd appreciate if you suggest your concern on the etherpad. | 08:54 |
| yasufum | I'm going to upload the etherpad page for the next antelop :) | 08:54 |
| yasufum | please wait for a while. | 08:54 |
| yuta-kazato | Thanks a lot. | 08:55 |
| yasufum | It seems enough for the topic for now. | 08:56 |
| yasufum | yuta-kazato: thanks for the suggestion. | 08:57 |
| yasufum | move on to the next topic. | 08:57 |
| yasufum | #topic CFP for reducing resources for FTs | 08:58 |
| yasufum | It's just a brief suggestion for our the latest serious | 08:59 |
| yasufum | issue | 08:59 |
| yasufum | ... | 08:59 |
| yasufum | We has several failures on zuul gate at the end of R3. | 08:59 |
| yasufum | It might be because of some shortage of resources on CI. | 09:00 |
| yasufum | Although I have no idea for the problem, we should reduce the amount of FTs to avoid such a problem at the end of antelop. | 09:01 |
| yasufum | So, I'd appreciate if you suggest any idea for the issue to discuss at the next PTG. | 09:02 |
| yasufum | Do you have any comment? | 09:02 |
| yasufum | good | 09:04 |
| yasufum | go on to the third topic. | 09:05 |
| yasufum | # Backport for stable/zed | 09:05 |
| yasufum | We couldn't merge all candidate patches for zed, four patch were over the deadline. | 09:06 |
| yasufum | So, I decided to backport them in stable/zed. | 09:07 |
| yasufum | Three patches have already merged to master, but just one remained. | 09:07 |
| yasufum | #link https://review.opendev.org/c/openstack/tacker/+/857082 | 09:08 |
| yasufum | I'd like to merge it before the end of R2, and upload stable patches for four patches at once. | 09:08 |
| yasufum | That's all. Do you have any comment? | 09:09 |
| ueha | I think the above patch is waiting for the document to be added. | 09:10 |
| yasufum | yes | 09:11 |
| yasufum | The owner agreed to add docs. | 09:11 |
| ueha | I’m afraid if we can merge this week. | 09:12 |
| ueha | This Friday is a holiday in Japan, so there are only 2 days left. but I will do my best to review it when it is added. | 09:13 |
| yasufum | thanks | 09:14 |
| yasufum | OK | 09:16 |
| yasufum | It might be enough for today's discussion. | 09:17 |
| yasufum | So, let's close this meeting if you have no more comment. | 09:18 |
| yasufum | Thank you for joining, bye! | 09:19 |
| yuta-kazato | thanks, bye. | 09:19 |
| ueha | Thanks, bye | 09:19 |
| yasufum | #endmeeting | 09:19 |
| opendevmeet | Meeting ended Tue Sep 20 09:19:37 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:19 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-09-20-08.01.html | 09:19 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-09-20-08.01.txt | 09:19 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-09-20-08.01.log.html | 09:19 |
| *** amorin_ is now known as amorin | 12:07 | |
| *** tosky is now known as Guest1012 | 12:14 | |
| *** tosky__ is now known as tosky | 12:14 | |
| *** tosky is now known as Guest1013 | 12:30 | |
| *** tosky__ is now known as tosky | 12:30 | |
| *** dasm|off is now known as dasm | 13:30 | |
| *** soniya is now known as soniya|dinner | 14:14 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!