17:05:16 #startmeeting MODEL 17:05:16 Meeting started Fri May 2 17:05:16 2014 UTC. The chair is dconde. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:05:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:05:16 The meeting name has been set to 'model' 17:05:21 #chair alagalah 17:05:21 Current chairs: alagalah dconde 17:05:42 #info jmedved was to convert model to YANG 17:05:50 #info and workarounds and changes to model 17:06:11 #info recap coming w/ requirements of model 17:06:23 #info YANG cannot expressed self contained constructs 17:06:33 #topic Discussion of YANG and UML capabailities 17:06:36 #info linear chains are preferred to mimic containment 17:06:42 #info jmedved was to convert model to YANG 17:06:46 #info and workarounds and changes to model 17:06:51 #info recap coming w/ requirements of model 17:06:55 #info YANG cannot expressed self contained constructs 17:07:04 #info how to implement nested logical stmts 17:07:20 #info we can either keep formulas as blobs or str 17:07:24 #info specifically for matchers 17:07:31 #info for simplify the matchers. 17:07:39 #undo 17:07:39 Removing item from minutes: 17:07:47 #info to simplify the matchers 17:09:00 #info we will use YANG as a authoritative description of model, rather than diagram 17:09:08 #info from readams 17:09:29 #info ought to extend YANG? 17:09:29 #action dvorkinista (Mike D) to modify Matcher logic to be either ANDs, ORs, with Label EXCLUDE for negation. This will be a single level ie (A AND B AND C), (A OR B OR C), EXCLUDE (A AND B) 17:09:43 #info but that is second phase. 17:10:17 #info dvorkinista recommends no circumstances and scoring. 17:10:29 #info assume there exists a governance system to update the endpoints. 17:10:38 #info as an external input 17:10:48 #info here 17:11:14 #info it will not reduce the attractiveness of the model. 17:11:47 #info lenrow says we don't need to do all the use-cases. 17:12:27 #info no matter what we do, we have to architect for extensibility. 17:12:41 #topic MD-SAL / YANG requirements discussion - broader discussion 17:13:33 #info best thing for community is to look at readams's paper on how we can achieve goals for simplification. 17:13:46 #info paper to be finalized and shared next week. 17:14:02 jmedved 17:14:05 are you there? 17:14:37 #info we will assume jmedved is in agreement. since he wasn't on this moment. 17:15:37 #info we can look at what readams has transcribed. 17:15:59 #topic review of readams's yang model for 0.97 17:16:35 #info we are reviewing the doc now on hangout screen share now. 17:16:39 readams: when wil lthe paper be available? 17:17:41 #info early next week 17:17:43 jmedved: Tue latest 17:17:47 jmedved: COB 17:18:14 #info trying to get inhr and obj modl to map to UML doc. 17:18:25 #info challenge. model is complex 17:19:29 #info starting w/ jmedved's model and adding constructs - issues are complexity and decipher the "runes" w.r.t. inconsistencies that readams will rsolve w/ dvorkinista 17:19:42 #info same type @ two levels of hier. 17:20:26 #info he is using grouping but still needs to be mapped to a different location. 17:22:35 #info running into restrictions Java that is generated. 17:23:15 #info other challenge. relator object 17:23:52 #info inheritance is problematic. children override values, so what should be in base class? 17:24:21 #info are you using AUGMENT? readams is using groupings. 17:25:21 #info discussing whether we are overriding base types. how best to do that? 17:26:22 #info if super class has restrictions, we can reason at that level? or shall we use REFINE stmt? It's all tricky. 17:27:23 #info dvorkinista says we used to have match type in relator in original. so we have a vestigial item that needs to resolved. 17:28:01 #info it's possible to just have a relator. use a target, selector, and that's it. can be named or not-named. 17:29:52 #info dvorkinista is fine not using inheritance. 17:30:15 #info relator can be a providing selector or a consumer selector. do not treat them as separate things. 17:31:18 Is this GBP arch meeting or GBP model meeting (or are they one and the same now)? 17:31:33 thi sis the MODEL meeting. 17:31:45 ARCH meeting follows at 11 17:32:01 Great thanks. I'll update the Wiki. 17:32:33 #info once we have a proper model, it will be resolved in a concrete yang model 17:32:51 #info yang becomes authoritative. 17:33:36 #info but let us remembe that UML is easier to read... 17:34:19 #action alagalah will write a whitepaper that describes the UML model. 17:35:01 #info and text is ambiguous. so we do not want to replace UML 17:35:36 #info should we annotate UML? dvorkinista prefers that. 17:36:20 #info we will disucss how best to do it 17:36:32 #action we will annotate UML instead -- alagalah 17:37:07 #info lenrow has a "for dummes" draft in progress. 17:38:25 #topic open forum. 17:39:09 #info mickey_spiegel notices that many pages of model refers to same thing. dvorkinista says it is used to describe concept. 17:39:26 #info alagalah says each page tries to express a concept in context. 17:40:24 #action dvorkinista to restruct model in structure, definition use 17:40:47 #info lenrow questions. 17:41:19 #info is traffic chaining expression difficult? 17:41:41 #info we are missing some items. like sensitivities ! 17:42:09 #info dvorkinista will update model according to how it was expressed in YANG. 17:42:44 #info we meant to say service chaining, not traffic chaining. 17:43:29 #info let us try to model this. we are trying to pull in people from L4-L7 companies for their perspective. 17:44:39 #info let's have a discussion on what to include -- 17:45:12 #info we are speculating what RADware wants to do, or F5. 17:45:23 #info there is a project proposal for service chaining and see if it's common or not. 17:46:35 #info new svc chaining encapsulation type -- being proposed. 17:47:04 #link https://wiki.opendaylight.org/view/Project_Proposals:Service_function_chaining 17:47:30 #info project is service function chaning that is being proposed. 17:47:38 #info visions from ETSI and IETF, etc. 17:48:43 #info there are lots of projects with some overlap 17:48:53 #info we can render to it. 17:49:56 #info mickey_spiegel says - is this a matter of rendering, or referring to their model? 17:51:32 #info they are concentrating on instance. GBP can focus on policy. this is complementary. 17:52:11 #info we will have a conversation. 17:52:35 #action alagalah will talk w/ ewarnicke 17:53:03 #action alagalah will talk w/ ed warnicke regarding service chaining. 17:54:30 typing is muting you guys 17:54:42 ack 17:55:29 #info their diagram has more stuff than svc chaining ought to have. 17:56:19 #endmeeting