pristine rina-tnc-2016

Download Pristine rina-tnc-2016

Post on 20-Jan-2017

252 views

Category:

Internet

0 download

Embed Size (px)

TRANSCRIPT

Detailed vision and objectives

Simplifying multi-layer network management with RINAEduard Grasa, Fundaci i2CAT, FP7 PRISTINETNC 2016, Prague, June 13th 2016

Simplifying Multi-layer Network Management with RINA

Computer network being managedEvents

Reason about events

Layers state modelsCompare with desired stateUpdated network state

Desired network state

Reason about config changes

Network state driftLayers config modelsApply updated config

Network Management System2Automating network management Complexity of management models key metric to evaluate the limitations/possibilities on network automation (and its cost)

2

Are All IP networks easy to automate?Computer networking & telecom industry has been steadily moving towards an all IP world. Is all-IP convergence a simple, scalable, robust, manageable, performing and future-proof solution for all types of computer networks?Could be ifThe IP protocol suite had been designed with generality in mind, allowing its protocols to adapt to specific network environmentsThe IP protocol suite is well know for having no scalability, performance or security issues

Simplifying multi-layer network management with RINA3

12

14

2

There is a better approach: RINANetwork architecture resulting from a fundamental theory of computer networkingNetworking is InterProcess Communication (IPC) and only IPC. Unifies networking and distributed computing: the network is a distributed application that provides IPCThere is a single type of layer with programmable functions, that repeats as many times as needed by the network designersAll layers provide the same service: instances or communication (flows) to two or more application instances, with certain characteristics (delay, loss, in-order-delivery, etc)There are only 3 types of systems: hosts, interior and border routers. No middleboxes (firewalls, NATs, etc) are neededDeploy it over, under and next to current networking technologies

4

1

2

3

4

5

6Simplifying multi-layer network management with RINA

4

RINA macro-structure (layers)Single type of layer, consistent API, programmable policies

Host

Border router

Interior Router

DIF

DIF

DIFBorder router

DIF

DIF

DIF (Distributed IPC Facility)

Host

App A

App B

Consistent API through layers

IPC APIData TransferData Transfer ControlLayer ManagementSDU DelimitingData Transfer Relaying and MultiplexingSDU ProtectionRetransmission ControlFlow ControlRIB DaemonRIBCDAP Parser/GeneratorCACEP

EnrollmentFlow AllocationResource AllocationRoutingAuthenticationState VectorState VectorState VectorData Transfer Data Transfer Retransmission ControlRetransmission ControlFlow ControlFlow ControlIncreasing timescale (functions performed less often) and complexityNamespace ManagementSecurity Management

Layers are resource allocators, provide IPC services over a certain scope, they all have the same functions5

IP protocol suite macro-structureFunctional layers organized for modularity, each layer provides a different service to each otherAs the RM is applied to the real world, it proofs to be incomplete. As a consequence, new layers are patched into the reference model as needed (layers 2.5, VLANs, VPNs, virtual network overlays, tunnels, MAC-in-MAC, etc.)

6

(Theory)

(Practice)Simplifying multi-layer network management with RINA

- Complexity, complexity, complexity (unbounded, nobody knows what new combinations of layers may be needed in the future6

Network managementCommonality is the key to effective network management

7Commonality and consistency in RINA greatly simplifies management models, opening the door to increased automation in multi-layer networksReduce opex, network downtime, speed-up network service delivery, reduce components that need to be standardised

From managing a set of layers, each with its own protocols, concepts and definitions to managing a common, repeating structure of two protocols and different policiesSimplifying multi-layer network management with RINA

Core/backbone: IP/MPLSMetro aggregation: Carrier EthernetAccess: xDSL, FTTH (PON tech), WiFI, LTEServices: L2/L3 VPNs, Internet access, IMS

Micro DC: C-RAN, Mobile Edge computingMetro/regional/national DCs: provider service platforms (DNS, SMTP, etc) LTE EPC (S-GW and/or P-GW, MME), IMS, cloud hosting, NOC, etc7

Separation of mechanism from policy8

IPC APIData TransferData Transfer ControlLayer ManagementSDU DelimitingData Transfer Relaying and MultiplexingSDU ProtectionRetransmission ControlFlow ControlRIB DaemonRIBCDAP Parser/GeneratorCACEP

EnrollmentFlow AllocationResource AllocationRoutingAuthenticationState VectorState VectorState VectorData Transfer Data Transfer Retransmission ControlRetransmission ControlFlow ControlFlow ControlNamespace ManagementSecurity ManagementAll layers have the same mechanisms and 2 protocols (EFCP for data transfer, CDAP for layer management), programmable via policies.All data transfer and layer management functions are programmable!Dont specify/implement protocols, only policiesRe-use common layer structure, re-use policies across layersThis approach greatly simplifies the network structure, minimizing the management overhead and the cost of supporting new requirements, new physical media or new applications

Case study: Large-scale DC NetworkLarge-scale DCN connects around 100k servers, how to realize and manage the DCN with RINA and IP?Simplifying multi-layer network management with RINA9

IP-based DCN design(With minimal number of protocols)Data plane (up), control plane (down). L3-only fabric10

ToRToRFabricSpineFabricServerServer

IPv4 or IPv6 (Fabric layer)

UDP

VMVM

Ethernet

Ethernet

Ethernet

Ethernet

VXLAN

802.1Q

802.3

802.1Q

IPv4 or IPv6 (tenant overlay)

TCP or UDP or SCTP, (transport layer)

802.3

Protocol conversion, Local bridging

ToRToRFabricSpineFabricServerServer

IPv4 or IPv6 (Fabric layer)

TCP

Ethernet

Ethernet

Ethernet

Ethernet

LACP

Ethernet

LACP

Ethernet

TCP

eBGP

eBGP

TCP

TCP

eBGP

eBGP

TCP

eBGP

TCP

eBGP

RINA-based DCN designOverall design (up), Fabric addressing plan (down) Simplifying multi-layer network management with RINA11

PtP DIFPtP DIFPtP DIFPtP DIF

PtP DIF

PtP DIF

PtP DIF

PtP DIF

DC Fabric DIFTenant DIFToRToRVMServerServerVMFabricFabricSpine

Models for the DCN fabric: IP vs RINAAssumption (for IP): all nodes NETCONF/YANG capableSimplifying multi-layer network management with RINA12ConceptIP RINAInterfacesIPv4 interfaces, need IP address (one per interface), unique in the layer. Port-ids to N-1 flows, just need port-id (locally device- unique identifier) Data Transfer protocol syntaxIPv4 syntax, TCP syntax (TCP is used by the control plane) EFCP (length of fields). Need address (one per device in the layer), unique in the layer Forwarding entityRouter, one per device in the layer, has FIB entries (forwarding table) Relaying and Multiplexing Task (RMT), one per device in the layer, has forwarding table entries. Forwarding strategyLongest prefix matching, ECMP Longest prefix matching, ECMP Scheduling strategyFIFO (needs max-queue size)FIFO (needs max-queue size)Routing protocolBGP with different routing policies. Needs AS numbers, router-id (IP address), neighbours IP addresses and AS numbers. CDAP with link-state routing policy and topological addressing Directory protocol-CDAP with centralized directory policy. Mgmt protocolNETCONFCDAPMgmt modelsyang-common-types, yang-interfaces, yang-ip, yang-routing , yang-bgp daf-common-mom, dif-common-mom, dif-default-policies

Configuration overhead: # of addresses in the DCN fabricIP. 2*number of interfaces in the DCN fabric (MAC @, IP @)RINA. 1*number of devices in the DCN fabric (IPCP @)Simplifying multi-layer network management with RINA13

Models for the tenant layers: IP vs RINA (I)Assumption (for IP): all nodes NETCONF/YANG capableSimplifying multi-layer network management with RINA14ConceptIP RINAInterfacesEthernet interfaces: need MAC address (one per interface)802.1q interfaces: need VLAN-idVTEP interfaces: need VXLAN-id, local IP address and UDP port, remote IP address and UDP portIPv4 interfaces: need IP address (one per interface), unique in tenant overlay Port-ids to N-1 flows, just need port-id (locally device- unique identifier) Data Transfer protocol syntaxIEEE 802.3 (Ethernet), IEEE 802.1q, IPv4, UDP, VXLAN, TCP EFCP (length of fields). Need address (one per device in the layer), unique in the layer Forwarding entityrouter: one per VMEthernet bridge: one per server per tenant overlay E-VRF: one per ToR per tenant overlay Relaying and Multiplexing Task (RMT), one per device in the layer, has forwarding table entries. Forwarding strategyExact (MAC) address matchingLongest prefix matching, ECMP (load-balancing/redundancy at server level) Scheduling strategyFIFO (needs max-queue size)FIFO (needs max-queue size)

Models for the tenant layers: IP vs RINA (II)Assumption (for IP): all nodes NETCONF/YANG capableSimplifying multi-layer network management with RINA15ConceptIP RINARouting protocolBGP with multi-protocol extensions. Needs route distinguisher and VPN targets CDAP with link-state routing policy and topological addressing Directory protocolDNS (resolve domain names of apps executing in the te

Recommended

View more >