Policies
  • 19 Dec 2024
  • 2 Minutes to read
  • Dark
    Light

Policies

  • Dark
    Light

Article summary

Policies

Policies are templates for the guaranteed performance, resilience, and data governance of provisioned Volumes. You can create or modify your own Policies, or use one of the predefined policies.

Policies allow you to declare the desired characteristics of the volume that you wish to create. Policies are expressed in terms of volume performance and resiliency. Creating a volume automatically allocates and configures whatever is necessary to match these desired outcomes.

Policies can be performance optimized or capacity optimized:

  • Performance optimized policies eliminate any added layers that might affect the application data, providing best performance capabilities.

  • Capacity optimized policies use a more efficient data management and protection methods that provide optimization for the underlying capacity.

    Volumez uses capacity-saving methods (including compression, deduplication, erasure coding, and thin provisioning) where relevant, to consume the minimum amount of raw media. Using such methods might consume some CPU cycles and might reduce the performance of your volumes (it will still be within the performance range that you specified).

Predefined Policies:

Volumez offers four predefined policies.

You cannot modify them, but you can clone a predefined policy, and then modify and save the duplicate.

The predefined policies offer different trade-offs between resiliency and performance. Performance is optimized when nodes are located in the same geographic location. High resiliency can be achieved when each node is unaffected by any other, typically meaning a geographic distance exists between them. By fine-tuning these policies, you can find the right balance.

Zonal refers to the nodes being located across multiple zones. Regional means the nodes are in the same location.

The predefined policies are:

  • regional-standard-performance: The nodes are in the same geographic location.

  • regional-high-performance: The nodes are in the same geographic location. The policy is optimized for performance.

  • zonal-standard-performance: The nodes are across multiple zones. The policy is optimized for resiliency.

  • zonal-high-performance: The nodes are across multiple zones.

Policy Parameters that Can Be Changed for Active Volumes

When a policy is being utilized by an active volume, you can adjust the following parameters without disrupting the existing volume configuration:

Reserved Capacity (in percentage)

This parameter defines the portion of the total capacity reserved for the volume. Adjusting this value allows fine-tuning of resource allocation while ensuring the volume's operational stability.

Write Latency (microseconds)

Specifies the maximum acceptable write latency for the volume. Modifying this parameter enables the optimization of performance to align with workload requirements.

Read Latency (microseconds)

Indicates the maximum acceptable read latency for the volume. Changing this value helps achieve the desired read performance based on operational demands.

Require Disk Encryption

Determines whether disk-level encryption is mandatory for the volume. Updating this parameter ensures compliance with security and data protection policies.


Was this article helpful?

What's Next