01:01:27 <sridhar_ram> #startmeeting tacker
01:01:28 <openstack> Meeting started Wed Dec 16 01:01:27 2015 UTC and is due to finish in 60 minutes.  The chair is sridhar_ram. Information about MeetBot at http://wiki.debian.org/MeetBot.
01:01:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
01:01:32 <openstack> The meeting name has been set to 'tacker'
01:01:38 <sridhar_ram> #topic Roll Call
01:01:45 <vishwanathj> o/
01:01:48 <sripriya> o/
01:01:50 <sridhar_ram> who is here for tacker mtg ?
01:01:56 <sridhar_ram> vishwanathj: sripriya: hi there!
01:02:38 <prashantD_> hi
01:02:57 <sridhar_ram> prashantD_: howdy
01:03:10 <sridhar_ram> lets give few mins, before we start.
01:05:18 <sridhar_ram> #topic Agenda
01:05:25 <sridhar_ram> #link https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_16.2C_2015_-_APAC_Timezone
01:05:32 <sridhar_ram> #topic Annoucements
01:05:57 <sridhar_ram> Tacker Midcycle meetup is planned for end of Jan 2016
01:06:14 <sridhar_ram> this is a F2F meeting to be held in San Jose, CA
01:06:33 <sridhar_ram> Here is the poll for possible dates - #link http://goo.gl/forms/8hVPXcmoqz
01:07:12 <sridhar_ram> Please provide your inputs!
01:07:40 <s3wong> hello
01:07:49 <sridhar_ram> next.. we are heading towards Holiday season in US
01:08:04 <sridhar_ram> s3wong: hi, we just getting started...
01:08:22 <s3wong> sridhar_ram: yes
01:08:44 <sridhar_ram> I won't be available for next two weeks...
01:08:55 <sridhar_ram> .. any volunteers to run the mtg ?
01:09:10 <sridhar_ram> or do think we shd skip next two weekly meeting ?
01:09:18 <vishwanathj> i vote for skipping
01:09:31 <sripriya> +1
01:09:33 <ksantoshk> +1
01:09:36 <vishwanathj> for some of us we can use the time to do some review
01:09:45 <vishwanathj> review -> reviews
01:09:55 <natarajk> +1
01:09:56 <sridhar_ram> vishwanathj: true, our review queue is quite deep
01:10:20 <sripriya> yup, and also implementing the bluprints itself
01:10:40 <vishwanathj> +1
01:11:02 <sridhar_ram> alright.. lets skip. we will reconvene at our usual time on Jan 5th
01:11:28 <sridhar_ram> anything else to announce / heads up ?
01:11:53 <sridhar_ram> lets move on...
01:12:04 <sridhar_ram> #topic Mitaka blueprint updates
01:12:16 <sripriya> sridhar_ram: python jobs are enabled for python-tackerclient
01:12:50 <sridhar_ram> sripriya: oh, yeah.. thanks for pointing out and thanks to Yong Sheng from 99cloud
01:13:04 <sridhar_ram> gongysh: are you here ?
01:13:42 <sripriya> sridhar_ram: so any new python-tackerclient changes will need to include unit tests coverage
01:14:02 <sridhar_ram> sripriya: true...
01:14:41 <sripriya> and also the original device unit test cases will be removed eventually which is currently enabled
01:15:35 <sridhar_ram> sripriya: I hope we can convert these to "vnf" client test cases
01:16:39 <sripriya> sridhar_ram: yes, it is actually a "conversion" there should be no other major impacts as it is based on devices
01:16:50 <sridhar_ram> lets see if yong sheng joins to take up Efficient VNF placement topic
01:17:13 <sridhar_ram> sripriya: okay..
01:18:13 <sridhar_ram> sripriya: do you want to give a quick update on Multi-VIM ?
01:18:31 <sridhar_ram> sripriya: .. or shd I say multi-site ? ;-)
01:19:02 <sripriya> sridhar_ram: sure, there have been some great inputs/comments on the spec. I need to upload a new version of spec incorporating these inputs
01:19:38 <sripriya> sridhar_ram: :-) yes we have transitioned to "multi-site VIM"
01:19:47 <sridhar_ram> sripriya: I like it :)
01:20:05 <natarajk> Nice
01:20:19 <sridhar_ram> sripriya: I'm happy to see all those nice discussions..
01:20:38 <sripriya> sridhar_ram: i understand there were concerns on the term. itself regarding multisite/multiregions/VIMs which we have discussed on the spec,
01:21:14 <sripriya> sridhar_ram: also we have moved on from VIM O to NFV O as the end goals of this new component is resource management across VIMs as per ETSI doc
01:21:15 <sridhar_ram> sripriya: we need to strike a balance between MANO taxonomy and the actual openstack multisite deployments methods
01:21:51 <sridhar_ram> sripriya: yes, multi-vim is *one* of the building blocks on NFVO
01:22:34 <sridhar_ram> sripriya: while we are not taking up Resource reservation / allocation .. this feature shd evolve into that in the future
01:22:41 <sridhar_ram> overall quite pleased...
01:22:55 <sripriya> sridhar_ram: the workflow will be pretty much NFVO->VIM->Regions->Availability_Zones->Cells that will constitute as vim selection for VNF placement
01:23:36 <sripriya> sridhar_ram: agree
01:23:50 <sridhar_ram> sripriya: wow.. that's quite a level of granular placement control..
01:24:35 <sripriya> sridhar_ram: :) or it can be just NFVO->VIM (With defaults)
01:25:11 <sridhar_ram> sripriya: okay.. keep in mind, there is also automated test complexity and horizon work
01:25:41 <sridhar_ram> sripriya: .. so we need to keep the scope not run away too much..
01:26:09 <sripriya> sridhar_ram: yes, with these inputs coming in, i observe there will be lot more work on horizon side as much as the server side
01:26:42 <sridhar_ram> afveitch: hi, we are discussing multi-vim / multi-site..
01:27:05 <afveitch> ok
01:27:43 <afveitch> sridhar_ram: I am still thinking about the best way to address the things you wrote in your response
01:28:09 <sripriya> sridhar_ram: i have not through much on the automated test complexity , but if we are doing this with multiple devstack installs, it will be good to understand if this is feasible in openstack jenkins
01:28:30 <sripriya> thought*
01:28:37 <sridhar_ram> afveitch: there is also some nomenclature / terminology that's cluttering us a bit..
01:28:53 <sridhar_ram> sripriya: true, it will be good to check w/ infra team apriori
01:29:31 <afveitch> sridhar_ram: Yes, agreed.  I think if we can align the mapping of the Heat multi region with the MANO docs, it would be good
01:30:20 <afveitch> sridhar_ram: That is part of what I am working to put into my follow up to comments - then send for general review.
01:30:22 <sridhar_ram> afveitch: ... bottomline if Tacker support VIM endpoints with multiple Regions along with support for AZ we would've implicitly covered OpenStack multi-site deployments using Regions
01:31:10 <sridhar_ram> afveitch: .. sure, lets continue the discussion in the gerrit, so that it gets captured in place...
01:31:12 <afveitch> sridhar_ram: Yes, I think you are correct.  Frankly, I am working to get more familiar with the multi region to be confident in myself in responding
01:31:49 <afveitch> sridhar_ram: agree with that plan
01:32:18 <sridhar_ram> afveitch: no worries. You point on "multi-site" is interesting .. in fact, as mentioned in the comment, it will be nice to group all VIMs in a specific "site" .. perhaps even plot them in a google maps enabled dashboard :)
01:32:41 <sridhar_ram> hope I'm not fantasizing too much :)
01:33:02 <afveitch> sridhar_ram: a man's reach should exceed his grasp :-)
01:33:27 <sridhar_ram> afveitch: perfect! like it
01:33:46 <sridhar_ram> anything else - major - on multi-site vim ?
01:34:12 <afveitch> sridhar_ram: not for me, I joined late and will review the log.
01:34:25 <sridhar_ram> afveitch: sure...
01:34:30 <sripriya> sridhar_ram: nothing from my end, i will upload a new spec for further discussions
01:34:41 <sridhar_ram> sripriya: sounds good...
01:35:14 <sridhar_ram> lets move on..
01:35:29 <sridhar_ram> tbh: do you want to give a quick update on auto-resource creation ?
01:36:09 <tbh> sridhar_ram, Hi, I want to readdress the comments mentioned in bp
01:36:36 <sridhar_ram> tbh: which specific one ?
01:36:51 <tbh> but sridhar_ram I want to know about what do you mean by template parametrization
01:37:28 <sridhar_ram> tbh: remember we discussed (perhaps even decided) to create flavors during VNFD creation...
01:37:43 <tbh> sridhar_ram, yes
01:37:48 <sridhar_ram> tbh: ... that may not work if some of the properties like num_cpu is parameterized..
01:38:09 <sridhar_ram> tbh: .. you can create flavors only at vnf-creation time
01:38:50 <tbh> sridhar_ram, yes, but we thought later of sending those details to heat with out tacker creating it
01:39:15 <tbh> sridhar_ram, so that will come under vnf creation time, right? but I haven't updated in specs yet
01:39:53 <sridhar_ram> tbh: ah, yes... do you use heat to create flavor on the fly during vnf instantiation time  ?
01:40:06 <tbh> sridhar_ram, yes
01:40:20 <tbh> sridhar_ram, and the scope of flavor is same as vnf
01:40:42 <gongysh> hi
01:41:00 <sridhar_ram> gongysh: hi there, we are discussion auto-resource creation spec from tbh
01:41:08 <gongysh> cool
01:41:08 <sridhar_ram> tbh: yeah, that shd work..
01:41:14 <sripriya> sridhar_ram: tbh: essentially glance image upload is the only case that happpens during vnfd-create operation?
01:41:44 <tbh> sridhar_ram, sripriya yes
01:42:06 <tbh> sripriya,  you asked about if about flavor duplicity
01:42:14 <gongysh> tbh,  how about flavor creation?
01:42:20 <tbh> sripriya, sridhar_ram  we can have duplicate flavors
01:43:30 <tbh> gongysh, as sridhar_ram said if the template is parametrized we cannot create flavors at vnfd creation time
01:43:30 <sripriya> isnt that redundant for the user, as an operator i dont want to create duplicate flavors for each vnf requests
01:43:41 <sripriya> tbh: ^
01:44:02 <tbh> sripriya,  but as we decided earlier flavors are cheap
01:44:35 <tbh> sridhar_ram,  but template parametrization case will apply for image creation also?
01:44:39 <sridhar_ram> tbh: agree it was cheap when it was associated with VNFD...
01:44:58 <sridhar_ram> tbh: no, we shdn't allow that IMO
01:45:26 <tbh> sridhar_ram, because images are of large sizes
01:45:56 <sridhar_ram> tbh: .. back to flavors we are now taking about number of flavors -at worst case == number of VDUs in the controller..
01:46:04 <sridhar_ram> tbh: .. that doesn't look good
01:46:10 <sripriya> tbh: then i will end up having a huge list of flavors in my deployment which is not preferred (and is ugly) even though the operation is inexpensive
01:46:34 <tbh> sridhar_ram,  sripriya but we have a solution that we have implemented for this
01:47:03 <tbh> sripriya,  sridhar_ram  https://review.openstack.org/#/c/252834/
01:47:21 <sridhar_ram> folks - lets wrap this discussion and continue in gerrit.. I'd like to discussion Efficient VNF placement
01:47:28 <sridhar_ram> *discuss
01:47:32 <tbh> sripriya,  sridhar_ram  heat translator can return the best match for the flavor
01:47:43 <tbh> sridhar_ram, okay
01:47:50 <sripriya> tbh: will take a look, thanks
01:47:58 <sridhar_ram> tbh: that look promising!
01:48:09 <sridhar_ram> #topic Efficient VNF Placement
01:48:33 <sridhar_ram> gongysh: vishwanathj: hi folks.. can you give a quick update on the scope & where you are ?
01:48:56 <gongysh> sridhar_ram, I have uploaded a spec for it
01:49:09 <vishwanathj> thanks to gongysh for starting the patchset....
01:49:13 <sridhar_ram> gongysh: link ?
01:49:22 <gongysh> sridhar_ram,  https://review.openstack.org/#/c/257847/
01:49:43 <vishwanathj> I plan to add to it and collaborate alongside gongysh
01:49:56 <sridhar_ram> gongysh: awesome... that's a good kick start.. !
01:49:57 <gongysh> It will depend on tbh's resource creation BP
01:50:33 <sridhar_ram> gongysh: true, and tbh's BP depends on bobh's tosca work.. and that worries me :(
01:50:41 <gongysh> but, since we can create flavor already,  just as tbh said, we can begin the coding for flavor creation.
01:51:17 <sridhar_ram> gongysh: cool..
01:51:41 <sridhar_ram> gongysh: please work with vishwanathj to split some areas for faster progress...
01:52:11 <gongysh> we need testing much. since the openstack CI dose not provide numa and sriov testing host.
01:52:44 <sridhar_ram> I remember Cisco contributed some CI for sr-iov.. but agree that will be challenging
01:52:51 <gongysh> vishwanathj,  you can update the https://review.openstack.org/#/c/252834/ to include what tasks you will do.
01:53:26 <vishwanathj> gongysh, I have some ideas with regards to make the VNFD content for NUMA, CPU Pin, Huge Pages and vCPU topology more generic...shall discuss with you
01:53:41 <gongysh> vishwanathj, sure
01:54:01 <sridhar_ram> btw, what are the must-have features ?
01:54:07 <vishwanathj> gongysh, thanks
01:54:18 <sridhar_ram> are we shooting to include pci-passthru and sr-iov in this scope
01:54:37 <vishwanathj> I see it as being called out as stretch for mitaka in the spec
01:54:43 <gongysh> sridhar_ram,  sriov should be the first thing.
01:55:26 <sridhar_ram> gongysh: okay.. it will be great to bring it in..
01:55:50 <sridhar_ram> gongysh: .. I was not sure about the effort involved
01:56:17 * sridhar_ram I hope we can extend this mtg few mins beyond the top of the hour...
01:56:29 * sridhar_ram .. if needed
01:56:59 <sridhar_ram> alright.. that's cool.. I'll let you and vishwanathj march on..
01:57:24 <sridhar_ram> this is a crucial feature for Tacker.. ! good luck  :)
01:57:35 <vishwanathj> gongysh, looking forward to collobarating with you and learning from your experience
01:58:06 <sridhar_ram> anything else on EPA / EVP topic ?
01:58:06 <gongysh> vishwanathj,  haha, do it together, and make it happen.
01:58:17 <vishwanathj> most definitely
01:58:25 <gongysh> sridhar_ram,  shall we begin coding before spec is merged?
01:59:07 <sridhar_ram> gongysh: well.. you need some amount of coding to write good blueprints :) .. yes, as long as you are ready to alter as we go!
01:59:53 <sridhar_ram> good to see the blueprint start.. lets continue the discussion in gerrit..
02:00:00 <gongysh> ok
02:00:05 <sridhar_ram> #topic Open Discussion
02:00:24 <sridhar_ram> as discussed earlier.. there is no IRC meeting for next two weeks
02:00:31 <sridhar_ram> we will reconvene Jan 5th..
02:00:43 <sridhar_ram> tacker core will be around to merge patchsets .. so keep the work going!
02:00:53 * sridhar_ram taking two weeks off
02:00:56 <sripriya> sridhar_ram: are there any priority patchsets that needs to be closed within this week before holidays?
02:01:53 <sridhar_ram> sripriya: nothing pops at this time.. but noticed the queue is deep and we need to keep clearing them ..
02:02:02 <sripriya> sridhar_ram: ok
02:02:04 <sridhar_ram> sripriya: .. to keep things manageable
02:02:29 <s3wong> I will be around :-)
02:02:30 <sridhar_ram> one heads up / request for help - please flag patchsets that need to go to stable/liberty..
02:02:36 <sripriya> gongysh: any update on the nova patchset if it will merged soon?
02:02:37 <sridhar_ram> s3wong: thanks!
02:03:19 <sridhar_ram> will plan to release pypi pkgs for liberty / 0.2.0 in first week of Jan
02:03:22 <gongysh> sripriya, no luck. network related patch is always slow in nova.
02:03:32 <gongysh> no network guys in nova cores.
02:03:55 <sridhar_ram> gongysh: that's bad.. no wonder nova-network --> neutron is in bad state
02:04:15 <sripriya> gongysh: thanks for update
02:04:15 <gongysh> sridhar_ram,  it is true.
02:04:22 <sridhar_ram> gongysh: in fact I want this nova fix in stable/liberty ...
02:04:28 <sripriya> +1
02:04:28 <sridhar_ram> gongysh: .. is that possible ?
02:04:46 <gongysh> yes, definitely
02:04:51 <gongysh> I will push it.
02:05:00 <sridhar_ram> gongysh: thanks!
02:05:04 <sripriya> cool!
02:05:17 <sridhar_ram> gongysh: I'm glad you joined Tacker team!
02:05:36 <sridhar_ram> anything else team ?
02:05:45 * sridhar_ram we are 5mins overtime
02:05:47 <sripriya> thats it from me
02:05:52 <gongysh> sridhar_ram, my pleasure
02:06:29 <sridhar_ram> alright.. if you taking a break / vacation.. have a nice time and a safe holiday season..
02:06:35 <sridhar_ram> if you going to work.. happy coding!
02:06:41 <sridhar_ram> see you all next year!
02:06:44 <afveitch> same to you, bye
02:06:52 <sripriya> bye! happy holidays!
02:06:54 <s3wong> bye
02:06:56 <vishwanathj> Happy holidays everyone, bye
02:07:05 <natarajk> Happy Holidays, Bye
02:07:11 <sridhar_ram> bye team! lets rock on in 2016
02:07:12 <gongysh> happy holidays. bye
02:07:20 <sridhar_ram> #endmeeting