16:01:26 <sridhar_ram> #startmeeting tacker
16:01:26 <openstack> Meeting started Tue Aug 30 16:01:26 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:01:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:29 <openstack> The meeting name has been set to 'tacker'
16:01:38 <sridhar_ram> #topic Roll Call
16:01:45 <janki> o/
16:01:46 <manikanta_tadi> o/
16:01:46 <diga> o/
16:01:48 <dkushwaha> o/
16:01:51 <vishwanathj> o/
16:01:51 <tung_doan> o/
16:01:56 <neel> o/
16:02:03 <bobh> o/
16:02:04 <sripriya> o/
16:02:05 <mike_m> o/
16:02:22 <sridhar_ram> hello everyone!
16:02:28 <sridhar_ram> let's start..
16:02:36 <sridhar_ram> #chair bobh sripriya
16:02:37 <openstack> Current chairs: bobh sridhar_ram sripriya
16:02:51 <sridhar_ram> #topic Announcements
16:02:56 <sridhar_ram> Few quick ones..
16:03:21 <s3wong> hello
16:03:52 <sridhar_ram> #link https://releases.openstack.org/newton/schedule.html
16:04:04 <sridhar_ram> We are in newton-3 / feature freeze territory !
16:04:34 <sridhar_ram> We need to be extra careful what we land until Sept 15th (newton release deadline)
16:04:52 <sridhar_ram> next..
16:05:05 <sridhar_ram> Please join me to welcome Yong Sheng to the core team!
16:05:12 <sridhar_ram> #link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102356.html
16:05:35 <sridhar_ram> Our geo diversity is quite amazing!
16:05:49 <sridhar_ram> next..
16:05:53 <sridhar_ram> Final Tacker client for Newton 0.7.0 is released
16:05:58 <sridhar_ram> #link http://lists.openstack.org/pipermail/openstack-announce/2016-August/001496.html
16:06:28 <sridhar_ram> thanks for all those who pushed patchsets and reviews to make this happen..!
16:06:50 <sridhar_ram> any other quick general shout outs ?
16:07:13 <sridhar_ram> moving on..
16:07:28 <sridhar_ram> #topic Newton Release Status
16:07:59 <sridhar_ram> let's go around and to see any sticking issues in the features expected to land in next couple of weeks...
16:08:14 <sridhar_ram> tung_doan: how is your alarm monitoring coming along ?
16:08:24 <sridhar_ram> tung_doan: any major issues blocking you ?
16:08:41 <tung_doan> sridhar: alarm monitor is almost done. https://review.openstack.org/#/q/status:open+project:openstack/tacker+branch:master+topic:tacker-alarming
16:09:26 <tung_doan> sridhar: i will need reviews latter
16:09:31 <sridhar_ram> tung_doan: does this include ceilometer alarm driver ?
16:09:43 <tung_doan> sridhar: yes, sure
16:10:27 <sridhar_ram> tung_doan: sorry, i haven't looked closely.. which specific patchset has ceilometer related things ?
16:10:29 <tung_doan> sridhar: alarm framework is already lauched. But it still need to review
16:10:53 <tung_doan> sridhar: np. https://review.openstack.org/#/c/362975/
16:11:45 <sridhar_ram> tung_doan: i was looking for requirements.txt changes to pull in ceilometer client..
16:12:14 <sridhar_ram> tung_doan: anyways, will review...
16:12:27 <sridhar_ram> team - need your help in the review of alarm mon..
16:12:30 <tung_doan> sridhar:  thanks
16:12:56 <sridhar_ram> it is coming in late, so..
16:13:36 <sridhar_ram> can someone volunteer to work with tung_doan to go beyond code review to pull the patchset and verify the functinality .. while the patchsets are still out
16:13:54 <janki> sridhar_ram, I can help
16:13:57 <tung_doan> sridhar: thanks you guys.. I will try to modify if possible in the rest time
16:14:20 <sridhar_ram> janki: great, thanks..
16:14:42 <janki> sridhar_ram, mention not :)
16:14:57 <tung_doan> sridhar: thanks janki
16:15:02 <sridhar_ram> tung_doan: please watchout for issues reported by janki !!
16:15:22 <sridhar_ram> moving on to...vnffg
16:15:24 <tung_doan> sridhar: sure.. it is important time for me
16:15:38 <tung_doan> sridhar: janki thank :)
16:15:47 <sridhar_ram> trozet: s3wong: hi, can you give an update where we stand on this feature
16:15:49 <janki> tung_doan, welcome :)
16:16:10 <trozet> sridhar_ram: hello
16:16:36 <sridhar_ram> trozet: sorry, for the abrupt pull into the meeting  :)
16:16:51 <sridhar_ram> trozet: s3wong: trying to get a sense of what is remaining for this whole feature ..
16:16:51 <diga> sridhar_ram: it seems, we have very large patchset. it will be good if we can reduce patch size in the future
16:16:54 <trozet> sridhar_ram: the plugin/ext side is almost done.  Need to get the abstract driver and janki's patch through (if not already done).  I then need to test the plugin with the client that was merged
16:17:09 <s3wong> sridhar_ram: I am doing integration of driver with trozet's plugin
16:17:12 <trozet> diga: this was the preferred method
16:17:20 <sridhar_ram> diga: the blame is on me, to consolidate at slightly coarse grain level
16:17:27 <s3wong> sridhar_ram: found some bugs (on my side), will post new patch sometime this week
16:17:29 <sridhar_ram> *to ask them
16:17:33 <diga> trozet: okay
16:17:49 <janki> trozet, I have uploaded PS addressing the comments
16:17:59 <trozet> sridhar_ram, s3wong: can we get the abstract driver taken care of? and janki's patch?
16:18:18 <s3wong> trozet: what's to take care of? merge?
16:18:19 <sridhar_ram> trozet: yes, those two are definitely close to land
16:18:26 <janki> sridhar_ram, a separate error_response will be droppped by API layer. Also error_response column is not present in the client
16:18:50 <trozet> s3wong: for abstract driver need your review s3wong
16:18:51 <sridhar_ram> janki: understood, i was about to response.. let's skip error_reason for now
16:19:01 <sridhar_ram> *respond
16:19:12 <janki> sridhar_ram, yes. I do have an idea though. we can discuss that after meeting
16:19:32 <s3wong> sridhar_ram, trozet: I am still the author of abstract driver, should I even +2 it :-)
16:19:44 <sridhar_ram> trozet: in fact, even the plugin / db / extn side seems to have gotten enough eyeballs.. that patchset would be next (in this series)
16:19:56 <trozet> s3wong: haha i don't mean you have to +2...just feedback on what I posted
16:20:02 <trozet> s3wong: like is it ok or not
16:21:18 <sridhar_ram> trozet: beyond the plugin / ext, abstract driver, n-sfc implementation .. what is remaining to be posted ?
16:21:59 <s3wong> sridhar_ram: that should be it --- it is end to end already with these
16:22:06 <trozet> sridhar_ram: i need to do the real TOSCA validation of the VNFFGD
16:22:24 <trozet> sridhar_ram: there are a few places where i have TODO (like validating all the VNFs are on the same VIM)
16:22:26 <sridhar_ram> s3wong: trozet: yes, the TOSCA portion is critical...
16:22:45 <trozet> sridhar_ram: but not too much other than testing everything together and seeing what doesnt work
16:22:46 <sridhar_ram> trozet: do you need substitution_mapping support for your TOSCA needs ?
16:22:59 <sridhar_ram> bobh: ^^
16:23:07 <trozet> sridhar_ram: I think we decided on ignoring that for the first pass
16:23:13 <trozet> sridhar_ram: to make things less complicated
16:23:27 <bobh> trozet: probably a good idea
16:23:40 <sridhar_ram> trozet: sure, thats a fine approach for this first iteration
16:24:01 <diga> trozet: any help you need ? I hv some interest in VNFFG
16:24:02 <sridhar_ram> i believe we need that more for NSD and NSD + VNFFGD
16:24:58 <trozet> diga: I could use help testing the whole thing
16:25:04 <trozet> diga: once it's ready
16:25:05 <sridhar_ram> s3wong: any blockers for your n-sfc implementation ?
16:25:06 <diga> trozet: sure
16:25:18 <s3wong> sridhar_ram: no, other than day job :-)
16:25:29 <trozet> s3wong: heh
16:25:31 <sridhar_ram> s3wong: :)
16:26:02 <sridhar_ram> diga: similar to what janki is doing for alarm-mon, it will be great if can team up w/ these folks to give this a spin end-to-end with all the patchsets out .. that would be awesome
16:26:24 <diga> sridhar_ram: Sure. I will
16:26:35 <sridhar_ram> trozet: janki: haiwei: s3wong: sripriya: amazing tag teaming so far in executing this feature ..!
16:27:01 <janki> sridhar_ram, thanks :)
16:27:51 <sridhar_ram> BTW, a talk submission on this feature is accepted for barcelona summit..
16:27:53 <sridhar_ram> #link https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15335/orchestrating-vnf-forwarding-graphs-and-sfc-using-opendaylight-neutron-and-tacker
16:28:13 <diga> sridhar_ram: Absolutely, will like to work with trozet & s3wong for every help they need from my side reviewing, testing etc
16:28:25 <sridhar_ram> even more reason to finish this and show a kickass demo!
16:28:39 <trozet> yeah diga, if you also want to review 2k lines that would be helpful ;)
16:28:56 <sridhar_ram> diga: great, thanks!
16:28:57 <diga> trozet: :)
16:29:00 <trozet> sridhar_ram: i'll plan on picking up and pushing new changes thursday
16:29:05 <sridhar_ram> moving on..
16:29:22 <trozet> sridhar_ram: so if we can get abstract driver and vnf resources done by then, i twill reduce hte number of moving parts under me
16:29:54 <s3wong> trozet: Thursday sounds good
16:29:54 <sridhar_ram> trozet: absolutely.. we can take care of them in a day
16:30:20 <s3wong> (someone else needs to give a +2 on abstract-driver)
16:30:25 <sridhar_ram> s3wong: if you can review trozet's updates to your abstract driver .. we are good to go
16:30:33 <trozet> thanks
16:30:44 <s3wong> sridhar_ram: sure --- still not appropriate to give a +2 :-)
16:31:25 <sripriya> s3wong: will review the patch
16:31:35 <s3wong> sripriya; Thanks!
16:31:39 <sridhar_ram> s3wong: understood.. just leave a note to us in the irc channel
16:31:48 <sridhar_ram> next, ... VNFC
16:32:01 <sridhar_ram> #link https://review.openstack.org/#/c/339798/
16:32:35 <manikanta_tadi> For VNFC BP, We have pushed a WIP patch already  https://review.openstack.org/#/c/358321/
16:32:50 <manikanta_tadi> review of spec is ongoing,
16:33:24 <sridhar_ram> manikanta_tadi: we need more folks to review this...
16:33:36 <sridhar_ram> mike_m: your comments are quite helpful ..
16:33:40 <manikanta_tadi> the tasks still left are sample templates,devref, functional tests which myself and tbh are taking up
16:33:52 <sridhar_ram> bobh: did you had a chance to look at this spec ?
16:34:06 <bobh> sridhar_ram: briefly - I'll take another look
16:34:40 <manikanta_tadi> bobh, Thanks ..
16:34:43 <sridhar_ram> I'm looking for bit more consensus on where we are heading .. even if we implement just a portion of the whole thing
16:35:42 <mike_m> I have a concern with the VNF requirement of needing the heat api agent.
16:35:46 <sridhar_ram> I do realize this is a "new" feature that seems to slide in .. we can bring this in as an "experimental" feature in newton
16:35:59 <sridhar_ram> mike_m: can you elaborate pls?
16:36:30 <mike_m> i was wondering of a more agnostic approach for the VNF.  This makes the feature very OpenStack VNF specific.
16:37:01 <sridhar_ram> mike_m: couldn't agree more..
16:37:15 <bobh> sridhar_ram: mike_m me too
16:37:46 <mike_m> I see the cloud-init as the only viable approach in this short period of time.  Couldn't that satisify the initial startup requirements?
16:38:02 <sridhar_ram> mike_m: we absolutely want Tacker be a TOSCA Orchestrator engine .. for multiple VIM types (openstack, vmware, aws, etc) and for NFV and beyond (like enterprisey use-cases)
16:38:57 <sridhar_ram> mike_m: we already support cloud-init in Tacker's TOSCA in the form of user-data..
16:39:36 <bobh> sridhar_ram: but user_data could easily be mapped to a different VIM without requiring specific changes to the image
16:40:07 <mike_m> Looking at this at a different angle, do you think the config of a VNF/VNFC might be more related to the EM interface?
16:40:21 <bobh> sridhar_ram: if a VNF relies on specific Heat functionality for creation, it is pretty much tying itself to OpenStack anyway
16:40:40 <sridhar_ram> bobh: you make use of the fact cloud-init is supported in different VIMs, agree but it can't support mid-life vnfc install / uninstall
16:41:10 <bobh> sridhar_ram: agree, do we know of similar capabilities in other VIMs?
16:41:22 <mike_m> In some respects, mid-life management might be more related to em.
16:41:41 <sridhar_ram> bobh: cloud-init is supported in many VIMs - definitely vmware and aws
16:42:16 <bobh> sridhar_ram: was thinking about the heat-specific config resources - SoftwareDeployment/SoftwareCOnfig/etc
16:42:41 <sridhar_ram> bobh: back to your question on making this heat specific, that is why i want to see this spec talk more about the VNFC changes in TOSCA and plugin and *most importantly* describe an abstract interface from plugin to infra_driver..
16:43:12 <sridhar_ram> bobh: .. it is upto the infra_driver to use any available mechanism -- cloud-init, ssh, SoftwareDeployment, etc
16:43:44 <sridhar_ram> mike_m: my understanding is EM aspects comes once the VNFC s/w is in place in the target VDU..
16:43:48 <bobh> sridhar_ram: right, which I was uncomfortable with specifying the heat driver in the VNFC config
16:44:13 <sridhar_ram> mike_m: but we need to get the bits in place first and that is what we need some clarity
16:44:40 <sridhar_ram> bobh: agree, that part doesn't gel for me as well..
16:44:50 <mike_m> agree
16:46:39 <sridhar_ram> if we scope this work to describe TOSCA VNFC dom will be given to infra_driver and infra_driver will take care of honoring it (or erroring out as un-supported) would that be okay for this initial attempt?
16:47:21 <sridhar_ram> plugin and TOSCA part doesn't (and shouldn't) know about SoftwareDeployement happening underneath
16:47:31 <mike_m> that sounds like the right approach to me
16:47:47 <bobh> sridhar_ram: agree - and the TOSCA shouldn't tell the orchestrator which infra to use
16:47:56 <manikanta_tadi> sridhar_ram, agree, this sounds good to me too
16:48:02 <sridhar_ram> bobh: mike_m: fair enough..!
16:48:26 <sridhar_ram> manikanta_tadi: please incorporate these in the spec and let's see how far we can push :)
16:48:49 <manikanta_tadi> sridhar_ram: Sure, will make the changes accordingly
16:48:50 <sridhar_ram> manikanta_tadi: continue to iterate these in your WIP patchsets
16:49:04 <sridhar_ram> alright.. moving on..
16:49:19 <sridhar_ram> #topic Ocata Feature Grooming
16:49:59 <sridhar_ram> I'd like to kick start Ocata feature planning in the background as we wrap up Newton
16:50:25 <sridhar_ram> as usual there is going to be a etherpad ..
16:50:44 <sridhar_ram> .. no surprise there, but i've left it empty this time :)
16:51:00 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-ocata-grooming
16:51:40 <sridhar_ram> based on the midcycle and other recent discussions ..
16:52:18 <sridhar_ram> I'd like to propose a decomposed vim-infra driver framework as one of the top items for next cycle
16:52:37 <diga> sridhar_ram: I am writting one spec for new API framework implementation like we discussed last time, will submit it to ocata repo. I have done enough study on that
16:52:42 <mike_m> has there been more discussions regarding this one: https://blueprints.launchpad.net/tacker/+spec/em-module? Could this be added as a potential for Ocata?
16:52:58 <sridhar_ram> please capture the items you think that is important for Ocata
16:53:20 <sridhar_ram> diga: sure, that's great
16:53:31 <sridhar_ram> mike_m: yes, that be taken up as well..
16:53:42 <diga> sridhar_ram: yep
16:54:04 <sridhar_ram> it will be also nice to come up w/ a relative priority among different items
16:54:36 <sridhar_ram> capturing in the blueprint is definitely a better option
16:54:52 <sridhar_ram> we can use the etherpad to socialize the idea
16:55:05 <diga> sridhar_ram: +1
16:55:43 <sridhar_ram> we will obviously have few carry overs from newton.. like NSD
16:55:58 <mike_m> no bp yet, but vmware vim.
16:56:12 <mike_m> likely a long shot for now, but certainly can be discussed.
16:56:40 <sridhar_ram> mike_m: sure, in fact i noticed there is a oslo.vmware ..
16:56:42 <sridhar_ram> #link https://github.com/openstack/oslo.vmware
16:56:49 <manikanta_tadi> sridhar_ram, OSC support ?
16:56:50 <sridhar_ram> something we can leverage
16:56:58 <mike_m> I saw that, was wondering the same.
16:57:19 <sridhar_ram> manikanta_tadi: yes, but relative priority will be low IMO
16:57:25 <diga> mike_m: sridhar_ram : I think lets have seperate etherpad for vmware vim, we can list out all in detail there
16:57:34 <dkushwaha> sridhar_ram, so, can we start for ocata now?
16:57:45 <mike_m> ok
16:57:53 <sridhar_ram> diga: yes, vmware vim will be biggee..
16:58:21 <diga> sridhar_ram: yeah
16:58:29 <sridhar_ram> dkushwaha: yes, the spec work can start.. the patchsets can merge only after stable/newton is pulled.. roughly after Sept 15th
16:58:54 <sridhar_ram> dkushwaha: can you please update ur NSD patchset to ocata dir ?
16:59:06 <dkushwaha> sridhar_ram, yes sure
16:59:19 <sridhar_ram> alright, let's continue to groom this Ocata list over next few meetings..
16:59:23 <sridhar_ram> time's almost up
17:00:02 <sridhar_ram> use the etherpad to capture any ideas to be entertained for Ocata.. it could be features or code clean
17:00:06 <sridhar_ram> thats it
17:00:10 <sridhar_ram> bye folks
17:00:13 <sridhar_ram> #endmeeting