16:01:57 <sridhar_ram> #startmeeting tacker
16:01:58 <openstack> Meeting started Tue Sep  6 16:01:57 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:59 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:02:01 <openstack> The meeting name has been set to 'tacker'
16:02:09 <sridhar_ram> #topic Roll Call
16:02:18 <tbh> o/
16:02:19 <manikanta_tadi> o/
16:02:20 <dkushwaha> o/
16:02:22 <vishwanathj> o/
16:02:27 <neel> o/
16:02:34 <mike_m> o/
16:02:40 <janki> o/
16:02:41 <sripriya> o/
16:02:43 <tung_doan> o/
16:03:06 <sridhar_ram> howdy all !!
16:03:11 <KanagarajM> o/
16:03:29 <sridhar_ram> #chair sripriya tbh KanagarajM
16:03:30 <openstack> Current chairs: KanagarajM sridhar_ram sripriya tbh
16:03:45 <sridhar_ram> #topic Announcements
16:04:29 <sridhar_ram> We are heading towards Newton RC1 target ..
16:04:31 <sridhar_ram> #link https://releases.openstack.org/newton/schedule.html
16:04:39 <diga> Hi
16:04:48 <sridhar_ram> just two more weeks left to wrap up Newton
16:05:04 <sridhar_ram> nothing else to announce from my side
16:05:20 <sripriya> sridhar_ram: when exactly is the server freeze, any specific date?
16:05:57 <sripriya> sridhar_ram: meant tacker main
16:06:27 <sridhar_ram> sripriya: as agreed earlier, that would be Sept 15th
16:06:43 <sripriya> sridhar_ram: thanks
16:07:06 <sridhar_ram> #topic Newton Release Status
16:07:39 <bobh> sridhar_ram: sorry late
16:08:22 <sridhar_ram> sripriya: again, on the deadline.. the reasoning is, once all server patchsets land by Sept 16th we will have one week of buffer time to take care of any critical bugs
16:08:26 <sridhar_ram> bobh: np
16:08:43 <sridhar_ram> btw, s3wong won't be able to make it to this call today
16:09:11 <sridhar_ram> as always, we shd expect few last minute issues / tidy ups to take care
16:09:21 <sripriya> sridhar_ram: ack
16:09:26 <sridhar_ram> any question related to the deadline ?
16:10:00 <sridhar_ram> now, let's go around the outstanding features..
16:10:22 <sridhar_ram> tung_doan: team: can you give an update on alarm monitoring ?
16:10:27 <tung_doan> sridhar_ram: it is almost done.. Now, just need some minor updates.. if possible, scaling action could be fired in my spec...
16:10:54 <tung_doan> #link: https://review.openstack.org/#/c/365435/
16:11:29 <sridhar_ram> tung_doan: thats great.. i know many community members are pitching in..
16:11:36 <dkushwaha> sridhar_ram, tung_doan I am trying to test the patch with respawn, but getting some issue.
16:11:54 <tung_doan> sridhar_ram: thanks all :)
16:12:21 <sridhar_ram> dkushwaha: can you elaborate ?
16:12:22 <tung_doan> dkushwaha: shoot please
16:12:45 <dkushwaha> sridhar_ram, tung_doan it looks respawn not done, even cpu utilization goes upto limit
16:13:11 <dkushwaha> sridhar_ram, tung_doan i am looking into that
16:13:52 <sridhar_ram> tung_doan: one suggestion in this area, is to starting using audit-event logs introduced recently by KanagarajM and vishwanathj
16:13:53 <tung_doan> other metrics you set the same, dkushwaha?
16:14:21 <dkushwaha> tung_doan, yea
16:14:30 <sridhar_ram> tung_doan: it will serve both as an enhancement and help debugging such situations..
16:14:35 <tung_doan> sridhar_ram: recognized it.. thanks sridhar
16:14:54 <sridhar_ram> KanagarajM: vishwanathj: please guide tung_doan to add that capability
16:15:00 <vishwanathj> sure
16:15:53 <sridhar_ram> tung_doan: given you are going for an all-in-one patchset .. https://review.openstack.org/#/c/365435/
16:15:54 <tung_doan> dkushwaha: i thivk the problem from ceilometer side
16:16:14 <sridhar_ram> tung_doan: .. you also need to include unit and func tests as well
16:16:22 <tung_doan> dkushwaha: please try with curl -X POST first to know what happens
16:17:02 <dkushwaha> tung_doan, ok, i will try try with same also
16:17:05 <tung_doan> sridhar_ram: understand.. thanks
16:17:38 <sridhar_ram> tung_doan: great.. i see this feature is coming together, it is going to cut close.. but i'm hopeful this will make it..
16:17:47 <janki> sridhar_ram, tung_doan: also shouldn't there be a single abstract_drvier file for all monitor drivers?
16:18:19 <sridhar_ram> tacker-cores: can couple of you sign up to review this ?
16:18:50 <tung_doan> janki: we think we already discussed that we should have an abstract driver for them.. could oyu elaborate it?
16:18:51 <sridhar_ram> bobh: given your previous monitoring creds, would you be able give this a scan ?
16:19:24 <bobh> sridhar_ram: I can take a look
16:19:33 <sridhar_ram> bobh: thanks!
16:19:36 <janki> tung_doan, contents of this https://review.openstack.org/#/c/365435/6/tacker/vnfm/monitor_drivers/alarm_abstract_driver.py should be merged with https://github.com/openstack/tacker/blob/master/tacker/vnfm/monitor_drivers/abstract_driver.py
16:19:39 <tung_doan> janki: it is the same with ping, httpping
16:20:20 <janki> tung_doan, yes, I have noticed that. Are all these intentinally kept separate or they will be merged in future/
16:20:28 <janki> sridhar_ram, your view on this ^^
16:20:52 * sridhar_ram is looking up
16:21:56 <sridhar_ram> janki: my initial thought is it should be merged..
16:22:20 <janki> sridhar_ram, +1, for all infra, mgmt and other drivers
16:22:47 <tung_doan> janki: i think we should sepaparat.. in the future, maybe we had a lot of function for drivers
16:23:00 <sridhar_ram> janki: .. only thing we need to be careful is collateral damage to existing  non-alarm monitoring like ping, http-ping, custom monitor drivers
16:23:06 <tung_doan> janki: *sepaparat --> separate
16:23:41 <tung_doan> sridhar_ram: that's correct
16:23:51 <sridhar_ram> let's take this specific item to the gerrit..
16:24:11 <sridhar_ram> janki: good catch, btw!!
16:24:17 <tung_doan> sridhar_ram: I realize that when implementing...
16:24:19 <janki> sridhar_ram, thanks :)
16:24:25 <sridhar_ram> anything else of concern on alarm-mon ?
16:25:27 <sridhar_ram> I'm super glad to see this community coming together as a team to help on this feature! you folks are awesome!
16:25:32 <sridhar_ram> moving onto VNFC
16:25:34 <tung_doan> ok.. thank all guys for looking :) please continue reviewing it
16:25:59 <sridhar_ram> #link https://review.openstack.org/339798
16:26:38 <sridhar_ram> Given where we are in the release window.. i propose we move this feature to Ocata
16:27:26 <sridhar_ram> This is a critical feature and there are still many review comments to be captured, agreed up and .. then to be implemented
16:27:42 <sridhar_ram> we just don't have enough runway to land this
16:27:57 <sridhar_ram> Let's make this (and NSD) as one of the initial features in Ocata
16:28:05 <sridhar_ram> Thoughts ?
16:29:07 <sridhar_ram> tbh: what do you think ?
16:30:00 <tbh> sridhar_ram, Yup, agree, instead of comprimising on features it provide, let's have a detailed discussion and implement completely in Ocata
16:30:15 <sripriya> sridhar_ram: given that we are stilll implementing/reviewing existing rfes/bugs, good to move them to next cycle but we can continue to implement/review the features and patches
16:30:45 <sridhar_ram> tbh: sripriya: thanks.. and i agree
16:31:00 <manikanta_tadi> sridhar_ram:  tbh : I do agree with you
16:32:08 <sridhar_ram> tbh: again, just so that we don't loose focus, we can continue the current scope penciled in .. to use Heat SD as the initial VNFC mechanism..
16:32:37 <sridhar_ram> I'll move the bp to Ocata
16:32:44 <sridhar_ram> moving on..
16:32:48 <sridhar_ram> VNFFG
16:33:11 <sridhar_ram> trozet: s3wong: provided offline status..
16:33:34 <sridhar_ram> most pieces should come together by end of this week..
16:33:55 <sridhar_ram> diga: did you had chance to try the patchsets in your testbed ?
16:34:10 <sridhar_ram> anyone else tried vnffg ?
16:34:26 <diga> sridhar_ram: I am contineously pinging to trozet about it but never got reply from his side
16:35:02 <sridhar_ram> diga: I think he was busy w/ OPNFV commitments last few days.. he shd be available this week
16:35:15 <diga> my setup is ready but need to discuss with him for testing
16:35:15 <sridhar_ram> diga: did anything fail explicitly in your trials ?
16:35:55 <sridhar_ram> diga: fair enough, you probably need an initial cheat sheet of CLIs to fire at this feature ?
16:36:11 <diga> sridhar_ram: yes
16:36:42 <sridhar_ram> diga: alright.. will ping trozet for this
16:36:57 <diga> I am waiting for trozet to provide me details so that I can understand the feature & test it appropriately
16:37:05 <sridhar_ram> i know gongysh was also planning to try this feature out.. more eyes are better :)
16:37:17 <diga> hmm
16:37:21 <sridhar_ram> diga: sounds good..
16:37:23 <janki> sridhar_ram, diga I believe it should start with creating a vnffgd and then a vnffg based on it
16:37:50 <diga> okay
16:37:52 <trozet> hi diga
16:38:00 <diga> trozet: Hi
16:38:30 <diga> trozet: lets discuss on this feature after the meeting
16:38:35 <trozet> diga: kk
16:39:28 <sridhar_ram> diga: trozet: thanks!
16:39:32 <sridhar_ram> moving on..
16:39:54 <sridhar_ram> #topic Newton Priority Issues
16:39:56 <diga> sridhar_ram: wc!
16:40:19 <sridhar_ram> beyond major features.. please flag any issues that needs to be fixed for newton
16:40:28 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-newton-release-priority
16:40:37 <sridhar_ram> ^^^ etherpad is still valid..
16:41:04 <sridhar_ram> before picking any Ocata features, please help out on this for next two weeks...
16:42:06 <sridhar_ram> I also realized we need reviewers for tacker-horizon
16:42:08 <sridhar_ram> #link https://review.openstack.org/#/q/project:openstack/tacker-horizon+status:open
16:42:22 <sridhar_ram> please review them as well
16:43:03 <sridhar_ram> Specifically https://review.openstack.org/349755 and https://review.openstack.org/347779
16:43:17 <sridhar_ram> moving on
16:43:24 <sridhar_ram> #topic Ocata Grooming
16:43:35 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-ocata-grooming
16:44:11 <sridhar_ram> Heads up on Ocata duration..
16:44:37 <diga> sridhar_ram: when we can start the dev for ocata ?
16:45:00 <sridhar_ram> Ocata is going to be shorter dev cycle than Newton.. it is not the usual 6months window
16:45:31 <sridhar_ram> The guidance from TC is to plan our work to be less than we used to
16:45:55 <diga> okay
16:45:57 <sridhar_ram> diga: we can start by 3rd week of Sept..
16:46:06 <diga> okay
16:46:27 <sridhar_ram> diga: in fact we can start to review / merge patchsets immediately after stable/newton branch is pulled
16:46:45 <diga> sridhar_ram: okay
16:47:29 <sridhar_ram> Let's continue to start writing blueprints and informally gather ideas in the etherpad above .. so that have enough discussion ahead of the design summit
16:47:59 <sridhar_ram> It will be great to use the design summit to make "final" implementation decisions and go into low-level design
16:47:59 <diga> I will push my spec by tomorrow, due to Ganesh Festival I couldn't do that, but its ready now
16:48:15 <sridhar_ram> diga: is that for API framework ?
16:48:19 <diga> yes
16:48:38 <sridhar_ram> diga: sounds good..
16:48:56 <diga> sridhar_ram: :)
16:49:01 <mike_m> hi, with regard to the EM module, https://blueprints.launchpad.net/tacker/+spec/em-module, I'm not sure if caoyue is writing that?
16:49:30 <diga> sridhar_ram: how many talks are selected from tacker project to summit
16:49:41 <sridhar_ram> diga: btw, for api framework, other projects have use a separate branch to develop the feature and then merge back to the master.. this is something we should consider doing to avoid affecting other features in flight
16:50:24 <diga> sridhar_ram: yep +1
16:50:28 <sridhar_ram> mike_m: i haven't seen a detailed tacker-specs write up beyond that BP request
16:50:51 <mike_m> Just wondering where we go with that, that is something I can help with, but not sure if someone else is picking that up.
16:51:50 <sridhar_ram> mike_m: let's check with caoyue and go from there..
16:52:17 <mike_m> ok.
16:52:27 <sridhar_ram> mike_m: can you briefly describe your "need" here ?
16:52:47 <sridhar_ram> mike_m: that BP write-up is bit too broad IMO and it needs to be narrowed down
16:53:14 <mike_m> sure.  I'd like to see a EM interface on the VNFM so that a EM could interact with the VNFM.
16:53:59 <mike_m> looking at the ETSI specifically, things like life cycle management for specific VNF's, configuration, notification of VNF/VFNS as they become instantiated, etc.
16:55:11 <sridhar_ram> mike_m: okay .. we can put this as an agenda for our upcoming meeting and drill down a bit
16:55:22 <mike_m> ok thanks!
16:55:38 <sridhar_ram> moving on..
16:55:51 <sridhar_ram> #topic Open Discussion
16:56:20 <sridhar_ram> diga: officially, there is a VNF FFG talk that got accepted for the summit
16:56:45 <diga> sridhar_ram: Gr8!
16:56:47 <sridhar_ram> I believe there are few other talks like the one on OPNFV Domino that is going to touch on Tacker
16:56:59 <sridhar_ram> Folks - anything else ?
16:57:03 <diga> okay
16:57:34 <sridhar_ram> alright .. that's a wrap!
16:57:42 <sridhar_ram> thanks everyone!
16:57:43 <janki> sridhar_ram, there is a bug to move to keystone3 in functional tests. Cann't find its url right now
16:57:57 <janki> sridhar_ram, that needs to go in newton too IMO
16:58:20 <sridhar_ram> janki: sure, let's flag that into our etherpad..
16:58:34 <janki> sridhar_ram, will do, thanks
16:58:40 <sridhar_ram> we can catchup in #tacker as needed
16:58:48 <sridhar_ram> bye folks
16:58:51 <sridhar_ram> #endmeeting