1 / 18

On the Management of Virtual Networks

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. Agenda. Introduction of Network Virtualization Environments and its management.

stacy-crane
Télécharger la présentation

On the Management of Virtual Networks

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

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

  3. Network Virtualization Environments NVE enables diverse network architectures to coexist in a shared physical infrastructurewithout affecting each other. Creating a virtual version of computing systems to hide the physical characteristics of a computing platform from users, instead showing another abstract one. 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. Business relationships What will NVEs Change? + Virtualization Support • Network Devices Routers supporting multiple virtual routing tables, Programmable switches, etc. Cisco, Google, Huawei, etc. Traditional ISPs SPs Infrastructure Providers Service Providers InPs • Network Management 4

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

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

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

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

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

  10. Comparison of virtualization management proposals

  11. Comparison of virtualization management proposals Single management is not responsible for overseeing the management of InP

  12. Comparison of virtualization management proposals A centralized network performs all administrative Management actions in the infrastructure, such as resource discovery, provisioning, anduser control

  13. 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 Comparison of virtualization management proposals

  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.

  15. MANAGEMENT OF VIRTUALIZED CLOUD COMPUTING ENVIRONMENTS • Dynamic resource scaling: Dynamically 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

  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.

  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 awidely accept ofmanagement API

  18. Thank you

More Related