20:05:11 <alagalah> #startmeeting UseCases
20:05:11 <odl_meetbot> Meeting started Mon Jun 23 20:05:11 2014 UTC.  The chair is alagalah. Information about MeetBot at http://ci.openstack.org/meetbot.html.
20:05:11 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:05:11 <odl_meetbot> The meeting name has been set to 'usecases'
20:05:27 <Bhushan_> Hi What is the Google hangout details for the Use cases meeting today?
20:05:32 <Bhushan_> Or are we using WebEx
20:05:46 <alagalah> #chair busha
20:05:46 <odl_meetbot> Warning: Nick not in channel: busha
20:05:46 <odl_meetbot> Current chairs: alagalah busha
20:06:04 <dconde> we are on webex today
20:06:05 <dconde> https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4NPPO6UULL1B0DFPK2HQ9VZX8-9VIB&rnd=563175.79385
20:06:42 <dconde> Bhushan_: sent the link
20:06:46 <alagalah> #topic dvorkin sent exceptions list
20:07:49 <Bhushan_> Thanks
20:09:31 <alagalah> #info Cisco user vs Sales users need different access
20:10:32 <alagalah> #info sanjay says that some users need lower security and some need hi security
20:12:42 <alagalah> #info sanjay talks about a hierarchy, dvorkin say lets make subjects hierarchical, no contracts
20:15:10 <alagalah> #info examples are getting more complex, dvorkin says classifiers into clauses
20:16:30 <alagalah> #info sanjay says single list of rules, but dvorkin says this is what we are trying to avoid..... but it complicates more mainstream cases
20:19:56 <alagalah> #info readams proposes that we have a list of actions
20:25:29 <alagalah> #info readams wants to be careful of defining an exponential # of rules.
20:27:09 <alagalah> #chair mickey_spiegel
20:27:09 <odl_meetbot> Current chairs: alagalah busha mickey_spiegel
20:27:21 <alagalah> #chair tbachman
20:27:21 <odl_meetbot> Current chairs: alagalah busha mickey_spiegel tbachman
20:28:58 <alagalah> #info dvorkin says we can make an exception at the clause level
20:32:27 <tbachman> #link https://wiki.opendaylight.org/view/Group_Policy:Sub-Groups:REQUIREMENTS#Documents
20:32:32 <tbachman> dvorkinista: ^^^^
20:32:32 <alagalah> #info dvorkinista is going to modify the slides
20:34:40 <alagalah> #info dvorkinista is changing the PPT
20:50:01 <alagalah> #info dvorkinista is going through this email, changing topic
20:50:19 <alagalah> #topic Dvorkin's over-ride model
20:51:11 <alagalah> #info new model that defines clobber etc for contracts
20:52:18 <alagalah> #info lenrow points out that its more of a stack type structure where you pop stuff off
20:54:01 <alagalah> #info lenrow points out that AAA system has control over where things get added or clobbered
20:56:23 <alagalah> #info mickey_spiegel asks question about clobbering QOS
21:02:34 <alagalah> #info dvorkinista goes to get note book with thoughts documented
21:04:24 <alagalah> #info dvorkinista says that exception rules are for planning for the unplannned.... but the model should handle normal operations
21:05:21 <alagalah> #info dvorkinista says that normal intent should be maintained until exceptions occur with overrides
21:05:49 <alagalah> #info lenrow is concerned about the stack of overrides and how they resolve
21:14:12 <lenrow> #info I think of this as a "parent-override" the tenant is being overruled by an ancestor, no?
21:18:44 <alagalah> someon needs to take up scribe
21:31:09 <dconde> #info unplanned policies can come in any form, says sanjay
21:31:46 <dconde> #info dvorkinista infrastrcture rules that has nothing to do with user intent can happen --like DDoS detection or firewall rule
21:31:58 <alagalah> thanks dan
21:33:02 <dconde> #info for data center scenarios , this should be sufficient says dvorkinista
21:33:37 <dconde> #info lenrow says it's out of scope of GBP (i.e. for simple use case)
21:33:51 <dconde> #info sanjay will work based on it.
21:34:07 <dconde> #info ball passed back to lenrow
21:34:54 <dconde> #info lenrow seeking volunteers to write up ideas and prsent in future meeting. UC use-cases has gone as far as we can without a straw man
21:35:26 <dconde> #info such as on-demand traffic engineering use cases.
21:35:53 <dconde> #info we need a volunteer for a one page description
21:36:15 <dconde> #info we need more interction with SFC in ODL and SFC in IETF and invite them to these meetings
21:36:41 <dconde> #info and write a paper on flow rules are written in each format.
21:36:53 <dconde> #info dvorkinista has talk w/ Paul Quinn.
21:37:20 <dconde> #info there are OK with GBP specifying high level intent.
21:37:32 <dconde> #info lenrow asks who is north and south?
21:37:41 <dconde> #info dvorkinista  says GBP is north of them (SFC)
21:38:21 <dconde> #info lenrow what about competing rule writers?
21:38:35 <dconde> #info dvorkinista says hes, but wants to defer that.
21:38:43 <dconde> #unfo
21:38:51 <s3wong> what is unfo :-)
21:40:03 <dconde> #info an awful lot of meeting. let's see in next few days
21:40:07 <dconde> #endmeeting