s Edge Secure Overlay Networks ESON Contact Srinivasa

s Edge Secure Overlay Networks (ESON) Contact: Srinivasa. r. addepalli@intel. com

Application Transformation (AR/VR apps, Gaming, Analytics and Even traditional applications due to sovereignty and context) Public/Private cloud m. S 4 Cloud platform m. S 4 m. S 3 m. S 2 m. S 1 Cloud Platform WAN External System m. S 3 Public/Private cloud m. S 4 Reasons: • Proximity • Data sovereignty • Economics • Context WAN To Edge N Edge 1 m. S 2 m. S 1 W A N Edge Platform m. S 2 m. S 1 Edge Platform Communication& security enablement - Across clusters - To outside users - Towards external systems. Network (LAN/WAN) Centralized computing to Geo distributed computing An App consisting of four Micro-services ms 1 talks to ms 2, ms 2 to ms 3 and ms 3 to ms 4 ms 1” is user facing service “ms 1”, “ms 2” are expected to be there together “ms 2” is stateful and hence need to talk to each other

ONAP 4 K 8 S Solution ONAP 4 K 8 S Multi Cluster Workload Orchestrator Placement controller (Optimization) Multi Cluster Traffic and Security Orchestrator Communication with individual edge clusters Enterprise Edge Network Edge CO Edge Public Cloud 3

Connectivity Challenges ONAP 4 K 8 S Placement controller (Optimization) Multi Cluster Traffic and Security Orchestrator Multi Cluster Workload Orchestrator Public/Private cloud m. S 4 External System m. S 3 Cloud platform WAN Edge 1 m. S 2 m. S 1 W A N Edge Platform Network (LAN/WAN) m. S 2 m. S 1 Edge Platform Assumptions today: • ONAP 4 K 8 S can reach the edge locations via publicly reachable IP address • Micro. Service 2 instances among edge locations can reach other. Again, expectation is that they are reachable. Reality: • Edge locations don’t have static public IP address. • Edge locations can only make outbound connections. An App consisting of four Micro-services ms 1 talks to ms 2, ms 2 to ms 3 and ms 3 to ms 4 ms 1” is user facing service “ms 1”, “ms 2” are expected to be there together “ms 2” is stateful and hence need to talk to each other

Connectivity Challenges and existing solutions Use IPv 6 addresses everywhere Not practical in all scenarios Use Overlays using SDWAN appliances Since they are not integrated with K 8 S, Distributed Service Mesh automation challenges IP subnets across edges are expected to be unique (no overlapping addresses) – May not be true in all cases as edges are from different parties

Need for ESON (Edge Secure Overlay Networks) - Proposal ONAP 4 K 8 S Placement controller (Optimization) Multi Cluster Traffic and Security Orchestrator Multi Cluster Workload Orchestrator Edges that don’t have any static public IP address, with overlapping addresses can talk to each other Public/Private cloud m. S 4 External System ESON CNF m. S 3 Call home functionality between Edges and ONAP is not required as ONAP 4 K 8 S can reach K 8 S API server of each edge. Cloud platform WAN ESON CNF Edge 1 m. S 2 m. S 1 Edge N W A N Edge Platform Network (LAN/WAN) ESON Hub m. S 2 m. S 1 Edge Platform ESON CNF Close integration with Traffic Orchestrator, to allow distributed service mesh among edges. No changes to apps No changes to existing network

s