18:23:28 #startmeeting Armoury Weekly 18:23:28 Meeting started Mon Oct 12 18:23:28 2015 UTC. The chair is anipbu. Information about MeetBot at http://ci.openstack.org/meetbot.html. 18:23:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:23:28 The meeting name has been set to 'armoury_weekly' 18:23:38 #topic Roll Call 18:23:45 #info anipbu 18:23:52 please pound in for ppl attending the meeting 18:23:52 #info subh 18:24:02 #info ariel_noy 18:24:23 #info edwarnicke 18:24:29 Today we will discuss the following... 18:24:33 #On going tasks 18:24:36 #info On going tasks 18:24:48 #info Be release plan 18:25:00 #info Interaction workflow 18:25:09 #info SFC use case with Tacker 18:25:16 #info feature list 18:25:36 Do you guys have anything you would like to discuss? 18:26:27 #topic On Going Tasks 18:27:30 any updates from folks on their tasks? 18:27:34 mmarsale1: You there? 18:27:51 anipbu: Do we have a list of who is working on what? 18:28:29 anipbu: i am working on driver-registry model. I discussed with Alexis about this in last meeting. https://git.opendaylight.org/gerrit/#/c/28265/ 18:28:34 #info https://trello.com/b/zsERKgeV/odl-armoury 18:28:41 #undo 18:28:41 Removing item from minutes: 18:28:45 #link https://trello.com/b/zsERKgeV/odl-armoury 18:28:52 subh: I can't view that link, is it a draft? 18:28:57 yes 18:29:28 what should I do to make it visible ? 18:31:01 I cannot access the link as well as well. 18:32:17 anipbu: should I try to add odl-armooury in reviewer ? 18:33:12 I'm not familiar with the draft capability. I normally upload my drafts as a normal patch but with the WIP in the message. 18:33:24 subh: If you would make it visible it would be easier for folks to see it :) 18:33:50 anipbu: I tend to do what you just suggested myself... (In fact, I think I was the one who started doing that at ODL :) ) 18:33:51 ok please go ahed, I will try to look for the option and let you know 18:34:24 #action subh to make driver-registry model patch visible for community 18:34:40 I have also updated the trello with the link to the patch 18:34:51 https://trello.com/c/Gb6QcQ9b/3-driver-registery-model 18:35:35 subh: any comments you would like to make on the driver registry model before we move on? 18:36:06 I think I need the comments on the model. 18:36:16 i have discussued with Alexis once 18:36:48 that I think we can do it over mails . 18:37:00 when you have made the patch visibility for the rest of the community, please send an email to the mailing list. thanks. 18:37:15 sure anipbu :) 18:39:01 Any other updates from folks on on going tasks? 18:40:58 I will need guide how to import object from other modules that is not in the base 18:41:45 ariel_noy: Say more 18:41:49 ariel_noy: I don't quite follow you 18:41:55 As the workload manager use the catalog and drivers it need it 18:42:17 ariel_noy: I would advocate a structure like this 18:42:23 Catalog Manager - standalone 18:42:34 Workload Manager - depends on Catalog Manager 18:42:49 Various drivers - depend on Workload manager 18:42:59 That way if you have n possible drivers, you can install only the m you want 18:43:03 Network Function in the Catalog but not in the front and Work load manger need to return it 18:43:19 ariel_noy: I don't follow that last sentence 18:43:20 If you prefer to work in String which is ID that is possible 18:43:41 ariel_noy: Could you say more... I'm a bit lost 18:43:47 If we want it to be yang object than I need to be able to point to that interface 18:45:08 for example catalogVNFType should be an object VNF Type from catalog and not object of work load manager 18:45:33 Maybe this is just symantics of yang that I do not know how 18:45:47 ariel_noy: I think I'm following you and *probably* agree 18:45:51 My basic point is that stacking 18:45:57 CatalogManager should be able to stand alone 18:46:11 I agree 18:46:11 Workload Managers should be agnostic as to drivers (but depend on Catalog Manager) 18:46:23 But work load manager should not 18:46:25 Drivers should depend on Workload Manager (so folks can pick and choose :) ) 18:46:43 Should be able to reference type from the catalog 18:46:46 When you say Workload Manager shouldn't stand alone, do you mean it should depend on VNF Catalog? 18:47:00 yes 18:47:52 We can take it offline and have a talk some time 18:48:22 yes, I think this needs more discussion over email. 18:48:38 ariel_noy: could oyu start a email thread to discuss in more details? 18:48:48 ok 18:49:00 ariel_noy: I agree with you that Workload Manager should depend on VNF Catalog 18:50:05 #action ariel_noy to start email thread for guidance on how to import object from other modules that is not in the base. 18:51:44 For catelog, I don't think there's been any updates on that discussion. I'll leave the status unchanged https://git.opendaylight.org/gerrit/#/c/26641/1 18:52:25 Any other updates on on going tasks? 18:54:06 Need to drop a few minute early 18:54:29 #info Please try to keep the trello board up to date on any updates you have for the corresponding tasks: https://trello.com/b/zsERKgeV/odl-armoury 18:54:36 ariel_noy: okay 18:54:57 #topic Be release plan 18:55:07 #link https://wiki.opendaylight.org/view/Armoury/Beryllium_Release_Plan 18:55:14 this is our finalized release plan 18:55:23 any comments please email the mailing list 18:55:37 #topic Interaction workflow 18:56:17 I would like to table this discussion when there is more members on the meeting 18:56:35 #info Interaction workflow discussion tabled for next week 18:56:51 #topic SFC use case with Tacker 18:57:20 I also think this topic should be tabled until next week 18:57:37 because alagalah and adetalhouet and not on the meeting. 18:57:52 #info SFC use case with Tacker discussion tabled for next week 18:58:05 #topic feature list 18:58:25 #link https://lists.opendaylight.org/pipermail/armoury-dev/2015-October/000048.html 18:58:42 there an email thread right now to discus the feature list. 18:58:54 folks should feel free to respond to the email thread for feedback. 19:00:02 anyone else have topics they would like to discuss? 19:00:05 is anybody else in the meeting? 19:01:26 Okay. thanks everyone. 19:01:28 #topic cookies 19:01:51 #endmeeting