| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Design and apply precise policies for where and how to apply protections in the implementation to make the fullest use of the rich content protection features of Swarm. Policies define how the data being uploaded to the Swarm cluster is stored, managed, and protected.
How it
...
Works
Cluster-level policies reside in configuration settings and allows allow defining cluster-wide and cluster-specific policies for how Swarm implements the content protection features (see See Configuring Cluster Policies). These baseline cluster policies can be layered with context-level (domain and bucket) policies, which reside in designated headers in the context objects themselves. Policies are not lifepoints: they not lifepoints (Lifepoint Metadata Headers): They do not have built-in lifetimes, nor do they specify transitions from one policy to another over time. Policies are only changed by explicit updates.
Types of
...
Content Policies
Policies can be set for these content protection options, specific to the context needed:
...
How many default, minimum, and maximum number of replicas to keep for the objects in this cluster/domain/bucket
...
-
...
Whether to enable or specify the EC encoding (
k:p) to use for the objects in this cluster/domain/bucket
...
-
...
Whether to enable, disable, or suspend versioning for the objects in this cluster/domain/bucket
These appear under the bucket or domain's Properties (gear) tab, Storage Policies section in the Content UI:
...
How
...
Policies Resolve
Swarm begins policy evaluation by eliminating contexts (domain and bucket) not applicable to resolving overlapping policies for one of two reasons:
...
Swarm (1) selects the anchored policy if it exists, or else (2) checks the relevant contexts from the bottom up and selects the first policy it finds.
...
Note
Within a given request to a context (domain or bucket) object, if more than one policy header of the same type is written, the last one written is honored.
Setting
...
Policies by
...
Cluster
Cluster-specific policies for domains and buckets can be set by including the cluster name parenthetically and separating them with a comma. Swarm looks for and takes any cluster-specific policy values, using the default value only if it finds no match.
...
| Code Block |
|---|
Policy-{feature}: enabled (myCluster), disabled (myRemote), disabled
or
Policy-{feature}: enabled (myCluster), disabled
|
| Info |
|---|
RequiredAlways end a multi-part policy with the preferred default value. |
Updating
...
Policies
Swarm cluster policies are all persisted settingsall Persisted Settings (SNMP), so use the snmpset command on the cluster's settings object to change and persist the policies cluster-wide. Domain and bucket policies are saved as headers on those objects.
See See Using SNMP with Swarm.