08:08:42 #startmeeting tacker 08:08:43 Meeting started Tue Jun 16 08:08:42 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:08:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:08:46 The meeting name has been set to 'tacker' 08:09:29 Hi 08:09:32 hi 08:09:34 hi all 08:09:36 Hi 08:09:42 I think we have two topics today 08:10:28 Patches including specs, and feedback to ETSI NFV from takahashi-tsc 08:10:57 Could you share the link? 08:11:09 which one? 08:11:22 Hi 08:11:41 Patches including specs, and feedback to ETSI NFV from takahashi-tsc --> this one 08:12:06 isn't it a topic of today? 08:12:15 patches or feedback, or both 08:12:16 ? 08:12:55 ah I thoght you mentioned it for review. 08:13:02 Don't care. 08:14:02 I hope you will review specs and add +1 if you agree to proceed it to implement. 08:14:18 OK. 08:14:22 OK 08:15:06 Usually, when we mention specific spec, we share the link:) It it good for review! 08:15:21 What is the topic today? 08:15:57 Sorry but some of my spec is WIP, I'll complete them soon... 08:17:03 I understand 08:17:31 Do we have a target deadline for it? 08:19:02 because we may have few feedback and it makes difficult to start implementations 08:20:15 yasufum, if you finish the first review for yoshito-ito, could you share the spec for review every meeting? 08:20:26 In my understanding, there is no official deadline. But I think we should make some our own deadline. Someday in July? 08:20:27 We have so many things. 08:21:02 So, we should focus on specific spec and review together in a short period. 08:21:35 Yes. We do not have as tacker team, but you can ask to be reviewed. 08:22:28 yasufum, what is the topic today? 08:23:00 From me, asking reviewing and confirm the status. 08:23:05 coud you mention the topic using #-topic?? 08:23:15 And get feedback hopefully. 08:23:31 It is not a specific topic 08:24:05 If you have specific topic, you can use topic tag. 08:25:24 takahashi-tsc and yoshito-ito, is it OK to complete review your patches in July, or before? 08:25:31 I don't have specific topic today... 08:25:53 yoshito-ito, if you finish the spec, I will reivew it soon. 08:26:17 OK, thanks 08:26:22 :) 08:31:18 I think it is OK that my 3 specs review is complete in July... But anyway, I clarify the deadline for each patch. 08:32:03 OK 08:32:57 Other than specs, I would like to have reviewing from yours for these patches. 08:33:06 https://review.opendev.org/#/c/734784/ 08:33:13 https://review.opendev.org/#/c/733721/ 08:33:21 https://review.opendev.org/#/c/735500/ 08:34:07 last one is already reviewed by takahashi-tsc, thanks 08:34:28 Yes, our team start to review these patches. 08:35:45 thanks 08:35:59 If you do not have comments anymore, go to the next topic 08:36:28 For the first patch (https://review.opendev.org/#/c/734784/), Ueha is also submitting a patch to tosca-parser 08:36:46 so it's better to see the status in tosca-parser, too 08:36:56 just a comment for the sharing status 08:38:05 https://review.opendev.org/#/c/735311/ 08:38:19 pls go to the next topic 08:38:49 thanks yoshito-san! 08:39:27 Sure, we also review tosca-parser patch. 08:40:22 takahashi-tsc: is it ready for discussion today? https://etherpad.opendev.org/p/tacker-meeting 08:41:56 Yes, please see L26-53. I wrote my opinion about what we request to ETSI NFV-TST. 08:42:19 #topic etsi-nfv-tst 08:43:04 My opinion is members who make specification (ETSI NFV members) should also make API test. So I'd like to ask it to TST. 08:44:20 i agree 08:44:50 TST already make some API test using Robot framework, but I want to improve coverage. So first, I ask increase Response code coverage. 08:45:26 Is there any comment about it, i.e. L31-40? 08:46:12 I think all tests for 2xx and 4xx are TST's role. 5xx is difficult.. 08:46:46 I agree. 08:47:13 At least, we need a coverage info in TST codes. 08:47:58 now we need to read through the souce to check the coverage 08:47:58 Yes, TST said just "All APIs are covoerd". but it is not enough. 08:49:03 We need more detailed coverage info. So I will propose the 1 view point "Response Code" and my opinion. 08:50:24 OK, so I'd like to get Tacker teams comment about response code coverage. And I also want is there any other view point of coverage? 08:51:34 I wrote Input Parameter coverage. Is there any other point? 08:52:28 How about "response header"? 08:55:18 According to SOL002/003, while response, "Location" info HTTP header. 08:55:42 "Location" should be available in HTTP header with response code 08:56:28 OK, i find such description in Spec document.It is possible as viewpoint. 08:57:01 Thanks! 08:58:23 I think we have no time today... So please write your comment in etherpad. 08:59:04 thanks 09:00:13 takahashi-tsc: Do yo think when do we fix our requirements for TST? 09:01:35 About coverage, I want to decide by next this weekly meeting. But I think we do not have to make perfect request. I want to continue to discuss. 09:02:18 So at next week, I want to decide what I propose to TST. TST meeting is on 30th June. 09:03:07 OK, make an agreement in next meeting. I would like to add my comment 09:03:37 Thanks for leading this activity 09:04:30 If you do not have any other topic, close this meeting. 09:05:14 seems nothing. thanks for joining today. 09:05:17 bye 09:05:20 bye 09:05:23 #endmeeting