Four IOV Fundamentals


Published on

Aprius solutions maximize application performance and minimize infrastructure costs in a data center by addressing network and storage I/O bottlenecks. The company offers a simple approach to provisioning and managing I/O resources by applying the principles of virtualization to server I/O including disk and flash storage, network and SAN interfaces. For additional information, please contact us at or visit

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Four IOV Fundamentals

  1. 1. The 4 Fundamentals of I/O Virtualization (IOV)<br />A<br />
  2. 2. 2<br />Server virtualization has led to the creation of other virtual resource types, including:<br />| CPU | Memory | Storage | I/O | Network |<br />I/O Virtualization (IOV)<br />The logical abstraction of server I/O (including network and SAN connections, direct-attached storage, coprocessor offload, video graphics, etc.) into many virtual resources, allowing for the balanced matching of I/O to physical and virtual servers.<br />27-Apr-10<br />
  3. 3. 3<br /> 4 Fundamentals of IOV<br />Maintain the Option of Choice<br />Be Ready to Scale<br />Make IOV an Extension of your Existing Infrastructure<br />Implement a New Data Center Mantra<br />27-Apr-10<br />
  4. 4. 4<br />1. Maintain the Option of Choice<br /><ul><li>Common method: assign I/O to a server by installing a card (typically via a PCI Express (PCIe) I/O slot)
  5. 5. Limits end-user I/O choice /application flexibility; increases overall app cost
  6. 6. An IOV system must present any I/O type to any server (physical or virtual)
  7. 7. Open, standards-based; flexibility controls quality, performance and operational costs</li></ul>27-Apr-10<br />
  8. 8. 5<br />2. Be Ready to Scale<br /><ul><li>Depending on number of servers (i.e. high-density blade or flexible rack-mount), IOV systems and pools must scale
  9. 9. I/O performance: coupled to servers and closely managed bandwidth, latency and policy requirements of the application; or
  10. 10. Share I/O resource pools across many servers using certain level of subscription.</li></ul>27-Apr-10<br />
  11. 11. 6<br />3. Make IOV an Extension of your Existing Infrastructure<br /><ul><li>IOV does not replace network access switches or change the configuration of network or SAN
  12. 12. IOV should accommodate direct server or network attachment modes:
  13. 13. Server-attached: ‘on-ramp’ to existing network and storage infrastructure
  14. 14. Network-attached: standards-based protocols provide I/O access over a common network and storage infrastructure</li></ul>CEE<br />Switch<br />Datacenter Fabric<br />(CEE)<br />Ethernet<br />I/O Resource Pool<br />SAN I/O<br />SAS/SATA<br />Video/GPU<br />Flash SSD<br />Utility I/O<br /> etc<br />27-Apr-10<br />
  15. 15. 7<br />4. Implement a New Data Center Mantra<br />MAKE, MONITOR, MANAGE and REPEAT<br /><ul><li>I/O must be actively managed by new rules, monitored for status and performance and provisioned on-demand.
  16. 16. IOV systems should also support prior management practices and processes.</li></ul>27-Apr-10<br />
  17. 17. 8<br />Aprius IOV Resources:<br /><ul><li>Learn about Aprius’ Technology Evaluation Platform
  18. 18. Aprius’ Interop Press Release
  19. 19. Aprius white paper “Four Fundamentals of I/O Virtualization”
  20. 20. Aprius on Twitter: @CraigAprius</li></ul>27-Apr-10<br />