1. On the Management of Virtual Networks Group 3 Yang Wenzhi 3474953 Wang Qian 3430773 Issam Alkindi 3444783 Zhu Guangjin 3440223 Zhang Haifeng 3392273 Sanjeev Maharjan3480473 1

2. Agenda  Introduction of Network Virtualization Environments and its management  Initiatives for the Management of NVEs  Research Perspectives  Conclusion 2

3. Network Virtualization Environments Creating a virtual version of computing systems to hide the physical characteristics of a computing platform from users, instead showing another abstract one. NVE enables diverse network architectures to coexist in a shared physical infrastructure without affecting each other. Why Network Virtualization Environments? ● Energy Consumption ● Easily Controlled and Inspected (C) ● Provisioned as Needed (P) ● Easily Relocated (S) ● Disaster Recovery (F) Effective & Reliable 3

4. What will NVEs Change? Network Devices Network Devices Business relationships Business relationships + Virtualization Support Routers supporting multiple virtual routing tables, Programmable switches, etc. Cisco, Google, Huawei, etc. Infrastructure Providers Service Providers Network Management Network Management Traditional ISPs InPs SPs 4

5. Management of Network Virtualization Environments InPs : Providing virtual networks & Monitorin g physical resources SPs : Operating virtual networks & Providing services to end users SPs lease resources from different InPs Manually Automatically Virtual Nodes: Hypervisor Virtual Links: VLANs, MPLS, LSPs, GRE tunnels Isolated in a physical one Operated by different SPs 5

6. Management Targets Management Functions Management Approaches NVEs Managed components of NVE which belong to different layers. How network management has been tackled by network virtualization projects. Vary in how managers and agents are organized. 6

7. Mngt Targets node link network operation of virtual and physical nodes, i.e. initial creation& node migration configuration and operation of physical and virtual links, i.e. link isolation &flow scheduling. entire virtual network including those span multiple physical networks 7

8. Supports several other management tasks, such as fault management and billing. Mngt Functions Allows SPs to instantiate and use virtual networks. Defines how management applications communicate with NVE resources and enabling interoperability. Provisioning Monitoring Interfacing 8

9. Autonomic * Reduce human intervention and allows dynamic adaption to changes in the network Mngt Approaches Policy-based * enforce isolation among virtual networks by controlling access permissions for each SP Centralized * Responsible for performing all management tasks Distributed * Multiple nodes cooperate to accomplish the mngt tasks 9

10. Comparison of virtualization management proposals Characteristi c Management targetManagement functionManagement approach Project/ proposal NodeLinkNetworkProvisionin g MonitoringInterfacingCentralizedDistributedAutonomic 4WARD AUTOI FEDERICA ProtoGENI UCLP VNARMS OpenFlow/ FlowVisor 10

11. Comparison of virtualization management proposals Characteristi c Management targetManagement functionManagement approach Project/ proposal NodeLinkNetworkProvisionin g MonitoringInterfacingCentralizedDistributedAutonomic 4WARD AUTOI FEDERICA ProtoGENI UCLP VNARMS OpenFlow/ FlowVisor Single management is not responsible for overseeing the management of InP 11

12. Comparison of virtualization management proposals Characteristi c Management targetManagement functionManagement approach Project/ proposal NodeLinkNetworkProvisionin g MonitoringInterfacingCentralizedDistributedAutonomic 4WARD AUTOI FEDERICA ProtoGENI UCLP VNARMS OpenFlow/ FlowVisor A centralized network performs all administrative Management actions in the infrastructure, such as resource discovery, provisioning, and user control 12

13. Comparison of virtualization management proposals Characteristi c Management targetManagement functionManagement approach Project/ proposal NodeLinkNetworkProvisionin g MonitoringInterfacingCentralizedDistributedAutonomic 4WARD AUTOI FEDERICA ProtoGENI UCLP VNARMS OpenFlow/ FlowVisor A switch can be probably sliced and allocated to different users. One issue that FlowVisor has to deal with is managing isolation among multiple slices 13

14. Research perspectives FEDERATIONS AND SLA NEGOTIATIONS enables access to larger-scale infrastructures(eg,protoGENI) Future: guaranteeing performance for participating entities through SLA. INTERPLAY BETWEEN INP MANAGEMENT AND SP MANAGEMENT cooperation to avoid conflicts, ensure stability. Future: INP:maximize the utilization of infrastructures, revenue SP:want predictable performance for virtual networks. 14

15. MANAGEMENT OF VIRTUALIZED CLOUD COMPUTING ENVIRONMENTS  Dynamic resource scaling: D ynamically modifying a previous resource allocation Nowadays: provide elasticity at the virtual machine level. Future: dynamic capacity adjustment of network resources (e.g.,bandwidth) requires further investigation.  Application-aware resource provisioning: characteristics of the applications are commonly ignored Future: Adaptive application-driven resource provisioning 15

16.  Energy management a significant portion of the operational costs of the InP Solutions: consolidating virtual resources into a small number of physical devices. Future: a good trade-off between energy consumption and applications' performance  Data center network management address configuration, traffic management,and flow scheduling. 16

17. MANAGEMENT OF SDNS separation of control and data planes and their implementation in software offer flexibility in controlling how network devices forward packet Management abstractions: current solution to sdns : require network operators to develop customized management packages using low-level instructions of a network operating system e.g., NOX Future :some adequate interfaces, protocols,OMNI system Interoperability and management API: SDNs can be deployed using virtualized forwarding resources from different providers using a variety of network operating systems and implementations. Future: stresses a need of a widely accept of management API 17

18. Thank you 18