16:01:22 <sridhar_ram> #startmeeting tacker
16:01:23 <openstack> Meeting started Tue Sep 27 16:01:22 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:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:26 <openstack> The meeting name has been set to 'tacker'
16:01:33 <sridhar_ram> #topic Roll Call
16:01:38 <tbh> o/
16:01:39 <vishwanathj> o/
16:01:39 <dkushwaha> o/
16:01:43 <janki> o/
16:01:47 <mike_m> o/
16:01:47 <n-harada> o/
16:01:51 <abinaya__> o/
16:01:56 <tung_doan> o/
16:02:09 <sripriya> o/
16:02:18 <sridhar_ram> howdy all !!
16:02:24 <sridhar_ram> #chair sripriya tbh
16:02:24 <s3wong> o/
16:02:25 <openstack> Current chairs: sridhar_ram sripriya tbh
16:02:31 <sridhar_ram> #chair sripriya tbh s3wong
16:02:32 <openstack> Current chairs: s3wong sridhar_ram sripriya tbh
16:02:49 <sridhar_ram> #topic Agenda
16:03:03 <sridhar_ram> #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Sep_27th.2C_2016
16:03:14 <neel> o/
16:03:16 <sridhar_ram> #topic Annoucements
16:03:37 <sridhar_ram> Tacker Newton got released, hurray !!!
16:03:50 <vishwanathj> awesome
16:03:55 <sridhar_ram> #link http://lists.openstack.org/pipermail/openstack-announce/2016-September/001665.html
16:03:55 <janki> yyeyeyeyy
16:03:57 <dkushwaha> congrats all :)
16:04:17 <sripriya> congrats team. great effort!!
16:04:23 <sridhar_ram> Tacker horizon vvvv
16:04:25 <sridhar_ram> #link http://lists.openstack.org/pipermail/openstack-announce/2016-September/001666.html
16:04:50 <abinaya__> hi all, i work for Sprint, I am new to tacker. I have just setup the dev env
16:04:50 <sridhar_ram> you just need to see all those commits that went in .. that just last 4 weeks
16:05:07 <sridhar_ram> abinaya__: welcome to the team!
16:05:22 <abinaya__> i would like to work on a bug
16:05:33 <sridhar_ram> IMHO, this is one of the best release of Tacker!! Tons of things went in
16:06:06 <s3wong> sridhar_ram: +1
16:06:07 <sridhar_ram> Agree w/ Sripriya, this was a great team effort!
16:06:14 <mike_m> great work, I'm very impressed with its feature set!
16:06:27 <sridhar_ram> mike_m: thanks!
16:06:40 <sridhar_ram> abinaya__: that's a good way to start..
16:06:53 <sridhar_ram> anything else to announce?
16:07:10 <sridhar_ram> nothing else from my side..
16:07:27 <sridhar_ram> #topic Newton Restrospective
16:07:55 <sridhar_ram> It make sense to pause few mins and assess what worked well in newton and what didn't ..
16:08:04 <sridhar_ram> Thoughts?
16:08:17 <sridhar_ram> We all should be as frank as we can be..
16:09:21 <sripriya> sridhar_ram: functional and unit tests need to go hand in hand with a feature or rfe patch
16:09:53 <vishwanathj> Breaking up into multiple patchsets worked well for me for the events audit plugin even though there were initial hiccups
16:10:06 <dkushwaha> vishwanathj, +1
16:10:18 <tung_doan> sripriya: +1
16:10:52 <sridhar_ram> one from my side on what-worked-well... when a feature was struggling a bit, different members naturally jumped in to help out .. a "sub-team" got organically formed, they owned the feature and most importantly delivered!!
16:11:23 <vishwanathj> +1
16:11:24 <sridhar_ram> ^^ this happened repeated .. VNFFG, alarm-mon, audit-log, etc
16:11:24 <sripriya> sridhar_ram: +1
16:11:58 <tbh> sridhar_ram, +1
16:12:30 <sridhar_ram> To me this is a cue for new members joining Tacker, they still can make a big by joining a "sub-team" or propose something "big" and ask for a sub-team to be formed ..
16:13:04 <sridhar_ram> we can try formalizing this in Ocata..
16:13:32 <sridhar_ram> sripriya: yes, unit and func needs to go hand in hand.. we still need improvements in this area
16:13:51 <sridhar_ram> now, what else could be improved ?
16:15:35 <sridhar_ram> I've an etherpad here for this..
16:15:38 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-newton-retrospective
16:15:48 <vishwanathj> it might be a good idea for reviewers and coders to come up with acceptance criteria for a patch early on if possible... as soon a developer thinks he or she is done, you get a comment that was not thought through during spec time .... expect this to be improved over time though
16:15:52 <sridhar_ram> if you think of anything, please capture in there..
16:17:38 <sridhar_ram> vishwanathj: agree, the more thorough spec review can help us avoid such expectation gap between the submitters and reviewers
16:18:22 <sridhar_ram> that reminds be of one more thing... the submitters of big features need to actively solicit / recruit reviewers ...
16:18:31 <sripriya> sridhar_ram: i guess ownership on the spec reviews can help so that the reviewer and developer can work through the spec to get it to its possible best
16:18:55 <sridhar_ram> reviewer bandwidth is important along the same lines as a submitters bandwidth.. reviewing is hard work !!
16:20:02 <vishwanathj> I understand that not everything can be thought through at spec review .. but a running list of acceptance criteria initiated by developer during implementation and modified as per dialogue between submitter/reviewer could help get a sight on when patch can be closed
16:20:05 <sridhar_ram> sripriya: +1, perhaps that answers by above suggestion... to "recruit" one of the spec reviewers to be your code reviewer.. this will also alleviate the problem that vishwanathj brought up
16:20:20 <sripriya> sridhar_ram: agree
16:20:52 <sridhar_ram> vishwanathj: we do have "work items" listed in the spec and we tracked that in the BP launchpad.. that was very useful.
16:21:13 <vishwanathj> +1 on the work items, that was very helpful
16:21:26 <sridhar_ram> Again, I'll capture these points in the etherpad after this meeting.. feel free to add anything else u can think of
16:21:46 <sridhar_ram> we will try to incorporate in the upcoming cycle..
16:21:49 <sridhar_ram> moving on
16:22:02 <vishwanathj> that helped me a lot to track my tasks, a good practice to continue
16:22:04 <dkushwaha> sridhar_ram,  instead of combining all in one patch, we should break down the large patches
16:22:19 <sridhar_ram> dkushwaha: agree..
16:23:09 <vishwanathj> the core team did a great job reviewing patchsets and also guiding team members when stuck....hopefully, you folks got enough sleep in this cycle
16:23:18 <janki> All in one patch is easy to test - like for me testing alarm-mon was easier
16:23:34 <sridhar_ram> dkushwaha: .. however there were some angst what "sized" patchset is ideal...
16:24:17 <sridhar_ram> dkushwaha: too many too small patchset are pain to test, ack janki's point ..
16:24:28 <sridhar_ram> we need to find a good balance
16:24:37 <dkushwaha> sridhar_ram, janki IMO patches should be logically complete at smallest level instead of their size
16:24:43 <diga> I prefer splitting larger patch into small will be good
16:25:15 <vishwanathj> dksushwaha +1 ... it took a while to understand that concept for me, but was glad that I did it that way in the end
16:25:18 <sridhar_ram> vishwanathj: thanks.. credits goes to all the rock start core-team members..
16:25:51 <sridhar_ram> alright folks, lots of good input.. will capture them into the etherpad..
16:25:56 <sridhar_ram> time to move to the next topic
16:26:22 <sridhar_ram> #topic Barcelona Summit Planning
16:26:41 <sridhar_ram> #link https://etherpad.openstack.org/p/tacker-ocata-summit
16:27:11 <sridhar_ram> Let's pencil in some candidate topics for the design summit...
16:27:50 <sridhar_ram> Fishbowl session Wed 3:05 - 3:45pm .. is a bigger room, and probably would be widely attended
16:28:18 <sridhar_ram> It will be good to talk about our roadmap / vision beyond things in flight..
16:28:53 <sridhar_ram> we can take up the next working session for near term features .. either already started or just about to ..
16:28:59 <sridhar_ram> any suggestions ? ideas ?
16:29:03 <janki> sridhar_ram, I would like to talk on containarised VNF. I am working on getting the demo ready
16:29:14 * sridhar_ram specifically looking for folks who are going to be in barcelona
16:29:25 <mike_m> sridhar_ram: multi-vim, specifically vcloud API?
16:29:35 <sripriya> mike_m: +1
16:29:41 <mike_m> sridhar_ram: I will be there.
16:29:56 <sridhar_ram> mike_m: great...
16:30:37 <sridhar_ram> mike_m: sripriya: on that I've reached out to some one from VMware working on Nova .. we should plan to invite nova-vmware members to our fishbowl session
16:31:20 <sripriya> sridhar_ram: yeah, that would be great idea
16:32:19 <mike_m> sridhar_ram: would also like to discuss the "EM" API.  I'm still trying to figure out what that should look like, but would like an open discussion on that.
16:32:50 <sridhar_ram> janki: for containerized VNF .. it might be possible just w/ TOSCA VDU changes and enhancing  openstack VIM driver to interface w/ Magnum / Zun through Heat
16:33:03 <sridhar_ram> mike_m: sure, lets pencil that in for the working session
16:33:22 <janki> sridhar_ram, I am thinking the same - having magnum instead of heat
16:37:02 <vishwanathj> thats a long silence
16:37:12 <sridhar_ram> i just updated the etherpad
16:37:12 <sridhar_ram> tbh: dkushwaha: do you folks want to talk more on VNFC & NSD in the summit ? perhaps what can be done beyond the initial VNFC and NSD support ?
16:37:12 <sridhar_ram> mike_m: I'd suggest you to put together a short google doc / slides to present for EM API... it will help to trigger the conversation
16:37:12 <sridhar_ram> mike_m: can you take that up?
16:37:26 <mike_m> sridhar_ram: yes I can
16:38:12 <sridhar_ram> janki: can't we invoke magnum using heat resources ?
16:38:56 <janki> sridhar_ram, I think we can. But am thinking to bypass heat if possible.
16:39:36 * sridhar_ram looks freenode irc server is flapping
16:40:20 <sridhar_ram> can you folks "hear" me ?
16:40:34 <janki> sridhar_ram, I can
16:40:35 <mike_m> sridhar_ram: I can, I was booted as well for a short time
16:40:37 <vishwanathj> I am seeing the same
16:44:31 <sridhar_ram_alt> We have about 15mins left.. let's see if irc channel settles up
16:46:41 <sridhar_ram> irc testing .. 1. 2. 3...
16:47:54 <sridhar_ram> janki: why ?
16:49:32 <sridhar_ram> Folks .. i'm ending this early due to IRC issues
16:49:38 <sridhar_ram> #endmeeting