16:02:47 <sridhar_ram> #startmeeting tacker
16:02:47 <openstack> Meeting started Thu Aug 13 16:02:47 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:02:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:02:51 <openstack> The meeting name has been set to 'tacker'
16:03:09 <sridhar_ram> Agenda #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Aug_13.2C_2015
16:03:20 <sridhar_ram> #topic Announcement
16:03:55 <sridhar_ram> Tacker Midcycle meetup next week - Aug 20 - 21st
16:04:09 <sridhar_ram> #link https://wiki.openstack.org/wiki/Tacker/LibertyMidcycle
16:04:16 <sridhar_ram> #link https://etherpad.openstack.org/p/liberty-tacker-midcycle
16:07:48 <sripriya> sridhar_ram just messaged he lost internet connectivity. he will join back once he has connectivity again
16:07:57 <sripriya> we can continue the meeting
16:08:26 <lsp42> Will the two days have their outputs recorded or logged? I'm in the UK and can't make the 20th at Brocade HQ
16:09:35 <sripriya> lsp42: as of now, there is no arrangment for recording the meeting, but we will log the meeting minutes of both days and also the action items
16:10:16 <sripriya> lsp42: 20th is mostly hackathon and will run for half a day only
16:10:45 <sripriya> 21st be a full day which will run through the agenda mentioned in the etherpad link
16:11:49 <sripriya> lsp42: did you have any other questions about the midcycle?
16:12:55 <lsp42> srpriya: None yet. I'm a noobie :)
16:13:03 <sripriya> alright, lets move on
16:13:22 <sripriya> #topic Tacker MANO API
16:14:03 <sripriya> since i'm not the chair, openstack does not automatically set the topic
16:14:39 <sripriya> so the API spec has been in good progress, i wil paste the link here for reference
16:14:55 <sripriya> #link https://review.openstack.org/#/c/204926/
16:15:47 <sripriya> the api spec is still active for any feedback or thoughts
16:16:37 <sripriya> and will probably merge by early next week once s3wong reviews and approves (core reviewer)
16:17:11 <sripriya> the other update i had was the implementation of the api spec
16:17:29 <sripriya> #link https://review.openstack.org/#/c/211734/
16:17:59 <sripriya> the patchset contains the fix required for the introduction of the new API extension
16:18:22 <sripriya> the fix is pretty straightforward and is mostly a wrapper around servicevm extension
16:18:31 <sridhar_ram> I'm back (internet provider - GoogleStarbucks)
16:18:51 <sripriya> i will be submitting thr python-tackerclient changes and unit test by end of this week
16:19:03 <sridhar_ram> #chair sripriya
16:19:04 <openstack> Current chairs: sridhar_ram sripriya
16:19:16 <sripriya> until then the patchset has been set to WIP and is open for any comments/feedback
16:19:22 <sripriya> sridhar_ram: welcome back!
16:19:45 <sripriya> sridhar_ram: take it over :-)
16:20:09 <sridhar_ram> are you done w/ MANO API update ?
16:20:43 <sripriya> i just finsihed the update, unless anybody has any questions
16:21:37 <sripriya> sridhar_ram: the topic could not be set to API update earlier since i was not the chair
16:21:40 <sridhar_ram> lets move on then..
16:21:49 <sridhar_ram> #topic AutoScaling Update
16:22:01 <sridhar_ram> prashant ?
16:22:19 <prashant> on autoscaling I have the spec, I upload the spec for review
16:23:06 <prashant> there are two work items, as we were discussing sridhar_ram, updating TOSCA template format and translation of template to heat
16:23:43 <sridhar_ram> Yes, TOSCA currently doesn't support AutoScaling & Monitoring yet
16:24:18 <sridhar_ram> this is something we need to take an initial crack at it
16:24:27 <prashant> sridhar_ram : I haven't made any progress on TOSCA template from where we left off few days ago
16:24:50 <sridhar_ram> prashant: can you share the google doc link w/ the team here ?
16:25:28 <sridhar_ram> it is preliminary but will give others some idea of the initial thought process and provide comments
16:25:58 <prashant> sure...there you go..https://docs.google.com/document/d/14LL_ZK0oQ_MDFgT82a0aBAiKb3kOJNQJUPcZkOVXVzI/edit?usp=sharing
16:26:23 <sridhar_ram> Once we have an implementation .. we can even influence / provide some suggestion back to the TOSCA community
16:26:59 <sripriya> sridhar_ram: does that mean we will contribute to the TOSCA simple vnf standard?
16:28:08 <sridhar_ram> sripriya: not in official sense, only companies joined as "contributor" status in OASIS can contribute
16:28:47 <sripriya> sridhar_ram: ok
16:28:48 <sridhar_ram> but we have folks in TOSCA-nfv who value Tacker teams input in this area .. and I'm sure they will consider our input :)
16:29:11 <sripriya> cool
16:29:23 <lsp42> quick Q on TOSCA...how far are we from supporting standing up multiple instances like NFVO?
16:29:27 <sridhar_ram> Rajkumar_Kuppura: qq.. have your team have any experience w/ AutoScaling using other Orch framsworks ?
16:29:55 <sridhar_ram> lsp42: here is a two part answer
16:30:20 <sridhar_ram> lsp42: 1) if a VNF has multiple VDUs (multiple VMs forming a VNF) - tacker support this today
16:30:23 <Rajkumar_Kuppura> nope. Sridhar. We just used the auto scaling group for scaling.. Haven't done much on this.
16:31:23 <sridhar_ram> lsp42: 2) NFVO / NSD level orchestration is something we are still discussing w/ an extended team of TOSCA + heat-translator + Tacker
16:32:03 <lsp42> sridhar_ram: thanks
16:32:47 <sridhar_ram> Rajkumar_Kuppura: okay
16:33:09 <sridhar_ram> prashant: I'll provide some comments on both TOSCA & ETSI NFV / IFA sections
16:33:23 <prashant> sridhar_ram : sure ty
16:33:29 <sridhar_ram> based on that we can take an attempt an implemenation
16:33:43 <sridhar_ram> looking fwd for your spec in tacker-specs!
16:34:36 <sridhar_ram> next topic
16:34:47 <sridhar_ram> #topic Liberty Release plans
16:35:04 <sridhar_ram> #undo
16:35:05 <openstack> Removing item from minutes: <ircmeeting.items.Topic object at 0xa46f790>
16:35:13 <sridhar_ram> #topic Switch to Master
16:36:11 <sridhar_ram> Tacker currently works using stable/kilo components for its dependencies (like nova, neutron, etc)
16:36:26 <sridhar_ram> I now have couple of patchsets to switch Tacker to master
16:36:47 <sridhar_ram> this is important to make a Liberty Release for tacker
16:37:23 <sridhar_ram> #link - https://review.openstack.org/#/c/211403/ - this is Tacker server
16:37:39 <sridhar_ram> #link - https://review.openstack.org/#/c/211405/ - this is for Tacker client
16:37:56 <sridhar_ram> this switch over will be bit *disruptive*
16:38:30 <sridhar_ram> But as long as you follow the instruction in our wiki ... will be painless
16:38:48 <sridhar_ram> any questions on this ?
16:39:56 <sridhar_ram> the patchset itself is switch over from oslo.messaging to oslo_messaging stuff
16:40:12 <sridhar_ram> hopefully we can plan to do this switch within couple of week
16:40:14 <sridhar_ram> weeks
16:40:39 <sridhar_ram> #topic Liberty Release Planning
16:41:17 <sridhar_ram> The plan is to cut a liberty release in late Sept
16:41:26 <sridhar_ram> we will finalize the date in next week's F2F
16:41:45 <sripriya> sridhar_ram: just to add, once the master changes are pushed, a kilo branch will be cut out to provide stable/kilo suport in Tacker
16:42:37 <ssuresh> hello all
16:42:52 <sridhar_ram> sripriya: yes, thanks for the heads up. we can pull the current branch as stable/kilo before the switch to master
16:42:54 <ssuresh> this is shrinath
16:42:57 <sridhar_ram> ssuresh: hi
16:44:21 <sridhar_ram> On the release - with things in flight I'm hoping if we can following things - MANO API, Health Mon Refactoring, Switch to Master, Testing - that will be a solid release
16:44:52 <sridhar_ram> prasant's AutoScaling will be the cherry on the top if it made it ...
16:45:09 <sridhar_ram> prashant: no pressure ;-)
16:45:13 <sripriya> :-)
16:45:40 <sridhar_ram> any question on the release plan ?
16:46:08 <sridhar_ram> the date I had in mind in Sept 25th .. lets decide that next week
16:46:46 <sridhar_ram> looks both s3wong and bobh couldn't make it today
16:47:06 <sridhar_ram> #topic Bugs
16:47:36 <sridhar_ram> anyone what to discuss any specific bugs here ?
16:48:32 <sripriya> sridhar_ram: should we discuss here about the introduction of param attribute in vnf create as a heads up?
16:48:43 <sridhar_ram> I want to give an heads up on one - there is bunch of fixes coming from Parameterization ..
16:48:59 <sridhar_ram> sripriya: ah.. we crossed each other !
16:49:07 <sripriya> :-)
16:49:26 <sridhar_ram> vishwanathj: do you mind giving a quick update ?
16:49:42 <vishwanathj> sridhar_ram, sure
16:49:45 * sridhar_ram realized it should've been an agenda topic
16:51:26 <vishwanathj> I have now uploaded 3 patchsets of what sridhar_ram and sripriya were referring to......it basically adds support to onboarding a VNFD template that supports parameterized input.
16:51:52 <vishwanathj> I have created a bug https://bugs.launchpad.net/tacker/+bug/1484227
16:51:52 <openstack> Launchpad bug 1484227 in tacker "Parameterization support missing in VNFD template" [Medium,In progress] - Assigned to vishwanath jayaraman (vishwanathj)
16:51:52 <uvirtbot> Launchpad bug 1484227 in tacker "Parameterization support missing in VNFD template" [Medium,In progress]
16:51:54 <uvirtbot> Launchpad bug 1484227 in tacker "Parameterization support missing in VNFD template" [Medium,In progress] https://launchpad.net/bugs/1484227
16:52:07 <sridhar_ram> Rajkumar_Kuppura: I believe this is one of the ask you had in our earlier discussions
16:52:32 <vishwanathj> with examples of what a VNFD template would look like and what a parameter value file would look like
16:53:09 <sridhar_ram> Rajkumar_Kuppura: please review these patchset .. particularly the usage
16:53:18 <vishwanathj> would suggest you folks going through the YAML attachments to the bug and providing feedback or ask for clarification, if any
16:53:39 <vishwanathj> Did initial developer testing and the results have been good
16:54:20 <vishwanathj> that's the end of my update
16:54:29 <Rajkumar_Kuppura> Sure Sridhar.. We've scheduled 30 mins discussion with you guys tonight your time
16:54:34 <sridhar_ram> vishwanathj: thanks for this enhancement. it is an important one, provides deployer flexibility
16:54:48 <Rajkumar_Kuppura> Please we'll discuss and learn and close it
16:55:14 <sridhar_ram> Rajkumar_Kuppura: the agenda for the sync up is for git commit process
16:55:29 * sridhar_ram notes 5mins left
16:55:46 <Rajkumar_Kuppura> yes.
16:56:00 <sridhar_ram> Rajkumar_Kuppura: lets use gerritt for the review of the parameterization..
16:56:16 <sridhar_ram> we can't have offline reviews ... it needs to be done in the open!
16:56:27 <Rajkumar_Kuppura> Got it.. we'll review the patchset for parameterization
16:56:37 <sridhar_ram> Rajkumar_Kuppura: you will get use to it soon :)
16:56:43 <sridhar_ram> *used
16:56:58 <sridhar_ram> moving on ...
16:57:05 <Rajkumar_Kuppura> Thanks Sridhar
16:57:08 <sridhar_ram> #topic Open Discussion
16:57:25 <sridhar_ram> anything else ?
16:57:41 * sridhar_ram will catchup the missed portions using eavesdrop
16:57:48 <Rajkumar_Kuppura> we have to consider monasca for service assurance.
16:58:15 <Rajkumar_Kuppura> as its has analytics & monitoring engine
16:58:29 <Rajkumar_Kuppura> Please thoughts..
16:58:39 <sridhar_ram> Rajkumar_Kuppura: sure, I think we need some solid discussion on this..
16:58:53 <Rajkumar_Kuppura> yes +1
16:58:56 <sridhar_ram> bobh is handling this area.. we need him
16:59:29 <sridhar_ram> lets plan an Agenda item on Monasca integration in the week after mid-cycle..
16:59:46 <sridhar_ram> again, no IRC meeting next well..
16:59:55 <sridhar_ram> will provide an update to the team
17:00:07 <Rajkumar_Kuppura> Sure.Sridhar - please share us the invite to participate in monasca discussion.
17:00:08 <sridhar_ram> on the midcycle
17:00:15 <sridhar_ram> times up
17:00:23 <sridhar_ram> by team
17:00:28 <sridhar_ram> #endmeeting