| *** hemna9 is now known as hemna | 07:38 | |
| yasufum | Hi tacker team | 08:00 |
|---|---|---|
| takahashi-tsc | hi | 08:00 |
| manpreetk | Hi | 08:00 |
| ueha | hi | 08:00 |
| edagawa_kc | Hi | 08:01 |
| esto-aln | Hello | 08:01 |
| yasufum | #startmeeting tacker | 08:01 |
| opendevmeet | Meeting started Tue Jan 25 08:01:56 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 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:03 |
| yasufum | esto-aln: thx for updating the etherpad | 08:04 |
| yasufum | and we have two topics today. | 08:04 |
| yasufum | First one is from edagawa_kc | 08:05 |
| yasufum | Do you have any trouble for the gate test, right? | 08:05 |
| yasufum | could you share your topic? | 08:06 |
| edagawa_kc | Sure. | 08:06 |
| edagawa_kc | At first, thank you for your reviewing the spec of this feature. | 08:06 |
| edagawa_kc | Currently I'm in functional testing phase and facing two issues. | 08:07 |
| edagawa_kc | Issue 1: Functional test of paging records causes TIMED_OUT in Zuul due to handling large number of pages. | 08:07 |
| edagawa_kc | Issue 2: Appropriate default number of records contained in a page hasn't been decided (currently defined "100" as tentative). | 08:07 |
| edagawa_kc | The detail is described in etherpad. I would like to ask your opinions/ideas to resolve them. | 08:08 |
| edagawa_kc | Regarding issue 1, I suggested five options to avoid issue. For my side, option 1' or 2 is better way, but I want to ask your opinion. | 08:11 |
| yasufum | Before that, there are several failures not only in ft but also others such as tox-cover | 08:12 |
| yasufum | Don't we need to take care about them now? | 08:12 |
| edagawa_kc | Yes, I have already noticed that and will fix it. | 08:12 |
| yasufum | ok | 08:12 |
| edagawa_kc | That' all from my side. | 08:15 |
| ueha | As for option 2, you wrote "it affects other existing test cases using tacker.conf.", what kind of effect does it have? | 08:19 |
| yasufum | Alhtough I don't how much time cost for the test itself, is opt 3 available? | 08:20 |
| ueha | If paging does not work in other tests, I think there is no effect. right? If so, I think Option 2 is simple and good. | 08:22 |
| edagawa_kc | As for the effect of option 2, for example, if we want to verify new test case with using value "3" for future, it needs changing tacker.conf definition. | 08:26 |
| edagawa_kc | I'm afraid the word "existing" is somehow incorrect. It means "the other tests". | 08:27 |
| ueha | Thanks, I got it. If we use option 1' or 3, do you mean that we can test according to the value? | 08:31 |
| edagawa_kc | As for issue 3, current behavior is that instantiation and termination repeats many times and each operation needs time to be completed. | 08:34 |
| edagawa_kc | Ｉ intend to fix this behavior more and shorten TAT so as not to become TIMED_OUT. | 08:35 |
| edagawa_kc | For example, preparing large records as pre-condition, using FAILURE process on purpose, etc., | 08:38 |
| yasufum | It seems so expensive comparing with our purpose of the test... | 08:40 |
| edagawa_kc | "If we use option 1' or 3, do you mean that we can test according to the value?" -> In option 1', actual paged behavior is only once. | 08:41 |
| ueha | The time out occur because it have to do a lot of LCM operations to prepare the data to test the paging query.. | 08:41 |
| yasufum | I think the feature is not so important actually as introducing a new FT. | 08:41 |
| yasufum | ueha: What do you think? | 08:41 |
| ueha | Yes, I think so. | 08:42 |
| edagawa_kc | You are mentioning Option 4, aren't you? | 08:44 |
| yasufum | If it's reasonable for the purpose | 08:44 |
| yasufum | In my conclusion, it's ok to implement is as UT, but how to test should be discussed later, on gerrit possibly. | 08:45 |
| edagawa_kc | Understood. | 08:47 |
| yasufum | edagawa_kc: Is the issue 2 also about the FT? | 08:48 |
| edagawa_kc | Issue 2 affects entire paging feature, but we can also discuss this issue on gerrit. | 08:50 |
| yasufum | got it | 08:50 |
| yasufum | I've just wondered if we can skip the issue2 because we don't so much time today. | 08:51 |
| yasufum | So, go to the next topic. | 08:51 |
| yasufum | hirogumi-noguchi: can you share your topic? | 08:52 |
| hirofumi-noguchi | sure | 08:52 |
| hirofumi-noguchi | My topic is about proposal to abolish default vim. | 08:52 |
| hirofumi-noguchi | Current Tacker can register default VIM, which is used when some API requests and Grant response does not include vimConnectionInfo > vimId. | 08:52 |
| hirofumi-noguchi | Though this implementation has advantages, there are also problems with vim's policy such as an issue which we have discussed last week in “About multi-tenant policy (ma-ooyama)”. | 08:53 |
| hirofumi-noguchi | When instantiation is executed without specifying VIM, the default VIM of the user who executes instantiate is selected. | 08:53 |
| hirofumi-noguchi | I think vim should be specified in the API request or Grant response basically. | 08:54 |
| yasufum | sure | 08:54 |
| hirofumi-noguchi | So I don't think the lack of a default vim is a problem. | 08:54 |
| hirofumi-noguchi | In my opinion, it is better that Tacker will return error in cases where the default vim was previously required. | 08:54 |
| hirofumi-noguchi | Since default vim is outside the scope of ETSI NFV SOL, I think it is an implementation issue. | 08:55 |
| hirofumi-noguchi | I would like to hear your opinions. | 08:55 |
| hirofumi-noguchi | That' all from my side. Thank you. | 08:55 |
| yasufum | thanks | 08:56 |
| yasufum | I'm not sure the reason why default vim was introduced, I agree with hirofumi | 08:57 |
| yasufum | because we don't need to have difficulties discussed as previous meeting | 08:58 |
| yasufum | if we drop the feature | 08:58 |
| yasufum | I think it's simple and better. | 08:58 |
| hirofumi-noguchi | I think the default vim is inherited from the legacy code. | 09:01 |
| yasufum | My only concern is that there is any operator expectig to use default vim. | 09:01 |
| hirofumi-noguchi | Regarding vim registration, SOL code also uses a legacy implementation. | 09:01 |
| yasufum | Is there any comment for the suggestion? | 09:03 |
| takahashi-tsc | I also agree that we do not need features for default VIM, And I also want to know operator's opinion. | 09:04 |
| ueha | +1, sorry for late because my computer was freezed.. | 09:08 |
| yasufum | I think it's almost unlikely that operators want to keep default vim in tacker personally. | 09:09 |
| yasufum | There are no objections right now. | 09:11 |
| yasufum | hirofumi: Could you upload a blueprint for the topic as first step, | 09:11 |
| hirofumi-noguchi | I got it. | 09:11 |
| ma-ooyama | I don't have clear opinion about whether default vim is needed. | 09:12 |
| ma-ooyama | But it is possible that some user may use NFVO that use default VIM because of limitation of its implimentation, but sorry I don't know the case. | 09:12 |
| yasufum | OK, thanks. | 09:12 |
| yasufum | Please continue to discuss because it's no urgent topic. | 09:14 |
| yasufum | We can have discussion in the next ptg if it's needed. | 09:15 |
| hirofumi-noguchi | OK. I got it. Thank you. | 09:17 |
| yasufum | ma-ooyama: I'd appreciate if you give us any futher update, especially about NFVO stand point. | 09:17 |
| yasufum | Any other comment? | 09:19 |
| ma-ooyama | Sure, I will. | 09:19 |
| yasufum | ma-ooyama: thanks | 09:20 |
| yasufum | seems nothing more | 09:20 |
| yasufum | So, wrap up this meeting | 09:21 |
| yasufum | Thank you for joining, bye! | 09:21 |
| takahashi-tsc | thanks, bye! | 09:21 |
| h-asahina_ | bye | 09:21 |
| manpreetk | bye | 09:21 |
| ueha | Thanks, bye. | 09:21 |
| ma-ooyama | thanks, bye | 09:21 |
| esto-aln | thanks, bye | 09:21 |
| hirofumi-noguchi | Thanks, bye. | 09:21 |
| yasufum | #endmeeting | 09:21 |
| opendevmeet | Meeting ended Tue Jan 25 09:21:44 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:21 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-01-25-08.01.html | 09:21 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-01-25-08.01.txt | 09:21 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-01-25-08.01.log.html | 09:21 |
| *** soniya29 is now known as soniya29|afk | 11:56 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!