Cinder Solidfire

Learn about configurations >

• allow-template-caching | boolean

  Create an internal cache of copy of images when a bootable volume is created to eliminate fetch from glance and qemu-conversion on subsequent calls.

• allow-tenant-qos | boolean

  Allow tenants to specify QOS on create

• api-port | int

  SolidFire API port. Useful if the device api is behind a proxy on a different port.

• emulate-512 | boolean

  Set 512 byte emulation on volume creation

• enable-vag | boolean

  Utilize volume access groups on a per-tenant basis.

• enable-volume-mapping | boolean

  Create an internal mapping of volume IDs and account. Optimizes lookups and performance at the expense of memory, very large deployments may want to consider setting to False.

• san-ip | string

  IP address of SAN controller

• san-login | string

  Default: sfadmin

  Username for SAN controller

• san-password | string

  Default: sfpassword

  Password for SAN controller

• svip | string

  Overrides default cluster SVIP with the one specified. This is required or deployments that have implemented the use of VLANs for iSCSI networks in their cloud.

• template-account-name | string

  Account name on the SolidFire Cluster to use as owner of template/cache volumes (created if does not exist).

• volume-backend-name | string

  Volume backend name for the backend. The default value is the application name in the Juju model, e.g. "cinder-sf-mybackend" if it's deployed as juju deploy cinder-solidfire cinder-sf-mybackend. A common backend name can be set to multiple backends with the same characters so that those can be treated as a single virtual backend associated with a single volume type.

• volume-prefix | string

  Create SolidFire volumes with this prefix. Volume names are of the form <sf_volume_prefix><cinder-volume-id>. The default is to use a prefix of ‘UUID-‘.