1 / 11

Group Based Policy

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).

dex
Download Presentation

Group Based Policy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Group Based Policy Weekly Requirements Meeting 7-7-2014

  2. 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)

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

  4. 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.

  5. 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)

  6. 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.

  7. 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

More Related