| yasufum | Hi, tacker team. | 08:00 |
|---|---|---|
| manpreetk | hi | 08:00 |
| Ramona-ho-xu | hi | 08:00 |
| ueha | hi | 08:00 |
| yasufum | #startmeeting tacker | 08:00 |
| opendevmeet | Meeting started Tue Aug 2 08:00: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:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:00 |
| yuta-kazato | hi | 08:01 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:01 |
| yasufum | As you may notice, we have some problems on zuul gate tests. | 08:02 |
| yasufum | ueha has shared the causes and candidate fixes. | 08:03 |
| yasufum | could you share your item? | 08:03 |
| ueha | Sure | 08:03 |
| yasufum | #topic sharing about current zuul testing | 08:03 |
| yasufum | pls go ahead | 08:03 |
| ueha | First of all, regarding UT error, | 08:03 |
| ueha | An update of the jsonschema is causing an IP address validation failure (mismatch_error). | 08:04 |
| ueha | Yi Feng reported in bug report https://bugs.launchpad.net/tacker/+bug/1983067 . | 08:04 |
| ueha | This is because the fake data value used in the test is incorrect. It is defined "192.168.11.01" as IP address. | 08:06 |
| yasufum | It's silly actually :) | 08:06 |
| ueha | And now, this problem fixed in the patch posted by Yi Feng. | 08:07 |
| ueha | > Fix IPv4 check failure in UT: https://review.opendev.org/c/openstack/tacker/+/851478 | 08:07 |
| ueha | UT now passes in above patch! However, the other FT error occurs.. (Also occurs in other patches) | 08:07 |
| ueha | Next, regarding the FT error, | 08:08 |
| ueha | The error occurs on the start of the ceilometer, 500 error seems to occurs in gnocchiclient | 08:09 |
| ueha | The same error occurred in the following ceilometer patch, so I think we must wait for a fix of ceilometer or library related with gnocchi. | 08:10 |
| ueha | We haven't looked into the exact cause, but if it takes too long to fix, we might need to consider a workaround.. | 08:10 |
| ueha | That's all from myside. thanks | 08:10 |
| yasufum | Thanks | 08:11 |
| yasufum | Any comment? | 08:11 |
| manpreetk | ueha: Suggestion, we could ask telementry guys to look into ceilometer issue on priority. | 08:12 |
| yasufum | great! | 08:12 |
| ueha | Sure, I haven't contacted the teletemtry team yet. | 08:13 |
| manpreetk | Okiee | 08:13 |
| yasufum | hirofumi-noguchi: Do you have any comment because you've also started to start the FT error? | 08:13 |
| yasufum | s/to start/to fix/ | 08:14 |
| hirofumi-noguchi | I agree with ueha. I would like to wait for a fix of ceilometer. | 08:15 |
| ueha | The ceilometer patch has occured same problem, so I think it is handled with high priority in their team, but I will report to them. | 08:15 |
| yasufum | Thanks both for your help. | 08:17 |
| yasufum | It seems enough for the first item. | 08:17 |
| yasufum | Let's move on to the next one. | 08:18 |
| yasufum | #topic An observation in the existing VNF LCM Multi-tenant policy design | 08:18 |
| yasufum | from manpreetk | 08:18 |
| manpreetk | Shall I proceed? | 08:18 |
| yasufum | sure | 08:18 |
| manpreetk | Thanks | 08:18 |
| manpreetk | In current VNF LCM Multi-tenant policy implementation to get details of a subscription or VNF package of a different tenant returns HTTP code 204 (No content) in response. Please find details in L42. | 08:18 |
| manpreetk | In our(NEC) opinion HTTP status code should be 404 (Not found). | 08:18 |
| manpreetk | 08:18 | |
| manpreetk | Please share your valuable opinion for the same, what according to you is the *correct* status code 204 or 404 in above scenario? | 08:18 |
| yasufum | Thanks. | 08:24 |
| yasufum | Do you have any comment for the topic? | 08:25 |
| w-juso | As an addition, we think that 204 is not possible because SOL003 5.4.3.3.2 only allows 200 OK. | 08:26 |
| w-juso | https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf | 08:26 |
| yasufum | hmm... | 08:26 |
| ueha | I have a question, what about Individual VNF Instance or other Individual Resources? | 08:27 |
| ueha | return 404 Notfound..? | 08:28 |
| ueha | I was curious because only Subscription and Package were mentioned. | 08:29 |
| manpreetk | ueha: I have observed behaviour in multi tenant env, need to check for single VNF instance. | 08:31 |
| masaki-ueno | I think 4xx errors seems to be correct to be returned, but there may be some choices for the error. | 08:33 |
| masaki-ueno | I mean, 403 and 404 are possible for that kind of situation | 08:34 |
| takahashi-tsc | masaki-ueno: yes, actually we have similar discussion... My opinion is 404 is better, but what do you think? | 08:35 |
| masaki-ueno | However, in general, accessing to unauthorized resources should be returned 404 error. | 08:36 |
| masaki-ueno | (As you know, SaaS services such as Github has such behavior :) | 08:37 |
| masaki-ueno | So I think 404 seems to be more reasonable according to generic HTTP usage | 08:37 |
| takahashi-tsc | +1 | 08:37 |
| ueha | +1. Also, I think it is necessary to investigate if there is an effect on other Individual Resources such as VNF instance, OpOccs, etc. | 08:40 |
| yasufum | manpreetk: Could you make it clear the next work item on the etherpad if no other opposition? | 08:42 |
| manpreetk | yasufum: Sorry could you please explain what is required from me regarding next work item? I do not understand :( | 08:45 |
| yasufum | Just note the conclusion on the meeting. | 08:45 |
| manpreetk | Understood | 08:46 |
| yasufum | The last item is just a confirmation of reviewing remained specs. | 08:49 |
| yasufum | I think only one spec remained for the release, and all other ones have already merged. | 08:51 |
| yasufum | #link https://review.opendev.org/c/openstack/tacker-specs/+/834156 | 08:52 |
| yasufum | mapreetk: Could I confirm the status of your spec? | 08:52 |
| yasufum | I'm not sure there is any concerns about RBAC for the spec, or nothing on the release. | 08:54 |
| yasufum | because I cannot catch up the discussion, sorry... | 08:55 |
| yasufum | manpreetk: is it ready to be merged? | 09:00 |
| manpreetk | The spec needs some update work, as per investigation "heat" only allows "admin" role user to create stack. So such details need to be add in spec. | 09:01 |
| yasufum | OK, thanks. | 09:02 |
| yasufum | So, all topics done for today, but do you have any other comment? | 09:04 |
| yasufum | Or reqeust for review? | 09:04 |
| yasufum | good | 09:06 |
| yasufum | Let's close this meeting. | 09:07 |
| yasufum | Thank you for joining, bye! | 09:07 |
| yuta-kazato | thanks. bye! | 09:07 |
| masaki-ueno | bye | 09:07 |
| ueha | thanks, bye | 09:07 |
| manpreetk | Thanks all, bye | 09:07 |
| takahashi-tsc | bye | 09:07 |
| ma-ooyama | bye | 09:07 |
| w-juso | bye | 09:07 |
| Ramona-ho-xu | bye | 09:08 |
| yasufum | #endmeeting | 09:08 |
| opendevmeet | Meeting ended Tue Aug 2 09:08:06 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:08 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-08-02-08.00.html | 09:08 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-08-02-08.00.txt | 09:08 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-08-02-08.00.log.html | 09:08 |
| hirofumi_ | bye | 09:08 |
| *** tosky_ is now known as tosky | 10:24 | |
| *** dasm|off is now known as dasm | 11:06 | |
| *** priteau_ is now known as priteau | 12:38 | |
| *** dansmith_ is now known as dansmith | 13:46 | |
| *** bauzas is now known as bauzas_away | 18:17 | |
| *** kopecmartin_ is now known as kopecmartin | 19:09 | |
| *** dasm is now known as dasm|off | 21:09 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!