18:15:13 <adetalhouet> #startmeeting Armoury Weekly
18:15:14 <odl_meetbot> Meeting started Mon Oct 19 18:15:13 2015 UTC.  The chair is adetalhouet. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:15:14 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:15:14 <odl_meetbot> The meeting name has been set to 'armoury_weekly'
18:15:26 <adetalhouet> #topic Roll Call
18:15:41 <subh> #info subh
18:15:42 <adetalhouet> please pound in
18:15:43 <anipbu> #info anipbu
18:15:55 <anipbu> by the way, I have to leave early today :(
18:16:18 <adetalhouet> will wait a minute to see if edwarnicke is joining
18:16:21 <adetalhouet> anipbu: ok sure
18:16:37 <edwarnicke> adetalhouet: :)
18:17:17 <adetalhouet> edwarnicke: could you pound in please ?
18:17:23 <edwarnicke> #info edwarnicke
18:17:30 <adetalhouet> #topic  Agenda bashing
18:17:38 <adetalhouet> #info On going tasks
18:17:44 <adetalhouet> #info  Be release plan
18:17:51 <adetalhouet> #info Interaction workflow
18:17:57 <adetalhouet> #info  SFC use case with Tacker
18:18:04 <adetalhouet> Do you guys have anything to add here?
18:18:53 <adetalhouet> Ok so let's start by checking the on going tasks
18:18:56 <adetalhouet> #topic On going tasks
18:19:05 <adetalhouet> #info NF Catalog
18:19:19 <adetalhouet> so far the model has been briefly done
18:19:50 <adetalhouet> does anyone wants to update it ?
18:20:12 <adetalhouet> let's keep this for another time
18:21:10 <adetalhouet> #info Workload manager
18:21:25 <adetalhouet> I don't see ariel on the meeting so let's discuss this at another time also
18:21:31 <adetalhouet> #info driver
18:21:36 <subh> adetalhouet : Sorry forgot to update, Maros is travelling so he will not be able to join today's meeting
18:21:39 <adetalhouet> subh: has started the work for this
18:21:49 <subh> https://git.opendaylight.org/gerrit/#/c/28265/
18:21:50 <adetalhouet> #link gerrit: https://git.opendaylight.org/gerrit/#/c/28265/
18:21:57 <adetalhouet> subh: ok np
18:22:09 <adetalhouet> we had a few feedback
18:22:10 <subh> I've updated the model for the driver registry
18:22:20 <adetalhouet> We definitely need more feedback form the community
18:22:33 <adetalhouet> subh: yes I saw that, thanks
18:22:51 <subh> Reinaldo Penno also have some comments regarding naming convention
18:23:42 <adetalhouet> ok I'm reading the comments
18:24:12 <adetalhouet> As he mentioned, it would be nice to have identities type so it's easy to expand
18:24:43 <adetalhouet> so instead of image we could have type
18:24:51 <adetalhouet> what do you think subh ?
18:25:29 <adetalhouet> also, we will leave this patch as a WIP so folk can review it
18:25:45 <subh> I thing type is not appropriate
18:26:02 <adetalhouet> so basically what is this image container for
18:26:11 <subh> as it is the image name which driver will instantiate
18:26:17 <adetalhouet> goruping sorry
18:26:54 <adetalhouet> you mean the NF image based on the NFcatalog
18:27:02 <adetalhouet> so it's the NF catalog entry reference
18:27:03 <subh> yes
18:27:03 <adetalhouet> ?
18:27:24 <adetalhouet> Ok, so now the identify mentioned by Renaldo make more sense
18:27:44 <subh> but driver should also have some info for the image
18:27:59 <subh> like in one of the comments i have mentioned it
18:28:14 <adetalhouet> If you define some based identity for the NF catalog, then each NF will expand the based identity and will define its own
18:28:26 <adetalhouet> thus we are able to retrieve the NF info based on this identity
18:28:41 <adetalhouet> subh: does it make sense?
18:29:08 <subh> should driver refer NF catalog for image info ?
18:29:22 <subh> or driver should be aware about image by its own ?
18:30:27 <adetalhouet> well I think the driver should be standalone, but it is true that the NF can specify some precise configuration for its workload
18:30:47 <adetalhouet> thus I think the driver should be able to refer to the NF catalog for image info
18:31:30 <subh> I have one question, so image info will be populated by NF not by the driver .. is it correct to say
18:31:49 <adetalhouet> Correct, this is related to the NF
18:31:50 <subh> NF/ NFcatalog
18:31:53 <anipbu> catalog should have image info.  this can be referenced by apps or by tacker driver, docker driver, custom driver, etc.
18:32:09 <anipbu> at least that is my understanding.
18:32:10 <adetalhouet> anipbu: I agree
18:32:21 <adetalhouet> anipbu: this is also what I think
18:32:26 <subh> ok
18:33:00 <anipbu> the goal here is to make catalog the ODL go-to-guy for image info.
18:33:19 <subh> Then we should remove the image group from the driver-regisytry
18:33:41 <adetalhouet> anipbu: yes I couldn't agree more
18:34:30 <adetalhouet> subh: I think the driver need a reference of the image in used, but doesn't need to whole image
18:34:30 <anipbu> adetalhouet: good we're in agreement :)
18:34:45 <subh> ok :)
18:34:58 <subh> got it.
18:35:27 <anipbu> sorry guys i have to go.  I'll read the meeting minutes after.
18:35:34 <adetalhouet> meaning the workload manager will be provided by both the NF to use and the driver to use, and will configure the vm
18:35:50 <adetalhouet> anipbu: sure, thanks :)
18:36:30 <adetalhouet> should we move to the next topic?
18:36:33 <subh> sure
18:36:38 <adetalhouet> #topic Be release plan
18:36:44 <adetalhouet> #info documentation
18:36:56 <subh> https://git.opendaylight.org/gerrit/#/c/28541/
18:36:57 <adetalhouet> We have accomplished M3 the doc is the missing item
18:37:06 <adetalhouet> #link https://git.opendaylight.org/gerrit/#/c/28541/ doc patch
18:37:16 <adetalhouet> #info subh started the doc in the patch above
18:37:30 <adetalhouet> subh: do you need anything?
18:37:38 <adetalhouet> to purse to documentation
18:37:45 <adetalhouet> purse/pursue
18:37:46 <subh> yes, some review comments and suggestion
18:37:51 <subh> to write the sections
18:37:56 <adetalhouet> Ok sure
18:38:20 <adetalhouet> #action @all to review the documentation patch and give feedback https://git.opendaylight.org/gerrit/#/c/28541/
18:38:43 <adetalhouet> For the Be planning will have M4 coming along
18:38:55 <adetalhouet> So we need to prepare the deliverables
18:39:01 <subh> ok
18:39:14 <adetalhouet> I think the most important is, for now, the sequence diagram
18:39:23 <adetalhouet> it must be finished and approve
18:39:47 <adetalhouet> #link https://git.opendaylight.org/gerrit/#/c/27263/
18:40:09 <subh> are we going to put the sequence diagram in the docs ?
18:40:22 <adetalhouet> subh: Yes, this is a really good idea
18:40:58 <subh> okey :)
18:41:01 <adetalhouet> And the last topic for today is
18:41:09 <adetalhouet> #topic SFC use case with Tacker
18:41:36 <adetalhouet> I personally don't have must to say here as alagah is not there
18:41:54 <adetalhouet> And also, the underlying functionality needs to be done
18:42:36 <adetalhouet> does anyone has something to say
18:43:42 <adetalhouet> #topic open mic
18:44:17 <adetalhouet> I think there is a really low attendance in our meetings
18:44:43 <subh> yup
18:44:49 <adetalhouet> I have the feeling not so many people get involve in Armoury, thus it is hard to go ahead and get tasks done
18:45:03 <adetalhouet> subh: thanks for being there :)
18:45:35 <subh> it is helpful for me for my learning :)
18:45:45 <adetalhouet> I know most of us don't have much cycles this days, but I would really appreciated if at least, half of the initial committers show up at the meeting
18:46:14 <adetalhouet> subh: glad you can learn
18:46:36 <adetalhouet> #topic cookies
18:47:00 <adetalhouet> #endmeeting