======================================== #opendaylight-group-policy: ODL-GBP-ARCH ======================================== Meeting started by dconde at 18:03:28 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-group-policy/2014/odl_gbp_arch/opendaylight-group-policy-odl_gbp_arch.2014-06-20-18.03.log.html . Meeting summary --------------- * we are talking about need to reduce # of contracts per subject (dconde, 18:20:53) * but what about based on flow? (dconde, 18:21:01) * that's doable with conditions! - says dvorkinista (dconde, 18:21:09) * if it's anomalous we can apply those to sites provided by said servers. (dconde, 18:21:27) * but mickey says" what is the def iof flow" (dconde, 18:21:39) * 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. (dconde, 18:22:10) * dvorkinista says you can mark them (dconde, 18:22:21) * but sanjay says that only subset needs to be set. classifiers vs. conditions is unclear (dconde, 18:22:41) * filters are HTTP -- only difference is actions says dvorkinista (dconde, 18:22:53) * sanjays says what about on per-site (dconde, 18:23:26) * but if we have different sites, it's a different EPG -- says dvorkinista (dconde, 18:23:39) * info we can cover that in a clause. (dconde, 18:24:07) * functional equivalent thing are doable. not do it instance specific. (dconde, 18:24:23) * we have a functonal way to achive that in current model with clauses, etc. (dconde, 18:25:23) * we are worried about proliferation of subjects - says Sanjar (dconde, 18:29:08) * dvorkinista says we can intro containment within subject (dconde, 18:29:18) * same classifiers and multiple ACTION sets (dconde, 18:29:32) * in the world of controls -- it's never in run time. (dconde, 18:31:45) * there is an understanding of expected actions. nothing ins unplanned, says dvorkinista (dconde, 18:32:13) * this is in response to conditional labels or some other exception mechanism. (dconde, 18:32:26) * sajnay asks if we have lots of flows…then we….. (dconde, 18:33:00) * dvorkin says -- we can do anomaly detection per flow (dconde, 18:33:13) * anjays wants to see how to get away from too many subjects per flow (dconde, 18:34:55) * dvorkinista says it is not per flow. (dconde, 18:35:15) * we want to pre plan conditions to react consistently. (dconde, 18:35:31) * dvorkinista parts of contracts can be mutated over time (dconde, 18:36:14) * lenrow says if this is best practice for expected events -- that's OK (dconde, 18:36:26) * dvorkinista says let's figure out planned stuff vs. dynamic stuff. (dconde, 18:36:59) * do we want to extend concept of a session and piggy back on top of that. (dconde, 18:37:38) * sanjay asks how do we structure flows to KNOWN policies? (dconde, 18:38:50) * 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. (dconde, 18:39:32) * we want to avoid a backdoor into this. (dconde, 18:39:53) * it's OK to have exception case (like using Asmbly for dev drivers) (dconde, 18:40:31) * 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. (dconde, 18:41:12) * mickey -- how do we over ride or how to figure dyn add conditions, etc. (dconde, 18:44:56) * dconde asked whether we want these conditions to be as orthogonal a possible. (dconde, 18:50:41) * dvorkinista says yes (dconde, 18:50:47) * the conditions are planted by app owners (dconde, 18:50:55) * some form of melt-down that needs an exception to deal with anomaly. (dconde, 18:51:11) * we cannot alter intent (dconde, 18:51:38) * we want to deal with exceptons without changing intent. (dconde, 18:51:55) Meeting ended at 18:54:19 UTC. People present (lines said) --------------------------- * dconde (47) * odl_meetbot (4) * alagalah (2) * regXboi (0) Generated by `MeetBot`_ 0.1.4