16:04:35 #startmeeting tacker 16:04:37 Meeting started Thu Aug 27 16:04:35 2015 UTC and is due to finish in 60 minutes. The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:04:40 The meeting name has been set to 'tacker' 16:04:49 sripriya: you there ? 16:04:58 sridhar_ram: o/ 16:05:07 #chair sripriya 16:05:08 Current chairs: sridhar_ram sripriya 16:05:33 Agenda #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Aug_27.2C_2015 16:05:37 hello all 16:05:48 Rajkumar: hi 16:05:48 hi 16:05:51 hello 16:05:52 #topic Announcements 16:05:54 hi 16:06:17 hi 16:06:26 hi everyone! 16:06:49 Tacker liberty midcycle meeting minutes available here - #link https://wiki.openstack.org/wiki/Meetings/Tacker/Liberty-Midcycle-Meeting-Minutes 16:07:20 Slides used for the discussion is available in slideshare here - #link http://www.slideshare.net/SridharRamaswamy/openstack-tacker-liberty-midcycle 16:07:55 sridhar_ram: thank you for leading the tacker liberty midcycle 16:08:00 That's was a very productive meetup. Lots of nice discussions. Thanks for those who took the effort to participate! 16:08:11 sripriya: thanks! 16:09:05 anything else to announce ? deadline / milestones ? 16:09:48 sridhar_ram: how about the liberty release deadline for tacker? 16:09:57 I frankly we had the Tacker M summit talk to announce.. too bad it didn't got selected :( 16:11:06 sripriya: good question .. but we are bit lagging to get the previous checkpoints like stable/kilo pull, switch to master to knock off before we can take up Liberty release 16:11:56 I'm hoping these blockers will be cleared soon.. hopefully in next few days 16:12:01 sridhar_ram: understood, we can decide a date once the switch to master happens 16:12:08 hello 16:12:14 s3wong: hi 16:12:24 sripriya: exactly 16:12:43 prashantD_: you there ? 16:12:43 sridhar_ram: reg: sessions it will only make us evolve tacker even better for M release and beyond :-) 16:12:53 sridhar_ram : I am here 16:13:35 sripriya: I sure bet Tacker will have lot more stuff to showcase in N Summit! 16:13:56 sridhar_ram: :-) 16:14:09 Note, me and Bob H are invited for an NFV Panel .. will make sure to plug Tacker as much as possible ;-) 16:14:30 lets move on 16:14:35 #topic AutoScaling Update 16:14:54 prashantD_: take over for you are updates! 16:15:09 I have the spec out for review. 16:15:25 sridhar_ram : I saw your comments, I will address them, esp the template portion 16:15:33 * sridhar_ram needs to disable pidgin spell-checker... argh 16:15:50 on the meter side we are just going to stick with cpu_util for now? 16:16:27 prashantD_: given we have scoped to keep this effort simple I'm fine w/ sticking w/ cpu_util 16:16:54 unless anyone else have other options on which triggers should kick off auto-scaling actions 16:17:05 *opinions 16:17:18 good initial start 16:17:38 okay I will update the spec accordingly. 16:18:00 once it is done I will start the implementation portion. 16:18:14 prashantD_: sounds good 16:18:28 team - please review this spec - #link https://review.openstack.org/#/c/214297/ 16:18:39 day job is keeping me really busy so I couldn't attend midcycle, sorry 16:19:32 I also invite the VNF vendors interested in Tacker to see if they can leverage this feature... 16:19:46 .. we need some beta testing for this feature w/ real VNFs 16:20:01 prashantD_: no worries 16:20:11 prashantD_: anything else ? 16:20:36 sridhar_ram : no I am done for now...pls review the spec 16:20:44 will do 16:20:57 #topic Tacker-SFC Integration 16:21:21 trozet: you there ? 16:22:09 lets continue ... 16:22:48 as evident in the midcycle discussion .. we are super excited about Tim's SFC PoC efforts in Tacker 16:22:51 #link https://github.com/trozet/tacker/commits/SFC 16:23:27 I'd like to get the team's thoughts on how we can bring in into Tacker repo... 16:24:08 particular on the code structure that should host SFC api and backend implemenation 16:24:10 would not the regular process of a spec and then code patch set not gping to work 16:25:45 vishwanathj: that would be the ultimate goal.. however I want to get the initial strawman among our minds clear so that we can guide that effort - spec / code, etc 16:26:12 some background .. 16:26:44 Tacker code, for good or bad, is structured along the lines of neutron extension .. 16:26:52 sridhar_ram: are we still thinking about providing a sfc extension? 16:27:15 sripriya: I'm getting there ;-) 16:27:48 we are moving the current code into an extension named as "vnfm" - essentially the VNF Manager portion of Tacker 16:28:25 we also envision we will have an "nfvo" extension sometime in the near future with NFV Orchestration APIs / backends 16:28:56 now for SFC ... we probably need something similar.. 16:29:22 oh I see 16:29:32 Sridhar - Please share us any link or materials related to SFC. 16:30:13 Rajkumar_: unfortunately, there is no one spec to point to... 16:30:38 hopefully the spec / docs we write for Tacker+SFC could serve that purpose... 16:30:56 ETSI-VNFFG is probably a good high-level model to refer.. 16:31:00 Thanks Sridhar.. 16:31:22 Sure.. 16:31:32 IMO SFC is need in two places in ETSI MANO .. 16:31:54 (1) for VNFFG which is at the NFVO / NSD handler 16:32:24 (2) for intra-VNF (VDU wiring) - 16:32:39 I'm not too sure about (2) ... if there is a real use-case 16:33:52 question to the team - should SFC exists as an NVFO API or should it be a common API (using a tacker sfc extension) ? 16:34:41 Rajkumar_: I remember your team was interested in NSD aspects...any thoughts here ? 16:35:23 Sridhar - it would be in NFVO API 16:35:43 as it connects with VNF's. 16:36:25 Rajkumar_: okay... 16:38:03 lets think a bit more on Tacker-SFC integration .. it should map to ETSI-MANO's needs for SFC 16:38:36 we will have more SFC related activities in our next iteration ! 16:39:30 anything else on SFC ? questions, comments ? 16:40:07 #topic Liberty Release Plans 16:40:45 one comment on service chainning 16:40:51 #undo 16:40:52 Removing item from minutes: 16:41:07 xhuang: sure 16:41:10 if the scope of the service chaining also includes networking 16:41:27 then.. I am not sure if the NFVO is the right place 16:42:18 do we have any documentation on the scope? 16:42:39 sorry I missed the discussion on this topic last Friday 16:43:19 xhuang: agree, as pointed out earlier in this meeting, we need a document that spells out the scope of this effort 16:44:23 sridhar_ram: i can create a spec for SFC for the initial outline 16:44:24 any volunteers to take up this SFC work ? 16:44:45 sripriya: cool, thanks .. we need someone to help Tim as well 16:45:01 sridhar_ram: i can coordinate with him 16:45:17 sripriya: sounds good! thanks 16:45:37 xhuang: lets use that spec to discuss scope and our initial efforts 16:45:45 sure.. thanks 16:46:06 now to the liberty release plans... 16:46:31 s3wong: we briefly discussed earlier in the meeting on this .. 16:47:18 hi 16:47:23 sorry i am late 16:47:37 SFC I can take 16:47:46 we should wait, may a week, until we clear the backlog - Bob's fix, stable/kilo, switch to master .. etc 16:47:53 s3wong: what do you think ? 16:48:13 vks: hi, sure .. you and Sripriya can collaborate.. 16:48:51 sripriya, so can we talk offline 16:49:02 vks: sure 16:49:09 ok 16:49:45 s3wong: you there ? 16:50:56 ... we sure will be cutting close for a liberty release... 16:51:41 we should try to rush the things in flight like MANO api, TOSCA parameterization and perhaps auto-scaling, that would be decent Liberty release 16:52:25 lets open the floor for general questions.. 16:52:36 sridhar_ram: ack 16:52:46 #topic Open Discussion / Bugs / Misc 16:52:48 can we put some timelines 16:52:49 ? 16:53:13 also can we list down all the doc, spec we have 16:53:16 ??? 16:53:20 if any 16:53:22 ??? 16:53:31 sridhar_ram: sorry, was away from my desk for a while 16:53:34 it will help moving things faster 16:53:41 vks: the specs are in the tacker-specs repo 16:53:58 #link https://github.com/stackforge/tacker-specs 16:54:04 sridhar_ram, thnx 16:54:07 s3wong: np 16:54:29 can we work on deciding timelines in next meeting 16:54:31 ??? 16:54:37 internal to the team 16:54:47 If I need to propose a date - Sept 18 - 3 weeks from now ! 16:54:50 what you all think ? 16:55:15 so what all in that? 16:55:19 sridhar_ram: this is for Liberty release? 16:55:20 i mean the scope 16:55:25 ??? 16:55:45 sridhar_ram: 3 weeks from now sounds good... I should have time over the next week or so to clear review backlog 16:55:47 s3wong: yes...too ambitious? ;-) 16:56:14 vks: the ones I mentioned earlier .. the things that are in flight 16:56:23 sridhar_ram, MANO api 16:56:27 sridhar_ram: I know MANO API would be in, how about monitoring and auto-scaling? 16:56:27 MANO api, TOSCA parameterization and perhaps auto-scaling 16:56:32 tosca parametrization 16:56:38 autoscaling 16:57:15 MANO api & TOSCA param is zero risk 16:57:39 Bob H need to comment on health-monitoring and Prashant for auto-scaling 16:58:07 what about SFC?? 16:58:13 But the fact that we have a date .. might make this happen ;) 16:58:33 vks: don't believe that would be remotely possible to make Liberty at this point 16:58:37 vks: SFC is early in the cycle..that can't be Liberty release 16:58:49 but we can have some PoC my Tokyo summit 16:58:55 that code will be in the master 16:59:00 not in the stable/liberty 16:59:06 * sridhar_ram 1 min mark.. 16:59:09 sridhar_ram: yeah, would be nice to have a release by M-Summit 16:59:13 we got wrap up guys 16:59:33 we are out of time .. 16:59:40 hey let me know if i can close some bugs 16:59:42 Thanks, guys! 16:59:51 if someone want to continue please jump to #tacker channel... 17:00:10 thanks everyone! 17:00:11 vks: sure, thanks for your help! 17:00:23 #endmeeting