Blog


November 10, 2015


Quality of Service (QoS) is one of the fundamental constructs behind ioFABRIC Vicinity. Vicinity was developed to deliver application-specific service levels, continuously adapting to meet individual application’s needs, even when infrastructure and workloads change. Performance characteristics, capacity management, and data protection levels are the main functions that Vicinity controls and automates.

Today, I want to dive a little more deeply into Vicinity’s QoS policies. Vicinity has a centralized dashboard that allows administrators to define and set these policies for individual applications or groups of applications. After setting these service level objectives – this big, this fast, this protected – Vicinity automatically orchestrates the storage infrastructure to enforce those levels. Vicinity can assign the right types of storage, aligned with the right network, to individual applications or sets of applications. This ensures that the right CPU/memory resources are allocated in the hypervisor. QoS-driven automation significantly reduces storage OPEX and improves business agility through consistent performance, decreased risk, near zero manual intervention and downtime.

Vicinity’s QoS-driven storage automation controls performance, capacity, and protection levels:

  • Performance settings allow you to define the minimum, maximum, and target for IOPS, latency, and bandwidth on a per-application basis.
  • Capacity settings allow you to combine multiple kinds of storage to achieve different capacity and performance requirements – high-performance media for fast access, inexpensive capacity media for stale data.
  • Data protection options like replication, snapshots, and clones can be set for each application or group of applications, depending on the level of availability required.

In the case of a production database that is in constant use, Vicinity can maintain two or more synchronous replicas of the data, seamlessly recovering from any device, cabling/path, or power failure. However, a background Hadoop task may require less stringent protection, so Vicinity may maintain only one replica on archive media. Should that application suddenly require continuous access and uptime, Vicinity can change its level of protection and automatically migrate data to faster storage.

Vicinity intelligently monitors and adapts to physical infrastructure changes too. Let’s say you add some flash. Vicinity will automatically migrate performance-starved data to it, without any manual intervention. No migration projects, no headaches – and it all happens seamlessly while the applications are running.

Vicinity’s QoS-driven automation drastically reduces the largest storage budget item, OPEX. To hear more about Vicinity’s technical features, or join our beta program, or partner with ioFABRIC, send us a message at info@iofabric.com.

Back to top
[gravityform id="47" title="false" description="false" tabindex="20"]
[gravityform id="46" title="false" description="false" tabindex="50"]
[gravityform id="39" title="false" description="false" tabindex="50"]
[gravityform id="19" title="false" description="false" tabindex="10"]
[gravityform id="37" title="false" description="false" tabindex="50"]