| yasufum-o | Hi tacker team. | 08:01 |
|---|---|---|
| manpreetk | Hi | 08:01 |
| ueha | Hi | 08:01 |
| takahashi-tsc | hi | 08:01 |
| yasufum-o | #startmeeting tacker | 08:02 |
| opendevmeet | Meeting started Tue Nov 8 08:02:07 2022 UTC and is due to finish in 60 minutes. The chair is yasufum-o. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:02 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:02 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:02 |
| yasufum-o | #link https://etherpad.opendev.org/p/tacker-meeting | 08:02 |
| yasufum-o | There three items on the etherpad today. | 08:03 |
| yasufum-o | But the second one seems we already discussed in the previous meeting. | 08:04 |
| yasufum-o | So, two items actually. | 08:05 |
| yasufum-o | manpreetk: can you start from your item? | 08:05 |
| manpreetk | Sure thanks | 08:05 |
| yasufum-o | Thanks for the update. | 08:05 |
| yasufum-o | #topic Tacker Bug Triage Discussion | 08:06 |
| manpreetk | My topic is regarding Bug Triage. In OpenStack 2023.1 Antelope cycle proposal is to categorise and prioritise bugs with status "New". | 08:06 |
| manpreetk | If ee we agree with the proposal then I would like to seek your opinion regarding suggestions shared in etherpad https://etherpad.opendev.org/p/tacker-bugtriage. | 08:06 |
| manpreetk | * Action Items | 08:06 |
| manpreetk | * Participation and Duration | 08:06 |
| manpreetk | * Open Questions | 08:06 |
| manpreetk | So "Action item" comprise of how to categorise and prioritise with reference to OpenStack Bug Triage process. | 08:09 |
| manpreetk | But how to conduct this Bug Triage activity in Tacker? | 08:10 |
| manpreetk | If you guys have any suggestion/feedback/improvement please let me know. | 08:10 |
| yasufum-o | thanks | 08:12 |
| yasufum-o | any comment? | 08:13 |
| manpreetk | Additionally "Open Questions" would also help in categorising and prioritising bugs, need your opinion here as well. | 08:15 |
| yasufum-o | Fist of all, we don't have critical issues so much on the launch pad, right? | 08:15 |
| manpreetk | Yes | 08:16 |
| yasufum-o | I understand one of the main issue on your suggestion is to discard old issues labeled as "New". | 08:17 |
| yasufum-o | Is that correct? | 08:17 |
| manpreetk | Yes, correct. | 08:18 |
| yasufum-o | OK, thanks. | 08:19 |
| yasufum-o | I agree with your proposal to treat future bugs will be registered as described on your etherpad. | 08:20 |
| yasufum-o | For the existing bugs, espcecially too old ones, I think we don't take care so much. | 08:23 |
| yasufum-o | s/don't/shouldn't/ | 08:24 |
| yasufum-o | manpreetk: what do you think? | 08:24 |
| manpreetk | Agree | 08:24 |
| yasufum-o | And I think it's enough to change the status for now. | 08:25 |
| yasufum-o | Do you have any idea which status is the most appropriate for that? | 08:26 |
| manpreetk | IMO, "Wont fix" looks fine to me, though we need to explain reason in comment. | 08:27 |
| yasufum-o | Any other comment, team? I think "Incomplete" or "Opinion" might be also fine. | 08:30 |
| yasufum-o | nothing? | 08:32 |
| yasufum-o | OK | 08:33 |
| yasufum-o | manpreetk: let's fix it to change to "Won't Fix" for now. | 08:34 |
| manpreetk | Ok, meanwhile I ll check with other projects their practise for such scenario. | 08:35 |
| yasufum-o | sounds good | 08:35 |
| manpreetk | Could you please share your valuable opinion for keeping this activity Volunteer basis and schedule (weekly/ bi-weekly/monthly) and how to share triage results? | 08:38 |
| yasufum-o | I'm expecting the number of bugs is not so much for our team, bi-weekly is enough for me. | 08:39 |
| manpreetk | Ok | 08:39 |
| yasufum-o | For the old bugs, should we wait for your update of how other projects treating such a bugs? | 08:41 |
| manpreetk | Yes i ll update the etherpad with findings. | 08:42 |
| yasufum-o | good | 08:42 |
| manpreetk | We can initiate activity from our next IRC meeting. What do you think? | 08:42 |
| yasufum-o | agree | 08:42 |
| manpreetk | Thank you so much. | 08:43 |
| yasufum-o | Thanks for your contribution! | 08:43 |
| yasufum-o | move on to the next topic? | 08:44 |
| yasufum-o | hiromu: can we skip your item because it was discussed last week? | 08:46 |
| yasufum-o | Hmm, he might be off today. | 08:47 |
| yasufum-o | ma-ooyama: Are you here? | 08:48 |
| ma-ooyama | Yes. | 08:48 |
| yasufum-o | Thanks. It's your turn. | 08:48 |
| yasufum-o | #topic Introducing issues we want to work on at Antelope | 08:48 |
| ma-ooyama | Sure. Thanks. | 08:48 |
| ma-ooyama | After the last Operator Hour at PTG, we understood tacker has some issues to continuously discuss. | 08:49 |
| ma-ooyama | I know it is better to extract general issues about tacker as soon as possible, but at this time, I'll introduce some specific issues that I want to improve in Antelope. | 08:49 |
| ma-ooyama | I'm sorry that I couldn't introduce the issues at last PTG, but I would appreciate it if you allow me to explain the issues. | 08:49 |
| ma-ooyama | First issue is about using object storage. | 08:50 |
| ma-ooyama | As discussed in operator hour, how to store VNF packages is one of specific points to be discussed. | 08:50 |
| ma-ooyama | The better way to store vnf packages should be discussed in community, but at least, functionality of adapting object storage can be one of options for users. | 08:51 |
| ma-ooyama | So we would like to work on adding the functionality in the Antelope. | 08:51 |
| ma-ooyama | But we couldn't confirm whether tacker has already been able to use object storage or not. So if tacker could, we want to just add the document about how to use object storage. | 08:51 |
| ma-ooyama | What do you think about this first proposal? | 08:52 |
| yasufum-o | Thanks for your updates for the topic. | 08:53 |
| yasufum-o | I don't know about current impl of object storages actually. | 08:55 |
| yasufum-o | ueha: Do you have any suggestion for the proposal? | 08:56 |
| ueha | Sorry, I don't know about current impl too. | 08:57 |
| yasufum-o | ok, thx | 08:57 |
| ueha | How difficult does it take to check if block storage can be used? | 08:58 |
| ueha | sorry, s/block/object | 08:58 |
| ma-ooyama | I think it is not so difficult. | 08:59 |
| ma-ooyama | So at least, we must confirm whether tacker could use object storage or not as soon as possible. | 08:59 |
| yasufum-o | ma-ooyama: I'm not opposit to your proposal. | 09:00 |
| ma-ooyama | Thanks. So we will first confirm current impl. | 09:01 |
| ma-ooyama | Then to implement the function or write document. | 09:02 |
| ma-ooyama | Is it OK? | 09:02 |
| yasufum-o | I'd like to ask you to propose a spec for the feature. | 09:02 |
| ma-ooyama | Sure. We will make a spec before implementation. | 09:04 |
| yasufum-o | thanks | 09:04 |
| ma-ooyama | Thank you for your comments. | 09:06 |
| yasufum-o | can we move on to the next topic, improving mgmt driver log? | 09:06 |
| ma-ooyama | Sure. | 09:06 |
| ma-ooyama | Sorry. Are there any other comments? | 09:06 |
| ma-ooyama | So let me explain second topic. | 09:07 |
| ma-ooyama | As discussed in operator hour, there were a opinion that the mgmt driver log can be improved. | 09:08 |
| ma-ooyama | For example, when vnf configuration using ansible playbook fails, we couldn't know where or how the playbook fails from the messge displayed by vnflcm op show command. | 09:08 |
| ma-ooyama | So we want to implement the interface that pass such as ansible's error message to tacker and enable tacker to show the details of error. | 09:08 |
| ma-ooyama | What do you think about this? | 09:10 |
| yasufum-o | Is it not enough to change output to other than stdout? | 09:10 |
| yasufum-o | output to a file, for instance. | 09:11 |
| ma-ooyama | I think it is useful if users can see the details by executing command. | 09:13 |
| yasufum-o | I've just looking here | 09:13 |
| yasufum-o | #link https://docs.ansible.com/ansible/2.9/reference_appendices/logging.html | 09:13 |
| yasufum-o | It might be feasuble to change the configuration, although not sure if it doable in tacker. | 09:15 |
| ma-ooyama | You think it doesn't need to pass the ansible output to tacker because user can store the log to some files, right? | 09:17 |
| yasufum-o | might be yes | 09:18 |
| yasufum-o | although I don't udnerstand your exact requirement for the issue. | 09:18 |
| yasufum-o | If you want to jsut get whole logs on stdout, I think it's enought to change the output. | 09:20 |
| yasufum-o | what do you think? | 09:20 |
| ma-ooyama | Do you mean the logs will displayed in stdout after executing lcm command like instatiation? | 09:24 |
| yasufum-o | I don't understand the behavior of logging in ansible so much. So we need to have some more survey. | 09:26 |
| yasufum-o | I don't have any answer for your question, sorry. | 09:27 |
| ma-ooyama | Sorry, our proposal is too abstract. | 09:27 |
| ma-ooyama | So is it OK to discuss this based on spec. | 09:28 |
| yasufum-o | You don't need to give us a spec if no new feature will be proposed. | 09:29 |
| yasufum-o | Please continue us to discuss on the etherpad and chat. | 09:30 |
| ma-ooyama | Sure. Thanks. | 09:31 |
| ma-ooyama | So we'll add more concrete proposal to ehterpad. | 09:31 |
| yasufum-o | thanks | 09:31 |
| yasufum-o | It must be so helpful for us. | 09:32 |
| yasufum-o | So, lets close this meeting because it's 30 mins over the end of the meeting. | 09:33 |
| yasufum-o | If no more comments. | 09:33 |
| takahashi-tsc | Nothing from my side. | 09:33 |
| yasufum-o | thanks | 09:34 |
| yasufum-o | See you next week, bye! | 09:34 |
| takahashi-tsc | bye | 09:34 |
| ma-ooyama | Thanks, bye. | 09:34 |
| manpreetk | Thanks for discussion. Bye! | 09:34 |
| ueha | Thanks, bye | 09:35 |
| yasufum-o | #endmeeting | 09:35 |
| opendevmeet | Meeting ended Tue Nov 8 09:35:07 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:35 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-08-08.02.html | 09:35 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-08-08.02.txt | 09:35 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-08-08.02.log.html | 09:35 |
| *** dasm|off is now known as dasm | 14:02 | |
| *** dasm is now known as dasm|off | 22:28 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!