08:01:21 <dkushwaha> #startmeeting tacker 08:01:22 <openstack> Meeting started Tue Apr 2 08:01:21 2019 UTC and is due to finish in 60 minutes. The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:25 <openstack> The meeting name has been set to 'tacker' 08:01:36 <dkushwaha> #topic Roll Call 08:01:49 <dkushwaha> who is here for Tacker weekly meeting? 08:04:29 <hyunsikyang> hi 08:05:18 <dkushwaha> hello hyunsikyang 08:07:19 <dkushwaha> ok lets start.. 08:07:45 <dkushwaha> #topic Fenix plugin support 08:08:14 <dkushwaha> #link https://review.openstack.org/#/c/643242 08:08:24 <dkushwaha> hyunsikyang, have some queries on BPs 08:08:57 <hyunsikyang> Yes please. 08:09:24 <hyunsikyang> Can I explain it first? 08:09:36 <dkushwaha> hyunsikyang, is there any separate template for maintenance ?? 08:09:49 <hyunsikyang> ah. yes, 08:09:49 <dkushwaha> hyunsikyang, yes, go ahead 08:10:09 <hyunsikyang> until now, we just added maintenance property in the template. 08:10:53 <hyunsikyang> When user use this property, that VNF register AODH to get the event from fenix. 08:11:07 <dkushwaha> i could not see it in sample template in spec 08:11:32 <hyunsikyang> In the blueprint, you can see the template. 08:11:54 <dkushwaha> hyunsikyang, oh, my mistake, just checked, yes it was there 08:11:56 <hyunsikyang> It looks similar like general things. 08:12:01 <hyunsikyang> Yes. 08:13:11 <dkushwaha> ten my comment on line#124 is also invalid 08:13:17 <hyunsikyang> So, that VNF can receive the alaram from Fenix. So, when fenix want to start maintenace, tacker can help for Maintenance. 08:13:44 <hyunsikyang> ok:) 08:15:09 <hyunsikyang> Now, we draw only one procedure, but we will seperate it, soon. 08:15:28 <dkushwaha> i see 08:15:52 <hyunsikyang> And VNF Stop is just one of the example. so Changing the path thing is more acceptable. 08:16:04 <hyunsikyang> I will change some part:) 08:18:17 <dkushwaha> my comment on line#128 is to explain activities on tacker side in details 08:19:26 <dkushwaha> i mean, for example if we are talking about VNF stop(or anything else), what action will tacker perform in that, and how it will resume once maintenance done 08:20:10 <hyunsikyang> Actually, Fenix have a workflow like flow i draw in the bp. 08:21:01 <hyunsikyang> So, sometimes, it requires action to perform the maintenace such as down scaling.. 08:21:11 <hyunsikyang> or up scaling or migrate. 08:21:15 <hyunsikyang> migration. 08:21:57 <hyunsikyang> Now tacker can't support all of actions. 08:22:38 <hyunsikyang> But, we can make a procedure and messing structure first. 08:22:43 <hyunsikyang> And 08:23:04 <hyunsikyang> when we think about the role of tacker for maintenance, 08:23:10 <dkushwaha> yes, Regarding Fenix workflow, that one is complete flow from fenix to tacker, it will be good if we can also explain more about tacker side 08:24:07 <dkushwaha> hyunsikyang, agree, we can move step by step for other actions 08:24:31 <hyunsikyang> Ah ok. 08:24:41 <hyunsikyang> After update, please check it again. 08:25:11 <dkushwaha> yea sure 08:25:15 <dkushwaha> one more thing 08:25:34 <dkushwaha> we also needs to mention about the VNF status. 08:26:15 <hyunsikyang> Ah you mean that when VNF have a problem, is it going to tell to Fenix? 08:26:15 <dkushwaha> Ex. once VNF goes in maintenance state, we needs to update that 08:26:23 <hyunsikyang> AH, 08:26:28 <hyunsikyang> Ok. 08:27:54 <dkushwaha> btw, very nice and clear workflow diagram 08:27:57 <hyunsikyang> Yes In the fenix, when fenix upgrade node, it changed the status of node as a disable. 08:28:31 <hyunsikyang> like this, we also think the way to present current status. 08:29:45 <dkushwaha> hyunsikyang, IMO, once fenix change status of node, same should be reflected in VNF status as well 08:30:47 <hyunsikyang> Yes, I will think it again. because, now i am thinking to seperate procedure like infra maintenance and VNF maintenance/ 08:31:04 <dkushwaha> ok 08:31:46 <dkushwaha> hyunsikyang, I have further queries as of now 08:32:01 <hyunsikyang> yes 08:32:23 <dkushwaha> typo: no further queries as of now 08:32:33 <hyunsikyang> ah 08:32:36 <hyunsikyang> ok:) 08:33:17 <dkushwaha> hyunsikyang, do you have something else to discuss? 08:33:26 <dkushwaha> otherwise we can close this meeting 08:33:43 <hyunsikyang> no 08:33:50 <dkushwaha> ok 08:34:30 <dkushwaha> Thanks hyunsik for joining this meeting :) 08:34:50 <dkushwaha> closing it now 08:35:04 <dkushwaha> #endmeeting