08:01:19 #startmeeting tacker 08:01:19 Meeting started Tue May 16 08:01:19 2023 UTC and is due to finish in 60 minutes. The chair is yasufum-o. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:19 The meeting name has been set to 'tacker' 08:01:40 #link https://etherpad.opendev.org/p/tacker-meeting 08:02:37 We have two item on the etherpad today 08:02:54 for updating docs 08:03:31 and blueprint we've accepted at the previous vPTG. 08:03:40 So, lets start from the first item. 08:03:53 w-juso: raady? 08:04:02 thanks, ok 08:04:10 good 08:04:16 #topic Location of compliance test document 08:04:47 I would like to ask for your opinion on the compliance test document's location. 08:05:37 We make and upload the document WIP patch how to use the compliance test with tacker. 08:05:56 https://review.opendev.org/c/openstack/tacker/+/883052 08:06:09 This document is placed the following directory. 08:06:24 Welcome to Tacker Documentation -> Tacker Contributor Guide -> Compliance testcases for tacker 08:06:54 https://docs.openstack.org/tacker/latest/contributor/index.html 08:07:54 We put it in the same place where Function Test is implemented and how it works. 08:08:36 If there is a problem with the location of this document, please give me a comment. 08:08:49 That's all from my side. Thank you. 08:09:47 I think the location should be decided based on your contents in general 08:10:26 and we already have docs for testing, right? 08:10:59 Although there no docs for functional tests currently in. 08:11:37 Is there any reason separating your contents from the current testing section? 08:12:00 it's here 08:12:02 #link https://docs.openstack.org/tacker/latest/contributor/development.environment.html#testing-tacker 08:15:00 w-juso: hello? 08:16:18 The you provided link is a general. 08:16:58 Our description was a more detailed, so we split it. 08:18:12 Please correct one thing before. Docs for functional tests are here, sorry. 08:18:15 #link https://docs.openstack.org/tacker/latest/contributor/tacker_functional_test.html 08:19:33 Thank you, we too worried whether to place it in this document. 08:21:09 But, in the case of the addition, the document was separated because it did not match the structure of the current section. 08:24:27 It looks there are not so different and your update is not so detailed for me. 08:25:56 Although I understand something different about background and the name of class. 08:28:38 Is my understanding not correct? 08:34:47 w-juso: sorry? 08:35:19 Thank you for checking. We'll consider merging the document with the same description as long as the current patch content remains the same. 08:35:53 If the patch is updated in the future and there are more different descriptions, we will consider separating the documents in same directory. 08:36:33 My comment is just a question. So, let me know if you have any concern. 08:37:13 I'm not negative to separate them if there is a reason should do so. 08:37:48 Anyway, I'll wait your notice or update for a while. 08:38:00 w-juso, I heard that you may add some TST specific information to this page such as TST's information, TST repository infromation, how to change TST's code version and so on. 08:39:17 Whether to divide the page depends on the content. Anyway, let's discuss it after sharing your such update. 08:40:00 Thanks for the comments. 08:40:22 It seems we can go to the next item. 08:40:59 Thank you for your comment. After removing the WIP I'll put it on the agenda again. 08:41:20 ok, thanks 08:41:29 #topic Confirm blueprints for Tacker Bobcat 08:41:52 yuta-kazato: please share your topic. 08:42:03 ok. 08:42:42 In previous PTG, we discussed "Confirm support versions for k8s/helm/prometheus on Tacker Bobcat" 08:42:50 #link https://etherpad.opendev.org/p/tacker-bobcat-ptg#L61 08:43:36 We had the following question from ueha-san and investigated blueprint features. 08:43:46 > How to deal with blueprint? Modify the same existing BP or add a new BP. (ueha) 08:43:56 >> I will check to modify existing blueprint in details and answer in IRC. (yuta-kazato) 08:44:41 As a result, existing BPs could be modifed/updated by the contributor himself. 08:45:24 Therefore, we propose to continuously update the following existing BP, if that is OK with Tacker team. 08:45:32 BP: Update the version of Kubernetes/Helm/Prometheus 08:45:38 #link https://blueprints.launchpad.net/tacker/+spec/update-k8s-helm-prometheus 08:46:01 That's all from my side, thanks. 08:46:07 Any comments? 08:47:35 I agree. 08:47:41 Any other comment? 08:48:03 I agree too 08:48:24 i also agree 08:49:31 Thanks all, so we will modify the same exhisting BP for supporting versions for k8s/helm/prometheus. 08:49:53 Then we will add other blueprints too (e.g., enhance-tacker-documents, support-external-keymanager, etc..) 08:50:14 LGTM, thanks. 08:51:24 Thanks. 08:51:30 All done for today, but is there any other topic? 08:52:53 Or request for review? 08:54:06 such as waiting for another +2 from takahashi-tsc :) 08:54:10 https://review.opendev.org/c/openstack/tosca-parser/+/873217 08:54:18 https://review.opendev.org/c/openstack/tosca-parser/+/873217 08:54:37 I'd appreciate if you check it, thanks. 08:55:05 one is wrong... 08:55:06 https://review.opendev.org/c/openstack/tacker/+/876949 08:55:25 Oops, sorry I'll review them soon. 08:55:54 thanks 08:56:54 seems nothing more requests. 08:57:01 So, lets close this meeting. 08:57:05 Thanks for joining, bye 08:57:15 Thanks, bye 08:57:22 bye 08:57:33 #endmeeting