81
Monitoring a virtual network infrastructure summary of the paper in Computer Communication Review Nov. 2010 DOI:10.1145/1880153.1880161 Augusto Ciuffoletti 24 gennaio 2012

Monitoring a virtual network infrastructure - An IaaS perspective

Embed Size (px)

Citation preview

Page 1: Monitoring a virtual network infrastructure - An IaaS perspective

Monitoring a virtual network infrastructuresummary of the paper in Computer Communication Review

Nov. 2010DOI:10.1145/1880153.1880161

Augusto Ciuffoletti

24 gennaio 2012

Page 2: Monitoring a virtual network infrastructure - An IaaS perspective

Provisioning networking for an IaaS infrastructure

• The IaaS approach has been initially aimed mainly atstorage/computing resources

• Technology is ready to support the provision of networkresources as well

• There is demand for composite networking infrastructures(like Grids)

• However IaaS providers still offer flat LANs• We claim that the problem is in the interface between user

and provider

Page 3: Monitoring a virtual network infrastructure - An IaaS perspective

Provisioning networking for an IaaS infrastructure

• The IaaS approach has been initially aimed mainly atstorage/computing resources

• Technology is ready to support the provision of networkresources as well

• There is demand for composite networking infrastructures(like Grids)

• However IaaS providers still offer flat LANs• We claim that the problem is in the interface between user

and provider

Page 4: Monitoring a virtual network infrastructure - An IaaS perspective

Provisioning networking for an IaaS infrastructure

• The IaaS approach has been initially aimed mainly atstorage/computing resources

• Technology is ready to support the provision of networkresources as well

• There is demand for composite networking infrastructures(like Grids)

• However IaaS providers still offer flat LANs• We claim that the problem is in the interface between user

and provider

Page 5: Monitoring a virtual network infrastructure - An IaaS perspective

Provisioning networking for an IaaS infrastructure

• The IaaS approach has been initially aimed mainly atstorage/computing resources

• Technology is ready to support the provision of networkresources as well

• There is demand for composite networking infrastructures(like Grids)

• However IaaS providers still offer flat LANs

• We claim that the problem is in the interface between userand provider

Page 6: Monitoring a virtual network infrastructure - An IaaS perspective

Provisioning networking for an IaaS infrastructure

• The IaaS approach has been initially aimed mainly atstorage/computing resources

• Technology is ready to support the provision of networkresources as well

• There is demand for composite networking infrastructures(like Grids)

• However IaaS providers still offer flat LANs• We claim that the problem is in the interface between user

and provider

Page 7: Monitoring a virtual network infrastructure - An IaaS perspective

Why IaaS networking is difficult

• It is more difficult to describe a network than a host

• Quite evident: (topology, technology, throughput) versussingle option (small, medium, large)

• Monitoring and controlling the network is more complex• Less evident: explaining why and how to cope with is the

topic of the paper

Page 8: Monitoring a virtual network infrastructure - An IaaS perspective

Why IaaS networking is difficult

• It is more difficult to describe a network than a host• Quite evident: (topology, technology, throughput) versus

single option (small, medium, large)

• Monitoring and controlling the network is more complex• Less evident: explaining why and how to cope with is the

topic of the paper

Page 9: Monitoring a virtual network infrastructure - An IaaS perspective

Why IaaS networking is difficult

• It is more difficult to describe a network than a host• Quite evident: (topology, technology, throughput) versus

single option (small, medium, large)• Monitoring and controlling the network is more complex

• Less evident: explaining why and how to cope with is thetopic of the paper

Page 10: Monitoring a virtual network infrastructure - An IaaS perspective

Why IaaS networking is difficult

• It is more difficult to describe a network than a host• Quite evident: (topology, technology, throughput) versus

single option (small, medium, large)• Monitoring and controlling the network is more complex• Less evident: explaining why and how to cope with is the

topic of the paper

Page 11: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)

• This technology is mature and available OTS• Implements an ethernet LAN over an arbitrary (bridged)

topology• Frames (layer 2) labeled with a virtual network identifier (VNI)• Bridges route labeled frames across ports based on a VNI• The same port can be associated with multiple VNI

Page 12: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)• This technology is mature and available OTS

• Implements an ethernet LAN over an arbitrary (bridged)topology

• Frames (layer 2) labeled with a virtual network identifier (VNI)• Bridges route labeled frames across ports based on a VNI• The same port can be associated with multiple VNI

Page 13: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)• This technology is mature and available OTS• Implements an ethernet LAN over an arbitrary (bridged)

topology

• Frames (layer 2) labeled with a virtual network identifier (VNI)• Bridges route labeled frames across ports based on a VNI• The same port can be associated with multiple VNI

Page 14: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)• This technology is mature and available OTS• Implements an ethernet LAN over an arbitrary (bridged)

topology• Frames (layer 2) labeled with a virtual network identifier (VNI)

• Bridges route labeled frames across ports based on a VNI• The same port can be associated with multiple VNI

Page 15: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)• This technology is mature and available OTS• Implements an ethernet LAN over an arbitrary (bridged)

topology• Frames (layer 2) labeled with a virtual network identifier (VNI)• Bridges route labeled frames across ports based on a VNI

• The same port can be associated with multiple VNI

Page 16: Monitoring a virtual network infrastructure - An IaaS perspective

How to implement a network in the cloud

• The key technology is the virtual bridge (IEEE802.1Q)• This technology is mature and available OTS• Implements an ethernet LAN over an arbitrary (bridged)

topology• Frames (layer 2) labeled with a virtual network identifier (VNI)• Bridges route labeled frames across ports based on a VNI• The same port can be associated with multiple VNI

Page 17: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• An enterprise in a 3 floor building

• Logistics motivate a per floor cabling (left)

Page 18: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• An enterprise in a 3 floor building• Logistics motivate a per floor cabling (left)

Page 19: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• Usual bridges force network topology to follow logistics

• Instead enterprise organization might prefer a differentarrangement...

Page 20: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• Usual bridges force network topology to follow logistics• Instead enterprise organization might prefer a different

arrangement...

Page 21: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• Enterprise might prefer separate networks for desktops(VLAN1), printers (VLAN2) and archive (VLAN3)

• Each having an interface on each floor

Page 22: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• Enterprise might prefer separate networks for desktops(VLAN1), printers (VLAN2) and archive (VLAN3)

• Each having an interface on each floor

Page 23: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• The introduction of IEEE802.1Q bridges solves theproblem (right)

• Virtual LANs span across floors• Frames do not leak outside each VLAN (security)

Page 24: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• The introduction of IEEE802.1Q bridges solves theproblem (right)

• Virtual LANs span across floors

• Frames do not leak outside each VLAN (security)

Page 25: Monitoring a virtual network infrastructure - An IaaS perspective

Example

• The introduction of IEEE802.1Q bridges solves theproblem (right)

• Virtual LANs span across floors• Frames do not leak outside each VLAN (security)

Page 26: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 27: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 28: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN

• Routing through the provider infrastructure is transparent tothe user

• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 29: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user

• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 30: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user• Frames are confined within user’s virtual infrastructure

• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 31: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2

• Virtual networks can be dynamically configured using aspanning tree protocol

Page 32: Monitoring a virtual network infrastructure - An IaaS perspective

Bridging virtual hosts

• Inside a IaaS cloud, a real host in a data-centre implementsseveral virtual hosts

• An internal software bridge splits communication acrossvirtual TAP interfaces

• Virtual hosts appear as sharing a LAN• Routing through the provider infrastructure is transparent to

the user• Frames are confined within user’s virtual infrastructure• Frame routing is efficiently managed at layer 2• Virtual networks can be dynamically configured using a

spanning tree protocol

Page 33: Monitoring a virtual network infrastructure - An IaaS perspective

Network monitoring (in the age of the cloud)

• The user needs to monitor the performance of the network

• One basic need is load balancing• Network load is not covered by ordinary load balancing

services• In a composite network (not a 2-tiers WS), the provider

cannot anticipate what part of the network is under stress at acertain time

Page 34: Monitoring a virtual network infrastructure - An IaaS perspective

Network monitoring (in the age of the cloud)

• The user needs to monitor the performance of the network• One basic need is load balancing

• Network load is not covered by ordinary load balancingservices

• In a composite network (not a 2-tiers WS), the providercannot anticipate what part of the network is under stress at acertain time

Page 35: Monitoring a virtual network infrastructure - An IaaS perspective

Network monitoring (in the age of the cloud)

• The user needs to monitor the performance of the network• One basic need is load balancing• Network load is not covered by ordinary load balancing

services

• In a composite network (not a 2-tiers WS), the providercannot anticipate what part of the network is under stress at acertain time

Page 36: Monitoring a virtual network infrastructure - An IaaS perspective

Network monitoring (in the age of the cloud)

• The user needs to monitor the performance of the network• One basic need is load balancing• Network load is not covered by ordinary load balancing

services• In a composite network (not a 2-tiers WS), the provider

cannot anticipate what part of the network is under stress at acertain time

Page 37: Monitoring a virtual network infrastructure - An IaaS perspective

Example: Grid in the Cloud

• Depending on processing phase, different links areunder stress

Page 38: Monitoring a virtual network infrastructure - An IaaS perspective

Example: Grid in the Cloud

• Collection of experimental data: Data acquisition toStorage

Page 39: Monitoring a virtual network infrastructure - An IaaS perspective

Example: Grid in the Cloud

• Data retrieval: Storage to Web Server

Page 40: Monitoring a virtual network infrastructure - An IaaS perspective

Example: Grid in the Cloud

• Data processing: Storage to Computing resources

Page 41: Monitoring a virtual network infrastructure - An IaaS perspective

User configurable monitoring

• Under such circumstances, network monitoring requestscannot be anticipated by the provider

• The network monitoring activity should be dynamicallyconfigured by the user

• Configuration requires access to real and virtual networkinterfaces and to switching devices

• The provider wants to maintain control over these devices

Page 42: Monitoring a virtual network infrastructure - An IaaS perspective

User configurable monitoring

• Under such circumstances, network monitoring requestscannot be anticipated by the provider

• The network monitoring activity should be dynamicallyconfigured by the user

• Configuration requires access to real and virtual networkinterfaces and to switching devices

• The provider wants to maintain control over these devices

Page 43: Monitoring a virtual network infrastructure - An IaaS perspective

User configurable monitoring

• Under such circumstances, network monitoring requestscannot be anticipated by the provider

• The network monitoring activity should be dynamicallyconfigured by the user

• Configuration requires access to real and virtual networkinterfaces and to switching devices

• The provider wants to maintain control over these devices

Page 44: Monitoring a virtual network infrastructure - An IaaS perspective

User configurable monitoring

• Under such circumstances, network monitoring requestscannot be anticipated by the provider

• The network monitoring activity should be dynamicallyconfigured by the user

• Configuration requires access to real and virtual networkinterfaces and to switching devices

• The provider wants to maintain control over these devices

Page 45: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring proxy

• A proxy interacts with the user willing to implement networkmonitoring

• A network of proxies covers the complex networkinginfrastructure of the provider

• The proxy configures network probes so that they are ready torespond to user requests in the expected way

• A proxy has an authority that may be limited to a part of theprovider infrastructure

Page 46: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring proxy

• A proxy interacts with the user willing to implement networkmonitoring

• A network of proxies covers the complex networkinginfrastructure of the provider

• The proxy configures network probes so that they are ready torespond to user requests in the expected way

• A proxy has an authority that may be limited to a part of theprovider infrastructure

Page 47: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring proxy

• A proxy interacts with the user willing to implement networkmonitoring

• A network of proxies covers the complex networkinginfrastructure of the provider

• The proxy configures network probes so that they are ready torespond to user requests in the expected way

• A proxy has an authority that may be limited to a part of theprovider infrastructure

Page 48: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring proxy

• A proxy interacts with the user willing to implement networkmonitoring

• A network of proxies covers the complex networkinginfrastructure of the provider

• The proxy configures network probes so that they are ready torespond to user requests in the expected way

• A proxy has an authority that may be limited to a part of theprovider infrastructure

Page 49: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring interface

• An interface must be provided between the user applicationand the proxy

• The interface should inform the user about relevant changesin the virtual topology

• The interface has the effect of restricting the authority of auser controlled sensor to owned traffic trunks

• The interface may be implemted using tools like SOAP,possibly embedded in a Enterprise System Bus

• For performance reasons the same interface is not used totransfer streams of sensor results

Page 50: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring interface

• An interface must be provided between the user applicationand the proxy

• The interface should inform the user about relevant changesin the virtual topology

• The interface has the effect of restricting the authority of auser controlled sensor to owned traffic trunks

• The interface may be implemted using tools like SOAP,possibly embedded in a Enterprise System Bus

• For performance reasons the same interface is not used totransfer streams of sensor results

Page 51: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring interface

• An interface must be provided between the user applicationand the proxy

• The interface should inform the user about relevant changesin the virtual topology

• The interface has the effect of restricting the authority of auser controlled sensor to owned traffic trunks

• The interface may be implemted using tools like SOAP,possibly embedded in a Enterprise System Bus

• For performance reasons the same interface is not used totransfer streams of sensor results

Page 52: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring interface

• An interface must be provided between the user applicationand the proxy

• The interface should inform the user about relevant changesin the virtual topology

• The interface has the effect of restricting the authority of auser controlled sensor to owned traffic trunks

• The interface may be implemted using tools like SOAP,possibly embedded in a Enterprise System Bus

• For performance reasons the same interface is not used totransfer streams of sensor results

Page 53: Monitoring a virtual network infrastructure - An IaaS perspective

The network monitoring interface

• An interface must be provided between the user applicationand the proxy

• The interface should inform the user about relevant changesin the virtual topology

• The interface has the effect of restricting the authority of auser controlled sensor to owned traffic trunks

• The interface may be implemted using tools like SOAP,possibly embedded in a Enterprise System Bus

• For performance reasons the same interface is not used totransfer streams of sensor results

Page 54: Monitoring a virtual network infrastructure - An IaaS perspective

Data streaming

• Data are treated as a stream flowing from the sensor to theuser

• The stream may be encoded for security purposes• The stream may travel using owned traffic trunks

Page 55: Monitoring a virtual network infrastructure - An IaaS perspective

Data streaming

• Data are treated as a stream flowing from the sensor to theuser

• The stream may be encoded for security purposes

• The stream may travel using owned traffic trunks

Page 56: Monitoring a virtual network infrastructure - An IaaS perspective

Data streaming

• Data are treated as a stream flowing from the sensor to theuser

• The stream may be encoded for security purposes• The stream may travel using owned traffic trunks

Page 57: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management

• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 58: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools

• Dynamic control of sensors• Fully deployed• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 59: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors

• Fully deployed• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 60: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed

• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 61: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed• BUT

• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 62: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed• BUT• Monitoring controlled by Grid Admin

• Data stored in SQL repositories and retrieved to users

Page 63: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Page 64: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: Monalisa

• Distributed infrastructure management• Glues together diverse monitoring tools• Dynamic control of sensors• Fully deployed• BUT• Monitoring controlled by Grid Admin• Data stored in SQL repositories and retrieved to users

Rigid, hardly scalable

Page 65: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management

• Glues together diverse monitoring tools• Sensors are controlled by user application• Monitoring sessions activated on demand• Data returned to the user with an UDP stream• BUT• only a proof of concept implementation

Page 66: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools

• Sensors are controlled by user application• Monitoring sessions activated on demand• Data returned to the user with an UDP stream• BUT• only a proof of concept implementation

Page 67: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools• Sensors are controlled by user application

• Monitoring sessions activated on demand• Data returned to the user with an UDP stream• BUT• only a proof of concept implementation

Page 68: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools• Sensors are controlled by user application• Monitoring sessions activated on demand

• Data returned to the user with an UDP stream• BUT• only a proof of concept implementation

Page 69: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools• Sensors are controlled by user application• Monitoring sessions activated on demand• Data returned to the user with an UDP stream

• BUT• only a proof of concept implementation

Page 70: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools• Sensors are controlled by user application• Monitoring sessions activated on demand• Data returned to the user with an UDP stream• BUT

• only a proof of concept implementation

Page 71: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Distributed infrastructure management• Glues together diverse monitoring tools• Sensors are controlled by user application• Monitoring sessions activated on demand• Data returned to the user with an UDP stream• BUT• only a proof of concept implementation

Page 72: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Host A issues a network monitoring request (e.g.,bandwidth from X to Y)...

• that is taken in charge by the proxy in A’s domain...

Page 73: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• Host A issues a network monitoring request (e.g.,bandwidth from X to Y)...

• that is taken in charge by the proxy in A’s domain...

Page 74: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• that has authority to control a relevant sensor (agent ingd2 terms)...

• and data are returned to the originating host as astream.

Page 75: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

• that has authority to control a relevant sensor (agent ingd2 terms)...

• and data are returned to the originating host as astream.

Page 76: Monitoring a virtual network infrastructure - An IaaS perspective

Grid legacy: GD2

In principle this might be implemented in a virtualinfrastructure, using virtual components

Page 77: Monitoring a virtual network infrastructure - An IaaS perspective

Conclusions

• the techniques for complex networks in the cloud are availableOTS

• the hard issue is the control of the virtual network• network monitoring must be translated from virtual to real

(and back)• an effective infrastructure takes into accout multi-domain use

cases for scalability

Page 78: Monitoring a virtual network infrastructure - An IaaS perspective

Conclusions

• the techniques for complex networks in the cloud are availableOTS

• the hard issue is the control of the virtual network

• network monitoring must be translated from virtual to real(and back)

• an effective infrastructure takes into accout multi-domain usecases for scalability

Page 79: Monitoring a virtual network infrastructure - An IaaS perspective

Conclusions

• the techniques for complex networks in the cloud are availableOTS

• the hard issue is the control of the virtual network• network monitoring must be translated from virtual to real

(and back)

• an effective infrastructure takes into accout multi-domain usecases for scalability

Page 80: Monitoring a virtual network infrastructure - An IaaS perspective

Conclusions

• the techniques for complex networks in the cloud are availableOTS

• the hard issue is the control of the virtual network• network monitoring must be translated from virtual to real

(and back)• an effective infrastructure takes into accout multi-domain use

cases for scalability

Page 81: Monitoring a virtual network infrastructure - An IaaS perspective

Thank you!

Full reference:Augusto Ciuffoletti. Monitoring a virtual network infrastructure: an IaaSperspective. SIGCOMM Comput. Commun. Rev. 40, 5 47-52.DOI=10.1145/1880153.1880161http://doi.acm.org/10.1145/1880153.1880161

Download published version

Download preliminary version