05:30:40 #startmeeting tacker 05:30:41 Meeting started Wed Apr 5 05:30:40 2017 UTC and is due to finish in 60 minutes. The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:30:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 05:30:44 The meeting name has been set to 'tacker' 05:30:51 helo, guys 05:30:56 hi gongysh 05:31:02 hi all 05:31:11 hi, all 05:31:18 who are you here for tacker meeting? 05:32:24 hi all 05:32:30 hi 05:33:32 it seems other cores are all absent. 05:34:05 #topic agenda 05:34:26 #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_April_5th.2C_2017 05:34:47 as usual, we starts with review stats. 05:35:17 #link http://stackalytics.com/?metric=marks&module=tacker 05:35:28 hi 05:35:30 we are progressing. 05:35:32 KanagarajM, hi 05:35:53 you are the only one core except me here. 05:36:23 last week is a festival in China. 05:36:32 gongysh, oh ! should we skip... i saw sridhar msg on #tacker .... 05:36:54 KanagarajM, we have skipped one last week. 05:36:56 dkushwaha, hi 05:37:01 o/ 05:37:13 gongysh, yeah ! let us wait for some more time , then :) 05:37:14 gongysh, Sorry, I am late 05:37:27 dkushwaha, we are missing you. I strongly believe you will be online. 05:37:39 dkushwaha, later better than never. 05:37:54 gongysh, :) 05:38:03 Lets move to next topic. 05:38:08 #topic features and BP 05:38:27 first is the scheduling bp 05:38:37 I have received reply from mistral team. 05:38:52 the mistral PTL sugguest to use a loop like task. 05:39:17 he doest not think cron-like trigger is good for us. 05:39:36 so I have to study how the mistral to implement it. 05:39:58 I hope I will come up with a new spec to use mistral. 05:40:05 next week. 05:40:17 so this is a bp I am taking. 05:40:38 what do you have in your mind for this topic? 05:40:42 gongysh: Do you think cron-trigger is neef for this bp: https://blueprints.launchpad.net/tacker/+spec/vnf-policy-monitoring-worker? 05:40:44 what is the real usecase for using mistral ? 05:40:54 gongysh: if so, i will have a look 05:41:10 https://review.openstack.org/#/c/445543 05:41:20 I have some blocks before starting coding, listed in the draft spec. 05:41:32 tung_doan, we will not using cron-trigger. 05:42:09 tung_doan, do try using a workflow like this: a task -> a task until somethign, then tack b. 05:42:22 tack b/task b. 05:43:04 tung_doan, for the task scheduling BP, I was introduing zookeeper to do it. 05:43:06 gongysh: got it. +1 to go with mistral in the future 05:43:12 gongysh, I have a question, Will it be good to use workflow for loop like tasks? 05:43:20 but sridar thinks the mistral can do the same thing. 05:43:54 dkushwaha, I don't know, what is your opinion? 05:45:06 dkushwaha, to use mistral to implement our policy long live tasks, I cannot think any better. 05:45:52 dkushwaha, we have to try. to do the test. 05:46:03 gongysh, I am not sure, but may be in corner cases, It can be hard to handle 05:46:53 tung_doan, can you do a try on https://blueprints.launchpad.net/tacker/+spec/vnf-policy-monitoring-worker? 05:47:19 tung_doan, you can try to use a workflow to do the monitor-worker. 05:48:00 gongysh: that's something in my mind. I need to look deeply into this. 05:48:17 tung_doan, ok 05:48:30 gongysh: writing a spec will be good 05:48:37 tung_doan, then we wait for you result. 05:49:10 tung_doan, I think at the same time, you can use a try code to help your spec. 05:49:22 o/ 05:49:24 sorry got late 05:49:34 I mean upload a patch as you are writing the spec. 05:49:38 gongysh: need to ping you some time for zookkeeper support 05:49:54 tung_doan, no, you just forget the zookeeper stuff. 05:50:11 tung_doan, use mistral feature to do it. 05:50:27 if mistral can implement, we will not use zookeeper. 05:50:41 since mistral is already a part of tacker. 05:51:06 gongysh: got it. 05:51:33 next BP, YanXing_an , 05:51:45 https://review.openstack.org/#/c/445543/ 05:52:30 YanXing_an, I have a concern to use a reserved barbican tenant to keep all VIM secrets. 05:53:15 Currently no methods were found to support shared vim if we use the operator's context. 05:53:34 YanXing_an, you have said the RBAC, right? 05:53:54 gongysh, yes 05:54:22 YanXing_an, Lets later use the rbac to share the secrets later. 05:55:31 YanXing_an, so first forget the shared vim. 05:55:38 gongysh, if so, vim need support rbac too, not shared with all users. 05:56:02 YanXing_an, yes. we can introduce RBAC in tacker. 05:56:46 second. Do we need retain fernet key in local file if barbican is not available in the 05:56:46 deployment environment? 05:57:17 YanXing_an, Let's keep it for a cycle. 05:57:41 yongysh, ok 05:57:59 guys, do you have other BPs to talk? 05:58:31 my BP for OSC plugin is still in progress. 05:59:00 trinaths, ok 05:59:17 if no, lets move to next topic 05:59:17 #topic bugs 05:59:34 wait 05:59:38 @Zhou_Zhihong https://review.openstack.org/#/c/453442/ 05:59:51 I've submited a spec patch with an example of block storage. https://review.openstack.org/#/c/453442/ 06:00:06 Please do a review to help me update the spec. 06:01:02 Zhou_Zhihong, it is a newly uploaded patch. 06:01:06 great. 06:01:11 https://launchpad.net/tacker/+milestone/pike-1 06:01:32 the Pike-1 is nearing 06:01:47 we have some patches in plate. 06:02:02 Zhou_Zhihong: the BP still needs further more details. 06:02:17 For tosca translation concerns toscaparser and heat-translator projects. I still need time to look into the code and update the spec. 06:02:39 Zhou_Zhihong: ok 06:02:47 dkushwaha, https://review.openstack.org/#/c/448844/ 06:03:20 dkushwaha, I think I have dealt with your comments. 06:03:38 o/ 06:03:46 sorry got late 06:03:55 diga, welcome 06:04:01 https://review.openstack.org/#/c/448466/ 06:04:17 this is also related to service robustness. 06:05:17 do you guys have other bugs to talk? 06:06:02 tackerclient. 06:06:03 KanagarajM, one bug for your tenant_id and name uniqueness 06:06:25 KanagarajM, it seems you just dealt with creation, you missed the update API. 06:06:27 gongysh, I missed https://review.openstack.org/#/c/448844/ , will checked it again. But I i was thinking for another patch/way to handle that issue 06:06:37 https://bugs.launchpad.net/python-tackerclient/+bug/1674906 06:06:37 Launchpad bug 1674906 in python-tackerclient "failed to update is-default attribute of vim" [Undecided,In progress] - Assigned to Trinath Somanchi (trinath-somanchi-m) 06:06:53 gongysh, yeah for update i have asked trinaths to handle 06:07:27 KanagarajM: I handled it, please visit, https://review.openstack.org/#/c/449956/ 06:07:30 trinaths, we are waiting for server part to be merged. 06:07:56 trinaths, i will look into it. thanks 06:07:58 dkushwaha: sridhar opened this bug: https://bugs.launchpad.net/tacker/+bug/1678329 06:07:58 Launchpad bug 1678329 in tacker "Explicitly detect if mistral workflow missing" [Low,New] 06:08:02 https://bugs.launchpad.net/tacker/+bug/1676074 06:08:02 Launchpad bug 1676074 in tacker "Tacker server throws exception when member action contains UPDATE string." [Undecided,In progress] - Assigned to Trinath Somanchi (trinath-somanchi-m) 06:08:17 trinaths, it is just dealing with VIM update. 06:08:26 gongysh: ok 06:08:30 dkushwaha: I think it is nice to have 06:08:47 trinaths, for tenant_id and name uniqueness, we still need to take care of vnfd, nsd update. 06:09:19 tung_doan, I will check it, I assigned it to myself 06:09:21 gongysh: okay. I'm updating as per review comments related to the BUG. 06:10:04 gongysh: I will post another commit for vnfd and nsd update for tenant_id and name uniqueness. 06:10:12 gongysh: will that be okay ? 06:10:17 trinaths, ok 06:10:34 ok, do you have other bugs to talk about? 06:11:04 gongysh: only 2 as I posted earlier and the new one just got in plate. 06:11:46 jeremy_chang, hi 06:12:00 gongysh: I'm working on Pagination bug. but it takes time. 06:12:07 how is the VNFFG functional test? 06:12:18 trinaths, I know that takes time. 06:13:24 gongysh: ok 06:13:33 YanXing_an, do you have any idea about the VNFFG test? 06:13:44 Jimmy_ye is on business, he is working on https://review.openstack.org/#/c/451827/ 06:14:12 this bug blocks vnffg ft 06:14:53 YanXing_an, ok 06:15:19 I will review it. 06:15:27 netx topic 06:15:29 yongysh, he will update the patch soon. 06:15:37 #topic open discussion 06:15:48 we still have some time. 06:15:59 gongysh: about tacker api framework, I have some patches ready with new setup 06:16:00 dkushwaha, what is the progress for NS spec? 06:16:07 gongysh: I will push those for review today 06:17:37 dkushwaha, are you there? 06:18:20 ok, it seems he is not here. 06:18:30 Do you guys have some thing to talk? 06:18:42 if no, we can wrap up the meeting earlier. 06:18:50 We have less knowledge about tosca, and process in tosca-parser and heat-translator, step slowly to read the codes, do you have some helpful materials or guides? 06:18:55 gongysh: I think you haven't seen my status :( 06:19:23 diga, I know you are pushing some new patches about API. 06:19:33 gongysh: :) okay 06:20:07 since tung_doan will take the mistral test job, I will have much time to do review and some book keeper stuff. 06:20:30 just upload your patches ... 06:20:48 YanXing_an: you can refer to OASIS tosca specs 06:20:59 gongysh: i have not looked into mistral before. need time to understand this :) 06:21:25 YanXing_an: refer to slideshare or Openstack Summit videos for heat related demos or presentations 06:21:34 tung_doan, never mind. lets do it together. 06:21:46 gongysh: thanks 06:22:21 trinaths, thanks, i will look into these. 06:22:40 YanXing_an: good tutorials i think: http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/tosca-nfv-v1.0.html 06:22:52 YanXing_an: happy to help 06:23:12 YanXing_an: tosca-paser and heat-trans mainly focus on it 06:23:39 tung_doan, thanks 06:24:30 KanagarajM: Can I take this forward https://review.openstack.org/#/c/450528/ ? 06:25:37 trinaths, sure. but let me know what changes you want to make ? 06:26:20 KanagarajM: as said before, apart from vim-update, other update changes are done in this patch. 06:26:59 KanagarajM: as discussed before, do I need to post another commit on all these changes? 06:27:54 trinaths, YanXing_an , tung_doan , please pay attention to review. 06:28:02 trinaths, that patch already takes care of the create part and it can be merged now. for update fn test, its your choice :) either add new commit or use existing commit it self. 06:28:46 trinaths, you can do the update part in your own new patch. 06:29:01 KanagarajM: gongysh: okay 06:29:17 ok, now, lets end our meeting. thanks everyone. 06:29:22 #endmeeting