h_asahina | hi, tacker-team. yasufum is not available due to machine trouble. Could ueha or takahashi-tsc start the meeting instead? | 08:05 |
---|---|---|
takahashi-tsc | Sure, I'll handle the meeeting. | 08:06 |
yasufum | hi | 08:06 |
manpreetk | hi | 08:07 |
ueha | hi | 08:07 |
masaki-ueno | hi | 08:07 |
yasufum | sorry for waiting... | 08:07 |
yasufum | Is it just starting? | 08:07 |
takahashi-tsc | no, yasufum, can you handle the meeting from now? | 08:07 |
yasufum | sure | 08:07 |
yasufum | #startmeeting tacker | 08:07 |
opendevmeet | Meeting started Tue Jun 14 08:07:58 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:07 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:07 |
opendevmeet | The meeting name has been set to 'tacker' | 08:07 |
yuta-kazato | hi | 08:08 |
yasufum | hi | 08:08 |
h_asahina | hi | 08:08 |
yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:08 |
yasufum_ | oops, I’ve terminated for a while… | 08:11 |
*** yasufum_ is now known as yasufum | 08:11 | |
*** yasufum_ is now known as yasufum | 08:14 | |
yasufum | sorry, can you see my message? | 08:15 |
ueha | yes, I can see | 08:15 |
takahashi-tsc | Now yes, | 08:15 |
yuta-kazato | yes. I can see. | 08:15 |
Ramona-ho-xu | yes | 08:15 |
yasufum | thx | 08:16 |
yasufum | manpreet: I’ d ask you again, is there any update for RBAC for heat? | 08:16 |
manpreetk | yasufum: Sorry no updates as the policy popup meeting was postpone due to OpenInfra Berlin Event. Would update once receive any information. Thanks | 08:17 |
yasufum | OK, thanks! | 08:18 |
yasufum_ | Let’s start from the first topici. | 08:20 |
yasufum_ | #topic Next PTG | 08:20 |
*** yasufum_ is now known as yasufum | 08:20 | |
yasufum | It will be held on October 17-20 at Columbus, Ohio | 08:21 |
yasufum | I mean it’s not a virtual event. | 08:21 |
*** yasufum_ is now known as yasufum | 08:24 | |
yasufum | Although we are not sure situation of COVID-19 will be well, I’d like to have a meeting on the event. | 08:24 |
yasufum_ | takahashi-tsc: My network codition is so bad, so could you host the meeting? | 08:27 |
yasufum_ | :( | 08:27 |
takahashi-tsc | sure. | 08:27 |
*** yasufum_ is now known as yasufum | 08:28 | |
yasufum | It’s just the second topic remained. | 08:28 |
yasufum | thx | 08:28 |
takahashi-tsc | yasufum, is there any other message about next PTG? | 08:28 |
yasufum | just one thing, I’d ask community if we can have hybrid meeting, onsite and online. | 08:29 |
yasufum | if possible. | 08:29 |
takahashi-tsc | Thanks. Yes it is better that PTG is hybrid meeting... | 08:30 |
takahashi-tsc | Anyway, if you get any information, please share it with us. Everyone, if you know any information, please share with us! | 08:31 |
takahashi-tsc | Then can we move to next topics? edagawa_kc, can you start? | 08:32 |
edagawa_kc | Sure. | 08:33 |
edagawa_kc | I would like to discuss the pagination feature in CLI. | 08:33 |
edagawa_kc | I have implemented the feature in Tacker server side according to ETSI SOL013 in Yoga cycle. Now I am considering how to design the pagination feature also in CLI side. | 08:33 |
edagawa_kc | In Zed vPTG, I have suggested some options for the design, but no conclusion have been reached. Now I would like to suggest a new option which can solve demerits in existing ones. | 08:34 |
edagawa_kc | I described the detail of that in [New option] part in the etherpad. | 08:34 |
edagawa_kc | I investigated the feasibility about this behavior, and found there already is the code which possibly enable such a behavior in client side. | 08:35 |
edagawa_kc | Therefore I would like to suggest implementing this CLI feature into target APIs according to existing code. | 08:35 |
edagawa_kc | That's all from my side. | 08:36 |
takahashi-tsc | Thanks, in my understanding, "suggested some options" is | 08:37 |
takahashi-tsc | https://etherpad.opendev.org/p/tacker-zed-ptg#L109 | 08:37 |
takahashi-tsc | Is it correct? | 08:37 |
edagawa_kc | Yes, correct. | 08:37 |
takahashi-tsc | OK, thanks. Any comments? | 08:38 |
ma-ooyama | I have a comment. | 08:38 |
ma-ooyama | As the user, we want to retrieve all records by executing a command only once. | 08:39 |
ma-ooyama | So I think the implementation of "New option" looks good. | 08:39 |
edagawa_kc | Thank you for the comment, I see. | 08:40 |
takahashi-tsc | thanks, any other comments? I also think new option is better, because there is already some implementation. | 08:41 |
hirofumi-noguchi | Let me confirm the processing of new option. | 08:43 |
hirofumi-noguchi | With this new option, all_record functionality implemented on the client side and normal paging process is executed on the server side? | 08:45 |
hirofumi-noguchi | v2 API doesn't support the all option on the server side, but I wondered if this option could be used for v2 API. | 08:47 |
hirofumi-noguchi | Is my understanding correct or not? | 08:48 |
edagawa_kc | Your understanding is correct. In this case, server side behaves pagination. This is different from "all_records" feature in server side. | 08:49 |
hirofumi-noguchi | Thx, I see. | 08:49 |
hirofumi-noguchi | I was confused with all_record. | 08:50 |
takahashi-tsc | Any other comments? I think new option is basically agreed. Details of the spec will be discussed in gerrt. | 08:53 |
takahashi-tsc | Do anyone object new option? | 08:54 |
ueha | I agree too. thanks for suggestion the new option. :) | 08:56 |
takahashi-tsc | Good. edagawa_kc, I think you should update spec. please update your spec, and let's discuss it in gerrt. | 08:56 |
edagawa_kc | I see. I will update it and then post to gerrit. Thank you. | 08:56 |
takahashi-tsc | Good, so that's it. Any other topics for today's meeting? | 08:57 |
yasufum | nothing | 08:57 |
takahashi-tsc | OK, let's close today's meeting. Thank you everyone! bye | 08:58 |
ma-ooyama | bye | 08:58 |
ueha | thanks, bye | 08:58 |
yasufum | thanks, bye! | 08:58 |
caishuwen | bye | 08:58 |
edagawa_kc | bye | 08:58 |
manpreetk | bye | 08:58 |
takahashi-tsc | #endmeeting | 08:58 |
yuta-kazato | bye | 09:02 |
takahashi-tsc | ? The meeting is not closed yet? | 09:04 |
takahashi-tsc | #endmeeting | 09:04 |
masaki-ueno | #endmeeting seems to be enable only for the one who called #startmeeting... | 09:05 |
takahashi-tsc | Hmm, could you ask yasufum to close this meeting? | 09:07 |
takahashi-tsc | I sent email to yasufum. | 09:12 |
masaki-ueno | I also sent slack message to yasufum. Thanks :) | 09:13 |
takahashi-tsc | thanks! | 09:13 |
yasufum | #endmeeting | 09:17 |
opendevmeet | Meeting ended Tue Jun 14 09:17:04 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:17 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-06-14-08.07.html | 09:17 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-06-14-08.07.txt | 09:17 |
opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-06-14-08.07.log.html | 09:17 |
*** soniya29|ruck is now known as soniya29|ruck|afk | 09:32 | |
*** soniya29|ruck|afk is now known as soniya29|ruck | 10:23 | |
*** dasm|off is now known as dasm | 14:31 | |
*** soniya29|ruck is now known as soniya29|out | 15:21 | |
*** dasm is now known as dasm|off | 21:02 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!