Resource Type: netapp_quota

Defined in:

lib/puppet/type/netapp_quota.rb

Providers:

cmode
sevenmode

Overview

Manage NetApp quota entries. Please note that NetApp identifies a quota entry uniquely by the type, target, volume, and qtree. This type on the other hand has to uniquely identify a quota entry only by its target. This means that you cannot manage two quota entries for the same user (username = quota-target) but for different trees. As a result this type is best at managing tree quotas

Example:

Limit ‘qtree1` on `vol1` to 10G

   netapp_quota { '/vol/vol1/qtree1':
     ensure    => present,
     type      => tree,
     volume    => 'vol1',
     disklimit => '10G',
   }

Limit user bob to consume 2G on qtree1. Note that you cannot
define multiple quotas for user bob:

    netapp_quota { 'bob':
      ensure    => present,
      type      => user,
      qtree     => 'qtree1',
      volume    => 'vol1',
      disklimit => '2048M',
    }

Make sure the following restrictions apply in your
environment before using this type:
- every quota target has to be unique
- quota entries must not contain any special characters that would
  require quotation

Properties

• disklimit

  The amount of space that the target can consume, e.g. ‘100M` or `2G`. You can also specify absent to make sure there is no limit.

  Supported values:

  • absent
  • /^[0-9]+[KMGT]$/i
• ensure (defaults to: present)

  The basic property that the resource should be in.

  Supported values:

  • present
  • absent
• filelimit

  The number of files that the target can have. You can also specify absent to make sure there is no limit.

  Supported values:

  • absent
  • /^[0-9]+[KMGT]?$/i
• qtree

  The qtree that the quota resides on. This is only relevant for ‘user` and `group` quotas

• softdisklimit

  The amount of space the target has to consume before a message is logged. You can also specify absent to make sure there is no limit.

  Supported values:

  • absent
  • /^[0-9]+[KMGT]$/i
• softfilelimit

  The number of files the target has to own before a message is logged. You can also specify absent to make sure there is no limit

  Supported values:

  • absent
  • /^[0-9]+[KMGT]?$/i
• threshold

  The amount of disk space the target has to consume before a message is logged. Set to absent to make sure the treshold is unlimited

  Supported values:

  • absent
  • /^[0-9]+[KMGT]$/i
• type

  The type of the quota. You can define ‘tree`, `user` or `group` here

  Supported values:

  • tree
  • user
  • group
• volume

  The name of the volume the quota resides on

  Supported values:

  • /^\w+$/

Parameters

• name (namevar)

  The name of the quota target. Depending on the quota type this can be a pathname (e.g. ‘/vol/vol1/qtree1`), a username, or a group

• provider

  The specific backend to use for this ‘netapp_quota` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.