1 / 8

Four IOV Fundamentals

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 info@aprius.com or visit www.aprius.com.

Aprius
Download Presentation

Four IOV Fundamentals

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. The 4 Fundamentals of I/O Virtualization (IOV) A

  2. Server virtualization has led to the creation of other virtual resource types, including: • | CPU | Memory | Storage | I/O | Network | I/O Virtualization (IOV) 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.

  3. 4 Fundamentals of IOV Maintain the Option of Choice Be Ready to Scale Make IOV an Extension of your Existing Infrastructure Implement a New Data Center Mantra

  4. 1. Maintain the Option of Choice • Common method: assign I/O to a server by installing a card (typically via a PCI Express (PCIe) I/O slot) • Limits end-user I/O choice /application flexibility; increases overall app cost • An IOV system must present any I/O type to any server (physical or virtual) • Open, standards-based; flexibility controls quality, performance and operational costs

  5. 2. Be Ready to Scale • Depending on number of servers (i.e. high-density blade or flexible rack-mount), IOV systems and pools must scale • I/O performance: coupled to servers and closely managed bandwidth, latency and policy requirements of the application; or • Share I/O resource pools across many servers using certain level of subscription.

  6. 3. Make IOV an Extension of your Existing Infrastructure • IOV does not replace network access switches or change the configuration of network or SAN • IOV should accommodate direct server or network attachment modes: • Server-attached: ‘on-ramp’ to existing network and storage infrastructure • Network-attached: standards-based protocols provide I/O access over a common network and storage infrastructure CEE Switch • Datacenter Fabric • (CEE) Ethernet I/O Resource Pool SAN I/O SAS/SATA Video/GPU Flash SSD Utility I/O etc

  7. 4. Implement a New Data Center Mantra • MAKE, MONITOR, MANAGE and REPEAT • I/O must be actively managed by new rules, monitored for status and performance and provisioned on-demand. • IOV systems should also support prior management practices and processes.

  8. Aprius IOV Resources: • Learn about Aprius’ Technology Evaluation Platform • Aprius’ Interop Press Release • Aprius white paper “Four Fundamentals of I/O Virtualization” • Aprius on Twitter: @CraigAprius

More Related