Pure Storage

Turbonomic supports management of the following Pure Storage technologies:

  • FlashArray//C

  • FlashArray//X

The following technologies are not supported:

  • FlashBlade

Because of the improved performance of Pure Storage arrays, Turbonomic intelligently moves more demanding workloads to Flash-based data stores. Turbonomic analysis is also able to incorporate Pure Storage de-duplication and compression when recommending actions.

Prerequisites

  • Pure Storage F-series and M-series arrays running Purity 5.3.6 and 6.4.4 (Pure API 1.6)

  • A service account Turbonomic can use to connect to the FlashArray

    This account needs privileges to execute commands through the Pure Storage API — Typically the default pureuser administrative account.

Adding Pure Storage targets

Note:

This topic describes features that are available in the new design of the user interface. This new design is enabled by default. If you switched to the legacy design, click New Feature Toggle button in the navigation bar of the user interface and then turn on the toggle to re-enable the new design. For more information, see New Design for the User Interface.

  1. Click Settings > Target Configuration.

  2. On the Target configuration page, click Add Target.

  3. On the Select target page, click Pure Storage.

  4. In the side panel, review the connection requirements and then click Connect Target.

  5. Configure the following settings:

    • Hostname or IP address

      Specify the host name or IP address of the Pure Storage FlashArray.

    • Username

      Specify the username of the service account that Turbonomic uses to connect to the FlashArray.

      The username must not contain the domain. For example, Username=jjsmith is correct, while Username=myDomain\jjsmith fails to validate.

    • Password

      Specify the password of the service account that Turbonomic uses to connect to the FlashArray.

    • Connect using HTTPS

      If this option is selected, Turbonomic uses SSL to connect to the Pure target.

      Most Pure Storage installations do not accept insecure connections. If you receive an error when adding the target with secure connections disabled, try re-adding with this option enabled.

      This option is selected by default.

    • Certificate authority

      Specify the root certificate for validating the SSL connection to the FlashArray.

Entity mapping

After validating your targets, Turbonomic updates the supply chain with the entities that it discovered. The following table describes the entity mapping between the target and Turbonomic.

Pure Turbonomic
Volume Storage
Shelf Array Disk Array
Controller Storage Controller

Storage targets (storage controllers) add Storage Controller and Disk Array entities to the supply chain. Disk Array entities then host Storage entities (datastores).

Monitored resources

Turbonomic monitors the following resources:

  • Storage

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage provisioned

      Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

      Note:

      When it generates actions, Turbonomic does not consider IOPS throttling that it discovers on storage entities. Analysis uses the IOPS it discovers on Logical Pool or Disk Array entities.

    • Latency

      Latency is the measurement of storage latency.

  • Disk array

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage provisioned

      Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    • Latency

      Latency is the measurement of storage latency.

  • Storage controller

    Note:

    Not all targets of the same type provide all possible commodities. For example, some storage controllers do not expose CPU activity. When a metric is not collected, its chart in the user interface will not display data.

    • CPU

      CPU is the measurement of CPU that is reserved or in use.

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

      The storage allocated to a storage controller is the total of all the physical space available to aggregates managed by that storage controller.

Actions

Turbonomic supports the following actions:

  • Storage

    • Resize up

      This action can only be executed outside Turbonomic.

  • Storage controller

    • Provision

      This action can only be executed outside Turbonomic.

  • Disk array

    • Provision

      This action can only be executed outside Turbonomic.

Pure Storage assigns all the disks managed by a storage controller to a single array, with a fixed form-factor. There are no actions to perform for an array. For example, there is no action to move a disk array from one storage controller to another. Likewise, there are no actions to move or provision volumes because of the fixed form-factor.