16:00:44 <sridhar_ram> #startmeeting tacker
16:00:44 <openstack> Meeting started Tue Jul 19 16:00:44 2016 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:48 <openstack> The meeting name has been set to 'tacker'
16:00:53 <sridhar_ram> #topic Roll Call
16:00:59 <KanagarajM> hi
16:01:08 <anshukch> o/
16:01:10 <s3wong> o/
16:01:11 <janki> o/
16:01:14 <dkushwaha> o/
16:01:14 <neel> o/
16:01:25 <tung_doan> hi all
16:01:32 <vishwanathj> o/
16:01:34 <sripriya> o/
16:01:50 <sridhar_ram> howdy folks! let's start...
16:02:14 <sridhar_ram> #topic Agenda
16:02:19 <sridhar_ram> #link https://wiki.openstack.org/wiki/Meetings/Tacker
16:02:42 <sridhar_ram> packed agenda..
16:02:51 <sridhar_ram> #topic Annoucements
16:02:57 <KanagarajM> sridhar_ram, shall we discuss the current items first, I saw today's meeting agenda, its big :)
16:03:40 <sridhar_ram> KanagarajM: yes, planning to take the items in flight first..
16:04:08 <sridhar_ram> back to annoucements..
16:04:26 <sridhar_ram> Since we are meeting next week for midcycle meetup..
16:04:54 <sridhar_ram> #info No weekly meeting next week, on July 29th
16:05:41 <sridhar_ram> Newton Feature Freeze is coming close - Aug 29th, just 7-weeks away
16:05:50 <sridhar_ram> #link http://releases.openstack.org/newton/schedule.html
16:06:22 <sridhar_ram> all features and RFEs need to merge by that date
16:06:41 <sridhar_ram> only bug fixes and integrations issues can be addressed after that..
16:07:18 <sridhar_ram> Please get your patchsets for specs and RFEs to post as soon as possible...
16:07:37 <sridhar_ram> we have a busy review cycle upon us..
16:07:50 <sridhar_ram> #topic Project Mascot
16:08:04 <sridhar_ram> #link http://lists.openstack.org/pipermail/openstack-dev/2016-July/099507.html
16:08:23 <sridhar_ram> We need to pick an animal mascot for Tacker project..
16:08:38 <sridhar_ram> here is the etherpad to collect inputs..
16:08:47 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-mascot
16:09:06 <janki> an animal is a must?
16:09:52 <dkushwaha> janki, +1
16:09:54 <sridhar_ram> janki: it can be anything from the natural world
16:09:59 <KanagarajM> i like this idea :)
16:10:03 <sridhar_ram> animal is the popular choice
16:10:21 <sridhar_ram> there is an interesting option in the etherpad to use a Squid..
16:10:26 <KanagarajM> i think only heat had some sort of logo earlier. good to have for all
16:10:28 <janki> I had an idea (shared on ehterpad) but it doesnot have animal/natural thing
16:10:50 <janki> Ya, squid is nice one
16:11:06 <sridhar_ram> few of us created this earlier for Tacker (with some professional help),
16:11:08 <sridhar_ram> #link https://wiki.openstack.org/w/images/2/21/Squid_rev7.jpg
16:11:14 <sridhar_ram> how does this look ?
16:11:32 <janki> sridhar_ram: +1, its really cool
16:12:00 <s3wong> sridhar_ram: nice!
16:12:01 <sridhar_ram> again, openstack logo team will rework this to make it something that is identifies it as openstack project..
16:12:33 <manikanta_tadi> any significance for containers in one of the tentecle
16:12:33 <sridhar_ram> janki: s3wong: thanks!
16:12:36 <sridhar_ram> manikanta_tadi: Tacker eventually orchestrating VNFC in Containers
16:13:07 <sridhar_ram> hopefully we get there sooner with integration with projects like Magnum & Zun/Higgins
16:13:24 <sridhar_ram> please leave ur comments in etherpad..
16:13:33 <sridhar_ram> moving on..
16:13:53 <sridhar_ram> #topic VNF Scaling
16:14:05 <sridhar_ram> #link https://review.openstack.org/#/q/status:open+branch:master+topic:tacker-scaling
16:14:18 <sridhar_ram> KanagarajM: over to you
16:14:32 <KanagarajM> this current patch set have the end-end functioanlity
16:15:15 <KanagarajM> sridhar_ram, would be great if we could get cores time on these patches
16:15:32 <sridhar_ram> KanagarajM: sure
16:15:43 <KanagarajM> hopefully this week or early next week we could target to merge them
16:16:23 <sridhar_ram> cores: please help to land this by early next week
16:16:39 <KanagarajM> sridhar_ram, thanks.
16:16:51 <KanagarajM> sridhar_ram, i will land the doc patches sooner
16:17:00 <KanagarajM> for the scaling
16:17:12 <sridhar_ram> KanagarajM: I'm pulling the patchset to try.. now, how do you typically trigger the scaling to test ?
16:17:36 <KanagarajM> please pull both cli and server patches
16:17:51 <KanagarajM> and it should work simply by using the tacke vnf-scale cli
16:18:05 <sridhar_ram> KanagarajM: okay...
16:18:21 <KanagarajM> there are two samples, and one with unit testing would be simple to test
16:18:41 <sridhar_ram> sounds good
16:18:42 <sridhar_ram> any questions on vnf-scaling ?
16:18:49 <sridhar_ram> *any other
16:19:03 <KanagarajM> i will and the patch for functional test once client patch get merged
16:19:20 <KanagarajM> land*
16:19:31 <sridhar_ram> KanagarajM: we might need to make a client release w/ scaling changes ?
16:19:54 <KanagarajM> sridhar_ram, yes. i feel so
16:20:27 <sridhar_ram> VNFFG will bring in slew of client changes.. not sure if we can club both into one release
16:21:01 <sridhar_ram> i'll take up the client release part
16:21:05 <janki> VNFFG is targeted for Newton release?
16:21:16 <sridhar_ram> janki: yes!
16:21:27 <KanagarajM> sridhar_ram, sure. but i feel it might delay the functional test. but i feel its ok
16:21:41 <janki> sridhar_ram: cool
16:21:55 <sridhar_ram> let's briefly discuss other things in the pipeline..
16:22:10 <sridhar_ram> apologies for impromptu change..
16:22:17 <KanagarajM> sridhar_ram, i will try to keep the patch ready, so that once the client rlease is done, we could take immediate action on functioanl test patch
16:22:34 <sridhar_ram> KanagarajM: perfect!
16:22:57 <sridhar_ram> KanagarajM: thanks a lot ! couldn't be happier how vnf-scaling has come together
16:23:18 <sridhar_ram> #topic VNFFG-AlarmMon-Status
16:23:59 <sridhar_ram> tung_doan: do you've an idea when you might be able to post the alarm-monitoring patchsets for review ?
16:24:02 <dkushwaha> sridhar_ram, I think we missed NSD
16:24:21 <sridhar_ram> dkushwaha: will got to it in few mins
16:24:48 <dkushwaha> sridhar_ram, ok
16:25:20 <tung_doan> sridhar: I already devided some parts for impemtation
16:25:38 <tung_doan> sridhar: hope to finish soon
16:26:26 <sridhar_ram> tung_doan: okay, again please keep in mind all the code-review and devref need to finish by Aug 29th.. otherwise this feature need to move to O-release..
16:26:49 <sridhar_ram> s3wong: along the same lines, how is your networking-sfc driver coming along ?
16:26:57 <tung_doan> sridhar: i know this time is very important.. thanks for reminding
16:27:09 <sridhar_ram> tung_doan: sure
16:28:05 <sridhar_ram> s3wong: u there ?
16:28:20 <sridhar_ram> s3wong: did you catch the question above ?
16:29:00 * sridhar_ram will sync up w/ s3wong offline
16:29:04 <sridhar_ram> #topic NSD
16:29:26 <sridhar_ram> #link  https://review.openstack.org/304667
16:29:34 <sridhar_ram> dkushwaha: take over, please
16:29:42 <dkushwaha> sridhar_ram, Last week, I have updated the spec.
16:30:03 <dkushwaha> sridhar_ram, i have some questions
16:30:20 <sridhar_ram> dkushwaha: shoot
16:30:33 <dkushwaha> sridhar_ram, and want o know team's opinion
16:30:52 <dkushwaha> sridhar_ram, As in spec, I am mentioning  VirtualLink and  ConnectionPoint tables separately, is it make sense? or we need to keep it attributes part of NetworkServiceTemplate ?
16:31:33 <sridhar_ram> dkushwaha: IMO, db tables for VLs and CPs doesn't make sense
16:31:51 <KanagarajM> sridhar_ram, +1 I too felt the same
16:32:02 <janki> sridhar_ram: I agree
16:32:06 <sridhar_ram> dkushwaha: handling it as attributes similar to how we are doing it for VNFD should be sufficient
16:32:39 <sridhar_ram> dkushwaha: now, what is the advantage of having this in DB ?
16:33:15 <sridhar_ram> there is a reason you are proposing this and I'd like to understand that
16:33:36 <dkushwaha> sridhar_ram, Actually I am thinking to invoke create_vnfd inside nsd onboard operation. and handle vld and cp separately
16:34:28 <dkushwaha> sridhar_ram, thats why i thought to keep it in different tables
16:34:42 <sridhar_ram> dkushwaha: these VLD and CPd are part of NSD yaml template itself, correct ?
16:34:57 <dkushwaha> sridhar_ram, yes
16:35:24 <sridhar_ram> dkushwaha: do we allow any API / CLI operations directly on VLD or CP ?
16:35:42 * sridhar_ram thinks most likely not
16:36:20 <dkushwaha> sridhar_ram, we can allow for some operations
16:36:32 <dkushwaha> sridhar_ram, like add vld
16:36:56 <sridhar_ram> dkushwaha:  yes, but that is probably for a future work, and it shd be out of scope for NSD work
16:37:39 <dkushwaha> sridhar_ram, agree. make sense to me
16:38:07 <sripriya> sridhar_ram: given that VNFFD and VNFD is in place and now NSD is coming in, are we thinking about a separate catalog framework for these templates?
16:38:26 <sridhar_ram> btw, on a related but a different idea.. i'd like you to explore using Mistral workflow for your NSD work
16:39:09 <sridhar_ram> Mistral support for Tacker got recently merged..
16:39:19 <sridhar_ram> #link https://review.openstack.org/#/c/331827/
16:39:36 <sridhar_ram> and there are some same workflow to create VNFD  / VNF is posted recently..
16:39:38 <KanagarajM> sripriya, now glare is ready ! so it would be an choice to consider :)
16:39:45 <sridhar_ram> #link https://review.openstack.org/#/c/341164/
16:40:10 <KanagarajM> sripriya, http://lists.openstack.org/pipermail/openstack-dev/2016-July/099553.html
16:40:50 <sridhar_ram> sripriya: good point in separating call the catalog out of VNFM
16:40:59 <sridhar_ram> s/call/all/
16:41:23 <sripriya> KanagarajM: thanks for the pointer, they mention tacker as well in the mail
16:41:30 <KanagarajM> sripriya, yes
16:42:05 <sridhar_ram> we shd engage more w/ glare team in Barcelona, we missed sync w/ them in Austin...
16:42:55 <sridhar_ram> Folks: can nfv-catalog split out be taken up as part of NSD work ?
16:43:18 <sridhar_ram> there shouldn't be any end user facing VNFD impact ?
16:43:22 <sridhar_ram> sripriya: ?
16:43:42 <sripriya> sridhar_ram: i guess no
16:44:15 <sridhar_ram> dkushwaha: please assess the impact of nfv-catalog split out as part of your NSD work
16:44:32 <dkushwaha> sridhar_ram, yes sure
16:44:47 <sridhar_ram> dkushwaha: all: please think about using mistral for NSD
16:45:04 <sridhar_ram> we can discuss that in the midcycle
16:45:14 <dkushwaha> sridhar_ram, I will llik into that
16:45:23 <dkushwaha> sridhar_ram, is invoking  create_vnfd inside onboard nsd is correct way?
16:46:24 <sridhar_ram> dkushwaha: in the initial phase, NSD can just reference VNFDs already onborded into the catalog
16:47:32 <sridhar_ram> dkushwaha: in a follow-on, we can consider supporting in-ling VNFDs within NSD. Then we need create_vnfd() with some properties to make it special (not visible in VNFD list, only available for that specific NSD)
16:47:44 <sridhar_ram> *in-line / embedded
16:48:38 <sridhar_ram> dkushwaha: let's continue the discussion in the midcycle.. you shd lead this topic, obviously
16:48:52 <dkushwaha> sridhar_ram, yes sure
16:48:55 <sridhar_ram> moving on..
16:48:59 <sridhar_ram> #topic VNFC
16:49:14 <manikanta_tadi> Hi All, Myself and bharath tried to understand how heat software component can be fit for VNFC support.
16:49:36 <sridhar_ram> #link  https://review.openstack.org/#/c/339798
16:49:46 <manikanta_tadi> One question on our mind is , How vnf upgrade can be supported on fly if we opt for heat software component
16:50:38 <sridhar_ram> KanagarajM: have some thought here ?
16:51:04 <manikanta_tadi> sridhar_ram : we are exploring various drivers apart from ssh driver what we had in the spec
16:51:33 <sridhar_ram> basically, we need to know if heat can do "uninstall" of s/w in VMs
16:52:24 <sridhar_ram> manikanta_tadi: can you & tbh plan to present some slides on this topic for next week's midcycle...
16:52:30 <manikanta_tadi> KanagarajM, pls provide your inputs from heat perspective
16:52:39 <sridhar_ram> please go over all the options in that prezo
16:52:49 <manikanta_tadi> sridhar_ram : Sure!
16:53:20 <sridhar_ram> I'll also lookup a bit more on Heat SoftwareComponent
16:53:20 <manikanta_tadi> sridhar_ram : We will come up with that...
16:53:48 <sridhar_ram> openstack-service --> VMs spawned is a hot topic these days in the ML
16:54:04 <s3wong> sridhar_ram: sorry, was out of desk a while ago
16:54:11 <sridhar_ram> there is a concern different projects are resorting to different methods
16:54:18 <sridhar_ram> something to keep in mind
16:54:36 <sridhar_ram> s3wong: np
16:54:37 <s3wong> sridhar_ram: currently aiming to have the patches out before the mid cycle next week; sorry for the delay
16:55:05 <sridhar_ram> s3wong: sure, release dates are approaching faster than i thought it would :)
16:55:15 <sridhar_ram> moving on
16:55:29 <sridhar_ram> #topic Midcycle Meetup Topics
16:55:56 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-newton-midcycle
16:56:11 <sridhar_ram> last call for topics to disucss in the midcycle..
16:56:30 <sridhar_ram> i'd like to invite the team to actively participate and be.. vocal !
16:56:46 <janki> I have a question
16:56:46 <sridhar_ram> I'd rather talk less and .. have the community speak :)
16:56:50 <sridhar_ram> janki: sure
16:57:07 <janki> Are we planning to have an ansible playbook for tacker as well?
16:57:11 * sridhar_ram 3mins left
16:57:32 <sridhar_ram> janki: yes, someone from Brocade is working on it..
16:57:41 <janki> ohk, cool
16:57:47 <sridhar_ram> janki: need to check how far it has progressed..
16:58:05 <janki> sridhar_ram: sure, let me know if help needed
16:58:13 <sridhar_ram> janki: sure
16:58:17 <janki> sridhar_ram: I also have an idea/feature development
16:58:25 <janki> not sure how valuable it is
16:58:37 <sridhar_ram> anything else on midcycle ?
16:59:15 <sridhar_ram> janki: write a spec / blueprint
16:59:26 <janki> sridhar_ram: sure, will do
16:59:28 <sridhar_ram> janki: don't worry about the usefulness..
16:59:34 <sridhar_ram> janki: you never know :)
16:59:34 <janki> :)
16:59:38 <sridhar_ram> alright times up
16:59:46 <sridhar_ram> thanks for joining everyone
16:59:49 <janki> bye
16:59:51 <sridhar_ram> talk to all next week
16:59:59 <sridhar_ram> #endmeeting