18:03:28 <dconde> #startmeeting ODL-GBP-ARCH
18:03:28 <odl_meetbot> Meeting started Fri Jun 20 18:03:28 2014 UTC.  The chair is dconde. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:03:28 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:03:28 <odl_meetbot> The meeting name has been set to 'odl_gbp_arch'
18:03:54 <dconde> #chair regXboi
18:03:54 <odl_meetbot> Current chairs: dconde regXboi
18:20:53 <dconde> #info we are talking about need to reduce # of contracts per subject
18:21:01 <dconde> #info but what about based on flow?
18:21:09 <dconde> #info that's doable with conditions! - says dvorkinista
18:21:27 <dconde> #info if it's anomalous we can apply those to sites provided by said servers.
18:21:39 <dconde> #info but mickey says" what is the def iof flow"
18:22:10 <dconde> #info sanjay says "user X comm to wiki site A on HTTP" that flow is what Sanjay wants to apply security, improve experience, etc. but you want to do something different.
18:22:21 <dconde> #info dvorkinista says you can mark them
18:22:41 <dconde> #info but sanjay says that only subset needs to be set. classifiers vs. conditions is unclear
18:22:53 <dconde> #info filters are HTTP -- only difference is actions says dvorkinista
18:23:26 <dconde> #info sanjays says what about on per-site
18:23:39 <dconde> #info but if we have different sites, it's a different EPG -- says dvorkinista
18:24:07 <dconde> #info info we can cover that in a clause.
18:24:23 <dconde> #info functional equivalent thing are doable. not do it instance specific.
18:25:23 <dconde> #info we have a functonal way to achive that in current model with clauses, etc.
18:29:08 <dconde> #info we are worried about proliferation of subjects - says Sanjar
18:29:18 <dconde> #info dvorkinista says we can intro containment within subject
18:29:32 <dconde> #info same classifiers and multiple ACTION sets
18:31:33 <dconde> #inf sanjay asks whether we burden dynamic app to come up with all this, or is this being figured out in runtime?
18:31:45 <dconde> #info in the world of controls -- it's never in run time.
18:32:13 <dconde> #info there is an understanding of expected actions. nothing ins unplanned, says dvorkinista
18:32:26 <dconde> #info this is in response to conditional labels or some other exception mechanism.
18:33:00 <dconde> #info sajnay asks if we have lots of flows…then we…..
18:33:13 <dconde> #info dvorkin says -- we can do anomaly detection per flow
18:34:55 <dconde> #info anjays wants to see how to get away from too many subjects per flow
18:35:15 <dconde> #info dvorkinista says it is not per flow.
18:35:31 <dconde> #info we want to pre plan conditions to react consistently.
18:36:14 <dconde> #info dvorkinista parts of contracts can be mutated over time
18:36:26 <dconde> #info lenrow says if this is best practice for expected events -- that's OK
18:36:42 <dconde> #info but if we cannot support high frequency surprises
18:36:59 <dconde> #info dvorkinista says let's figure out planned stuff vs. dynamic stuff.
18:37:38 <dconde> #info do we want to extend concept of a session and piggy back on top of that.
18:38:50 <dconde> #info sanjay asks how do we structure flows to KNOWN policies?
18:39:32 <dconde> #info dvorkinista semanticlly we can express is as for two EPs, each belong to an EPG, in context of a given contract, we need to overwrite a set of subjects. that's an exception.
18:39:53 <dconde> #info we want to avoid a backdoor into this.
18:40:31 <dconde> #info it's OK to have exception case (like using Asmbly for dev drivers)
18:41:12 <dconde> #info in the third option in yesterday's meeting, only thing we change are that there are not rules, but we put into filters of a subject.
18:44:56 <dconde> #info mickey -- how do we over ride or how to figure dyn add conditions, etc.
18:50:41 <dconde> #info dconde asked whether we want these conditions to be as orthogonal a possible.
18:50:47 <dconde> #info dvorkinista says yes
18:50:55 <dconde> #info the conditions are planted by app owners
18:51:11 <dconde> #info some form of melt-down that needs an exception to deal with anomaly.
18:51:38 <dconde> #info we cannot alter intent
18:51:55 <dconde> #info we want to deal with exceptons without changing intent.
18:53:38 <alagalah> dconde: Can you send me the minutes too please
18:53:55 <dconde> alagalah: I will post the meetbot URL
18:54:01 <alagalah> Ty sir
18:54:19 <dconde> #endmeeting