Versions Compared

Old Version 19

changes.mady.by.user Bala Harish A(AC)

Saved on

compared with

New Version 20

changes.mady.by.user Anjali Tyagi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated "storage/bandwidth limit" row

...

  • Bandwidth: total of network bytes IN plus bytes OUT. Bytes IN refers to data sent from the client application to the front-side interface of the Gateway. Bytes OUT refers to data sent from the Gateway to the client application. These measures include the content body of the HTTP requests. Bandwidth from replication feeds are is included when a feed is routed through the Gateway. Bandwidth from Management API requests are not included.

  • Storage in use is one of two types: Raw and Logical. Raw storage refers to the actual amount of disk space used within the cluster based on the replication/EC factor for the objects. Logical storage refers to the summation of the objects’ Content-Length headers. One type is allowed per quota policy. 

...

Enable

The feature must be deliberately enabled for this scope, after which all required values must be entered to Save.

Storage Type

Choose to monitor storage usage by

  • Raw Storage (the total footprint on disk of all objects, replicas, segments, manifests)

  • Logical Storage (the sum of the uploaded content and any versions).

Storage/Bandwidth Limit

Limits are set in units of MB, GB, TB, or PB that they are multiplies of 1024.

Note

Bandwidth resets automatically based upon a calendar month: the first day of the month at 00:00:00 UTC. The status automatically changes to OK when a metric falls back within the allowed limit or resets for the new month. 

Actions

Consequences for exceeding a quota, from least restrictive to most:

  1. Notify Only: Sends notification but does not restrict any operations

  2. Read/Delete Only: Blocks operations that may increase storage (no writes, updates)

  3. Read Only: Blocks operations that change or add content (no writes, updates, deletes)

  4. Lockout: Blocks all operations

Override

Sets an alternate Action with an Expiration date as a temporary policy override, such as to grant a grace period for the client to resolve the overage. Overrides may impose a more restrictive Action than the policy, such as may be used if a tenant is delinquent in payments.

Email Notifications

Lists recipients of email notifications, who are notified when a limit is exceeded or is no longer exceeded. 

Every time an overage begins or ends, the Gateway sends an email to every address defined within the quota policy's notification email list. These notifications contain the scope, the metric’s name and limit, the time of detection, and the resulting quota state that now applies to the scope. The scope is identified as the tenant name, the domain name, or the domain + bucket name. Notifications are specific to the scope where the overage occurs. For example, if a tenant quota is exceeded, notifications do not cascade down to the people in the domain and bucket quotas within the tenant. Limits cascade to lower levels, but notifications do not.

...