04:30:58 #startmeeting tacker 04:30:59 Meeting started Wed Jan 3 04:30:58 2018 UTC and is due to finish in 60 minutes. The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:31:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:31:02 The meeting name has been set to 'tacker' 04:33:53 YanXingAn, hi 04:34:26 hi 04:34:58 phuoc, hi 04:35:09 hi Mr.gongysh 04:35:20 #topic bp 04:35:24 lets start 04:35:32 with container vnf 04:35:41 phuoc, http://paste.openstack.org/show/636966/ 04:36:03 hi gongysh 04:36:18 please look at my c-vnf descriptor 04:36:55 I will update it 04:37:20 this way will keep the vnfd almost the same 04:37:28 original, I intend to support multiple containers in 1 VDU 04:37:45 but I will update with 1 container in 1 VDU 04:38:05 and provide 1 example about deploy c-VNF with real case 04:39:30 how do you mapping vnf resources to k8s elements? 04:39:51 vnf is a k8s service, vdu is a pod? 04:40:20 VNF is made of many VDU 04:40:38 phuoc, right. 04:41:23 and how do you map to k8s elements? 04:41:37 each of VDU, I define it by a Service, Deployment (deployment have many pods) and a Horizon Pod Auto-scaler (optional) 04:44:14 vnf can have many vdus. k8s service can have many pods, k8s pod can have many containers. 04:44:17 And VDU is exposed by Service (it looks like load balancer to Pods) 04:46:53 phuoc, do you think your spec is clear about the mapping? 04:47:10 if that is, I can read it again. 04:47:41 gongysh, I will update my spec to make it clear 04:48:00 phuoc, please make sure the mapping is clear and then do coding, otherwise, you probably waste your time. 04:48:01 because there are many ways to define c-VNF in Kubernetes 04:48:06 my spec is one of them 04:48:37 gongysh, thanks 04:48:52 phuoc, in openshift, the pod can have many containers. 04:49:37 gongysh, it is the same to kubernetes, that is why I try to define VNFC 04:50:07 1 VDU have many VNFCs (VNFC is defined by a container) 04:51:57 phuoc: A VNFC have only one VM? 04:52:54 phuoc, https://review.openstack.org/#/c/529116/2/samples/tosca-templates/vnfd/tosca-vnfd-containerized.yaml, why use a new configurable_properties instead of vnfc? 04:54:52 YanXingAn, I tried to map VNFC definition to k8s object 04:55:11 I think it is better to map VNFC to a container in Pod 04:55:37 gongsyh, I followed to this document from TOSCA http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd04/tosca-nfv-v1.0-csd04.html#_Toc482896065 04:56:27 it is only one document, they talk about VNFC 04:58:39 it seems there is no independent node type to define the vnfc 05:00:06 how about changing https://review.openstack.org/#/c/529116/2/samples/tosca-templates/vnfd/tosca-vnfd-containerized.yaml 05:00:19 configurable_properties: 05:00:19 redis-master: 05:00:20 properties: 05:00:20 num_cpus: 0.5 05:00:22 mem_size: 512 MB 05:00:22 into: 05:00:32 nfvc: 05:02:20 phuoc , http://paste.openstack.org/show/637006/ 05:03:16 actually, there are no definition in TOSCA about VNFC 05:03:31 so, I think about your advice http://paste.openstack.org/show/636966 05:04:04 we will have simple case, 1 VDU is defined a container 05:04:09 636966 is one vdu has one container. 05:04:27 ok, lets do it first. 05:04:44 Kompose project, they also define one container for one pod 05:05:13 so, we can't need VNFC 05:06:30 I mean since your current patch is trying to do multiple containers, we can do it 05:07:05 637006 is justing change 'configurable_properties' into 'vnfcs'. 05:07:52 637006 is just changing 'configurable_properties' into 'vnfcs'. 05:08:03 gongysh, I got it 05:08:05 thank you 05:08:54 phuoc, so what is your next direction? 05:09:30 after this spec? 05:09:44 In this spec. 05:10:02 http://paste.openstack.org/show/636966 or http://paste.openstack.org/show/637006/ ? 05:10:34 maybe I will go with multiple containers 05:10:55 but I have some issues with volumes in Kubernetes 05:11:19 phuoc, ok with multiple containers. 05:11:43 https://wiki.onap.org/pages/viewpage.action?pageId=16007890 05:12:09 this is one proposal project in ONAP to do the same thing 05:12:27 I will update Tacker if they have better solution 05:13:04 phuoc, you can let volume problem to next phase. 05:13:08 phuoc thanks 05:13:22 #info https://wiki.onap.org/pages/viewpage.action?pageId=16007890 05:13:32 next bp 05:13:35 longkb_, hi 05:13:51 hi 05:14:00 xuan0802, hi 05:14:08 I have seen the bp and its codes. 05:14:11 Hi, I and xuan0802 are working on bp: https://blueprints.launchpad.net/tacker/+spec/policy-based-vnf-cluster 05:14:20 have you guys tested that? 05:14:45 maybe you can record a demo before next meeting? 05:14:46 all functions as spec have been tested 05:15:04 however, we will add functional testcases soon 05:15:16 xuan0802, that's fine. thanks 05:15:38 xuan0802, if you can record a demo, it will be cool. 05:15:39 From your point of view, do we need to update our spec? 05:16:34 Ok, I will make a video demo and show to you in tacker channel 05:16:35 I cannot get a picture of how it will work if I just review the spec. 05:17:30 longkb_, thanks 05:18:02 #topic open discussion 05:18:23 do you guys have stuff to talk? 05:18:41 How about multi-site scenario in Tacker? 05:18:59 Do we have a plan to integrate with Tricircle? 05:19:12 longkb_, I see your spec relates to this. 05:20:31 longkb_, to work with tricircle, we need add some properties to our VLD elements. 05:21:17 yep, I see 05:21:19 of course, if we don't create VL, I mean use the existed neutron networks, it should work with tricircle now. 05:23:21 longkb_, if you think there are some we need to do in order to work with tricircle, you are welcome to file a bp and impement it. 05:23:31 impement -> implement 05:24:30 Thanks gongysh, I will think about it. Hence, I will make a bp that relates to Tricircle :) 05:24:45 anything else? 05:25:09 ok. lets end this meeting 05:25:15 #endmeeting