group based policy weekly requirements meeting 7-7-2014

11
Group Based Policy Weekly Requirements Meeting 7-7-2014

Upload: angelica-shaw

Post on 11-Jan-2016

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Group Based Policy Weekly Requirements Meeting 7-7-2014

Group Based PolicyWeekly Requirements Meeting

7-7-2014

Page 2: Group Based Policy Weekly Requirements Meeting 7-7-2014

AGENDA

• Continue enterprise access use case analysis (40 Minutes)• Review SFC use case (20 Minutes)• Discuss modeling requirements from SFC and steering use case.

Create "ask" for modeling group work (30 Minutes)

Page 3: Group Based Policy Weekly Requirements Meeting 7-7-2014

Continue Enterprise Access Discussion• Sanjay• https://wiki.opendaylight.org/view/File:Policy_Usecases.pptx

Page 4: Group Based Policy Weekly Requirements Meeting 7-7-2014

•To support multi-tenant aware service functions or SNs, traffic being serviced by a service function chain has to be identified by a tenant identifier. •A tenant identifier has to be carried along with the traffic to be serviced.• It is typical of tenant assets to be deployed in an isolated layer2 or layer3

domain such as VLAN, VXLAN or VRF.• It has to be noted that the SNs themselves maybe deployed in different

domains to suit the deployment needs of the SP and hence using the domain in which the SN is deployed is not an option. Although such a model is feasible it removes the deployment flexibility for the service providers. to the WAN edge.

Page 5: Group Based Policy Weekly Requirements Meeting 7-7-2014
Page 6: Group Based Policy Weekly Requirements Meeting 7-7-2014

More DC requirements

• SC exist in both N/S and E/W directions• Subscriber to DC is North/South• Intra-DC is East West

• Multiple Load balancing schemes required• Hash based on header• Utilization of SF pool• Other

• SF Pools elastic (add/remove appliances dyanamically)

Page 7: Group Based Policy Weekly Requirements Meeting 7-7-2014

Additions to GBP Model for DC SFC

• In addition to EPGs representing the “targets” of the SFCs, Each SF/VF in chain is an EPG (one or more EPs)• Need notion of Load Balanced Contract (LBC() between EPG1

(subcribers) , tied to consuming LBC witth EPG2(SF1), tied to LBC with EPG3 (SF2), tied to consuming LBC with EPG-N (SF-N), tied to contract with EPG-I (Internet). • Need to propose exact syntax of LBC in a chain for GBP• Need to take this proposal to ODL SFC team for review.

Page 8: Group Based Policy Weekly Requirements Meeting 7-7-2014
Page 9: Group Based Policy Weekly Requirements Meeting 7-7-2014
Page 10: Group Based Policy Weekly Requirements Meeting 7-7-2014
Page 11: Group Based Policy Weekly Requirements Meeting 7-7-2014

Additions for Mobile SFC Use Case

• Changes to Scaling Numbers (Tens/hundreds of millions of subs), huge events per second?• Need “lossless handoff” intent or similar?• Anything unique to these chains other than scale, roaming, dynamism