1 / 8

Network Virtualization for the Future Internet Workshop Dagstuhl, Germany, Sept. 17-19, 2008

Management of Virtual Networks Breakout Group S. Baucke, L. Eggert, A. Feldmann, W. Kellerer, L. Mathy, S. Simon, M. Stiemerling. Network Virtualization for the Future Internet Workshop Dagstuhl, Germany, Sept. 17-19, 2008. Network Virtualization.

otis
Download Presentation

Network Virtualization for the Future Internet Workshop Dagstuhl, Germany, Sept. 17-19, 2008

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. Management of Virtual NetworksBreakout Group S. Baucke, L. Eggert, A. Feldmann, W. Kellerer, L. Mathy, S. Simon, M. Stiemerling Network Virtualization for the Future Internet Workshop Dagstuhl, Germany, Sept. 17-19, 2008

  2. Network Virtualization • History is repeated:single service physical networks \/Integrated services physical networks \/integrated networks (with single services) physical substrates simple management simple management

  3. How to manage a virtualized network? • Is there a gain in management (less cost)? • we believe so (divide and conquer) • How can we quantify this gain? • Difficult – through use cases • Different flavours of management possible depending on services/requirements • General: Demand for simple service or platform deployment needed requires better management technologies  e.g., VPNs, ease of trial with a limited number of customers,...

  4. 3 levels of management • Virtual Network  VN operator • VN topology  VN provider • Substrate  Infrastructure provider • Note: for a business role any combination of roles is possible

  5. VN Operator • routing, traffic engineering • configuration • user/application authentification • fault management (not always neccessary) • encryption/security (if you do not trust) • needs: statistics per VN entity, counters, router ressources usage, fault notifications What is different from today's ISP? • Cost benefit: virtualized resource not hardware resources • no hw maintenance • flexibility (on a per hour/month basis) • simpler configuration: a virtual network will be for a special task: management of a phone network is easier than for IP  abstraction for networks • Need for a network description language • potential to get global coverage • virtual networks for debugging • user needs to have a VMware and has to install a certain image, this cannot be guaranteed today

  6. Layer of indirection for hardware, money VN provider Provides a VN topology • planning of VN • negotiation and renegotiation • Layer of abstraction on the management interfaces: access to the console of VN entities provided by IFP • provide consoles to VNO • resources pooling • move network • needs access to statistics • What is different from today's ISP (acting as VPN providers)? • Cost benefit: virtualized resource not hardware resources • No hardware maintenance • flexibility (on a per hour/month basis)

  7. Infrastructure provider • VN description – mapping ---> infrastructure • plan infrastructure (monthly basis) • provide consoles to VNP • HW maintenance • needs • access to statistics • watch dogs • What is different from today's ISP (owning a network hardware)? • Centralized network resource management • Database of record • Allow for optimization • Manage networks not elements • Enable movement of network entities ( power consumption)

  8. (3 most) important research issues • Abstraction of networks: Network description language • Management abstraction: parameters available between each level • How to provide access to management interfaces • Infrastructure provider: • Mapping of descriptions to infrastructure • Movement of VN entities • VN debugging (on all levels) • Statistics on each level of abstraction • Problem of divide & conquer: map a fault to a certain level • Problem of separated control loops

More Related