08:03:07 #startmeeting tacker 08:03:08 Meeting started Tue Dec 4 08:03:07 2018 UTC and is due to finish in 60 minutes. The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:11 The meeting name has been set to 'tacker' 08:03:23 #topic Roll Call 08:03:38 who is here for Tacker weekly meeting? 08:03:59 O/ 08:04:08 hi bhagyashris_ 08:04:15 Hi 08:04:17 o/ 08:04:24 phuoc, hi 08:04:53 dkushwaha, bhagyashris_ hi :) 08:06:01 seems no more members available 08:06:09 #chair phuoc 08:06:10 Current chairs: dkushwaha phuoc 08:06:18 hi, I'm late 08:06:33 joxyuki, hello 08:07:20 #topic BPs 08:08:01 about force delete BP 08:09:04 phuoc, have you pushed any patch? If so link please 08:09:06 Hi 08:09:08 I uploaded 2 patch sets: https://review.openstack.org/#/c/620381 and https://review.openstack.org/#/c/620385 08:09:51 phuoc, great 08:10:15 we can start with client first, and I can update in Tacker server later 08:11:14 phuoc, https://review.openstack.org/#/c/620385/1/tacker/api/v1/base.py 08:11:42 phuoc, in #397 08:11:53 what body will have? 08:13:05 dkushwaha, body likes {'vnf': {'attributes': {'force': True}}} 08:13:57 you can see it here, https://review.openstack.org/#/c/620381/2/tackerclient/tacker/v1_0/vnfm/vnf.py 08:16:07 phuoc, sounds good 08:16:39 phuoc, do you have plan to push patch, resource specific or combine patch for all 08:16:40 ? 08:17:12 like VNF, VNFFG 08:17:36 I prefer separate them into 3 parts 08:18:35 phuoc, fine. Ok I will update the spec accordingly 08:20:09 moving on 08:20:40 BP Mistral workflow monitoring 08:20:51 #link https://review.openstack.org/#/c/486924/ 08:21:14 phuoc, regarding your comment 08:22:03 Do you mean to use new context (i.e. generate_tacker_service_contex) for monitoring ?? 08:23:24 https://github.com/openstack/tacker/blob/master/tacker/context.py#L180 08:23:47 I think you can update it like this way 08:25:16 because I see in your patch, some parameters are fixed 08:25:48 phuoc, yea, i have to remove those hardcoded values. 08:26:57 but I am not sure, how generate_tacker_service_contex will be helpful here 08:27:38 removing hard coded is fine to me 08:28:02 ok, I will re-look my patch again, and will fix your comments 08:29:13 moving on 08:29:32 bhagyashris_, do you have something to discuss ? 08:29:52 yes 08:29:54 Thank you dkushwaha, joxyuki and phuoc for your response regarding HealVnfRequest data http://paste.openstack.org/show/735705/ . 08:30:08 Now I will start the implement of vdu_autoheal monitoring policy action according to the request data mentioned in reference link. 08:30:29 One thing would like to propose here is Should we use versioned object for HealVnfRequest data. 08:31:29 bhagyashris_, what is mean by "version object" ? 08:33:27 I don't think so, because API has its version in URI 08:34:49 I mean version object means https://github.com/openstack/oslo.versionedobjects/tree/master/oslo_versionedobjects 08:34:50 dkushwaha: What Bhagyashri is suggesting is instead of passing dict everywhere let's start using oslo Versioning objects 08:35:30 dkushwaha: We can start using oslo_versionedobjects for HealVNFRequest 08:36:02 tpatil, is there any related link? kindly share the same 08:36:16 i needs to look into that 08:36:22 I didn't tried it, so I want to see how it works 08:36:54 In nova project it is used widely 08:37:07 Currently all the core projects are using the Oslo versioned objects https://github.com/openstack/nova/tree/master/nova/objects 08:38:28 phuoc, any suggestion on that. ^^ 08:38:54 tpatil, bhagyashris_ I will check first and then let you know 08:39:12 I think we can do that way 08:39:28 I will check it too. 08:40:09 The drawback of dict is you don't know what attributes are present in HealVNFRequest or a VNF. If you convert it to oslo versioned object, it will be clear 08:41:02 For now, we suggest to implement it for HealVNFRequest and in future we can implement it for all cases 08:42:12 it's fine to me 08:42:29 phuoc: Thanks 08:42:38 tpatil, do you have an exmple of other case? 08:42:53 VNF dict, it's a big one 08:43:30 OK, got it. 08:43:39 bhagyashris_, tpatil sounds good as other core projects also using the same. so it seems fine to me.(although in between i will explore it and let you know in case of any query) 08:43:44 VNFD, Triggers etc etc 08:44:48 binh_, hi 08:44:49 dkushwaha, joxyuki phuoc: ok. Thank you :) 08:45:57 hi 08:46:24 I'm research 08:46:34 binh_, hello 08:46:37 Im same lab with phuoc 08:46:38 binh_, welcome to Tacker team. Could you please introduce yourself 08:46:43 Nice to meet you guys 08:47:12 I'm currently a research of DCN lab at Soongsil university 08:47:13 binh_ is my colleague 08:47:21 he have an idea about service graph https://docs.openstack.org/networking-sfc/latest/contributor/ietf_sfc_encapsulation.html 08:47:23 binh_, nice. 08:47:37 I hope you guys can help him to finish that feature :) 08:48:02 yeah, thank you all :D 08:48:21 my full name is Nguyen Hiep Binh 08:48:28 you can call me binh 08:49:13 I intent to implement branching and joining SFC path 08:49:47 base on networking-sfc ietf encapsulation as Phuoc mention above 08:50:04 binh_, phuoc will it go in Tacker side or networking-sfc? 08:50:42 It's will go on Tacker side and call networking-sfc 08:50:49 api 08:50:58 binh_, i see 08:51:15 We need define some template to call that APIs 08:52:27 binh_, Have you drafted any doc etc? 08:54:11 I will upload the spec on next week or next next week 08:54:21 binh_, cool 08:55:43 binh_, good to see you in Team, and welcome once again. 08:56:27 moving on 08:56:33 i will inform you guys when it finish 08:56:37 ok thank you 08:56:53 #topic Open Discussion 08:57:22 I have a patch to update SFC encapsulation https://review.openstack.org/#/c/620680 08:57:36 need some reviews on that patch, thanks :) 08:58:42 phuoc, Ok, I will review it 08:59:02 thank you 08:59:34 I am thinking to land CSAR package BP in Stein 08:59:40 #link https://review.openstack.org/#/c/582930/ 09:00:16 I seems owner is not available now a days 09:00:37 So hopefully, I will start working on that byt next week 09:00:48 that's great 09:00:55 dkushwaha, great 09:01:41 Thats all from my side 09:01:46 Do we have something more to discuss? 09:02:42 thanks 09:02:49 nothing from me 09:02:58 ok, Thanks all. 09:03:10 Closing this meeting for now 09:03:17 #endmeeting