08:02:07 #startmeeting tacker 08:02:08 Meeting started Tue Jun 26 08:02:07 2018 UTC and is due to finish in 60 minutes. The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:11 The meeting name has been set to 'tacker' 08:02:27 #topic roll call 08:02:52 o/ 08:03:00 dkushwaha, hi 08:03:09 hi 08:03:57 hi 08:05:25 ok 08:05:37 it seems other guys are busy. 08:05:43 #topic bp 08:05:54 phuoc, any thing to talk? 08:06:18 gongysh, I havee some bug with devstack 08:06:29 but I think it can be fixed in this week 08:06:41 Hi, everyone 08:06:46 AndreyS, hi 08:06:52 o/ 08:07:10 AndreyS, hi 08:07:34 we would like to discuss BP https://blueprints.launchpad.net/tacker/+spec/tosca-csar-mgmt-driver 08:07:54 AndreyS, can you introduce yourself first? 08:08:10 Andrey Sviridov 08:08:16 AndreyS, nice to see you :) 08:08:48 AndreyS, what is your company? 08:08:58 Hi all, I work with AndreyS on that blueprint and have some questions 08:09:18 We are from Netcracker/DTAG 08:09:21 My company is Netcracker 08:09:39 AndreyS, ahrechny, hi 08:09:43 ahrechny, hi, welcome 08:10:03 welcome to Tacker :) 08:10:06 AndreyS, ok do you have any idea for that spec? 08:10:20 We want to add ability to support csar packages only for VNFM 08:10:41 Hi all, also working with AndreyS and ahrechny 08:10:49 akozhevnikov, hi 08:10:54 big welcome 08:11:10 And want to discuss some architecture points 08:11:17 ahrechny, ok 08:11:19 go on 08:11:35 o/ 08:11:35 First of all - rest api 08:11:53 now it supports only text descriptors 08:12:10 but we need to upload files 08:12:48 ahrechny, yes 08:13:04 so we have some ways for it - send serialized text or add new api for files uploading 08:13:30 I agree with ahrecny that ability to onboard CSAR VNF packages (not simple yaml, but archive) is very important 08:13:37 is it possible to change current API? 08:14:15 hello 08:14:16 ahrechny you can have a draft design in a spec file 08:14:21 caobin, helo 08:14:24 welcome 08:14:35 caobin, could you please introduce yourself first? 08:14:55 My colleague 08:15:06 unfortunately we don't have draft yet 08:15:13 caobin, welcome. 08:15:27 thanks 08:15:45 ahrechny, to save csar files on tacker server side, we can use ceph. 08:16:32 ahrechny, please have draft design, and then we can have a talk at the next meeting. 08:17:34 I think you guys want to upload csar file to Tacker server 08:18:15 then Tacker server will create something, such as images, files 08:18:17 but one important question about API - may I change current method for creating VNF or I should create new one? 08:18:24 and then create VNFD ? 08:19:05 ahrechny, I think csar is a way to create a vnfd, nsd, or vnffgd 08:19:11 we want to create VNFD from csar, not from plain yaml file 08:19:33 *not only 08:19:37 ahrechny, IMO we should extend current method 08:20:00 ahrechny, IMO, it can be done with existing api too, needs to check that 08:20:03 But it means that I should change content type 08:21:04 for example to multipart/form-data instead of application/json 08:22:13 csar should be a self explained archive. it will read it is a vnfd, vnfgd or nsd something 08:23:23 yes, but we want to start for VNFM 08:23:44 than it can be extended for NFVO 08:23:56 ahrechny, first you need to have an idea what is the csar. maybe to refer to some standards or other mano systems. 08:24:13 and then we can see how the workflow is. 08:24:15 I have some examples 08:24:44 This will also require changes in the taker-client, now there is only support for yaml when creating VNFD 08:25:05 archive for VNF descriptor, which contains yaml file, meta data, imports, definitions of types, artifacts & etc 08:25:46 AndreyS, I think you guys need a draft design, and we can have a talk. 08:26:00 who knows Dinesh Bhor ? 08:26:33 gongysh, yea, I know 08:26:34 gongysh, yes 08:26:49 is he online? 08:27:10 no 08:27:24 he just updated a patch 08:27:31 https://review.openstack.org/#/c/570845/ 08:27:32 patch 570845 - tacker - Add placement policies support 08:28:22 he also did not reply to the comment 08:28:32 gongysh, do you want him to attend this weekly meeting? 08:28:37 sure 08:29:18 ok, I will talk to him to attend next meeting 08:29:34 joxyuki, thanks 08:29:53 I want to merge the policy spec early 08:30:08 since we are close to rocky cycle. 08:30:12 oh, I understood 08:30:35 I talk to him to join tacker channel 08:31:14 YanXingAn, hi 08:31:25 hi 08:31:36 how is the barbican problem? 08:32:13 joxyuki, if you have time, please have a test that patch too. 08:32:22 it is almost done. 08:32:33 there is no big issue with that patch. 08:32:51 https://review.openstack.org/#/c/570845/ ? 08:32:52 patch 570845 - tacker - Add placement policies support 08:33:02 gongysh: still coding 08:33:03 yes 08:33:26 YanXingAn, don't you want a bp for it? 08:33:30 ok, what is the big problme? 08:33:33 a spec? 08:34:21 YanXingAn, spec is not required of course. 08:36:03 #topic open discussion 08:36:16 dkushwaha, do you have some thing to talk? 08:36:32 gongysh, nguyenhai, I am reusing this patch, https://review.openstack.org/#/c/486924 08:36:33 patch 486924 - tacker - Implement VNF monitoring using Mistral 08:36:55 nguyenhai, But seems vim authentication related issue. 08:37:18 yes, we have problem with vim authentication 08:37:27 dkushwaha, this is why YanXingAn is doing barbican stuff. 08:37:33 Do you have any idea about that, as i missed it 08:37:50 gongysh, oh i see 08:38:11 YanXingAn will design a service account which can access all vim credentials. 08:38:39 gongysh, is this specific to conductor ? 08:38:47 yes 08:39:06 only conductor needs that. 08:39:13 yup 08:39:51 YanXingAn, do you have some draft for that? 08:39:54 #topic berlin summit 08:40:08 berlin summit is calling for presentation. 08:40:43 at vancouver, we have sfc, multi-vim talks. 08:40:44 dkushwaha: will have a draft before next meeting 08:41:05 YanXingAn, great, thanks 08:42:02 any tacker oriented presentations are welcome. 08:42:55 seems we have no other stuff to talk. 08:43:29 ahrechny, look forward to you csar draft design next meeting. thanks 08:43:49 #endmeeting