Skip to main content
Pure Technical Services

vSphere Plugin User Guide: Using the Home Screen

Many of the Pure Storage Plugin for the vSphere Client features are purposefully built-in to the native screens of the vSphere Client interface, to more seamlessly integrate feature functionality. Certain features of the plugin do not map directly to native vSphere objects (VMs, datastores, folders, etc) and are therefore placed in the home screen of the plugin.

The home screen of the plugin can be accessed by clicking on the top Menu dropdown in the vSphere Client and choosing Pure Storage in the list.

clipboard_ec3c1a899110af087b798062acfbcba26.png

Once accessed, tasks like authenticating the plugin to Pure1 or specific FlashArrays can be run and as well as other array functions.

clipboard_e1212d4e21eff20aa7158c87372379927.png

For information on authentication, refer to the following article:

vSphere Plugin User Guide: Configuring Authentication

Pure1 Tags

If Pure1 connectivity has been configured, the Pure Storage Plugin for the vSphere Client will pull all of the tags created within Pure1 for that particular array. The tags will be displayed in the Pure1 Tags column next to the array:

clipboard_e18a82c07a7488e79e12c8b5606cba67a.png

And also below if an array is selected and the Pure1 Tags tab is chosen.

clipboard_ee45ad02785597a7e21be5e6c43648bca.png

Tags can currently not be created, edited, or deleted with the vSphere Plugin. If tags are not appearing, it is for one of the following reasons:

  • Pure1 is not authenticated with the plugin
  • The selected FlashArray is not in the authenticated Pure1 organization. This usually means that your company has more than one Pure1 organization. Currently the plugin can only store authentication for a single Pure1 organization.

If you would like to create, edit, or delete Pure1 tags, please either login directly to Pure1.purestorage.com, or use REST API integrations like the Pure1 PowerShell module or the Pure Storage Plugin for vRealize Orchestrator.

 Current use cases, besides viewing them can be to copy/paste the tags into vSphere tags on datastore or VMs that are hosted by that particular array. There are future plans to further integrate Pure1 tags into the vSphere Plugin.

 

Pure1 Load Meter

The Pure1 Load metric (sometimes referred to as the "busy" meter) provides an easy-to-understand metric to help decide if the array performance is near a limit. This metric is returned as a percentage and reflects how much of the arrays current resources in aggregate are being used to run the current workload. 0% means the array is idle. 100% means that the array is entirely consumed with its workload.

For more details on the load metric itself, please refer to this article:

https://support.purestorage.com/Pure1/Pure1_Manage/003_Analytics/Array_Load_Statistics_Quick_Reference_Guide

When the plugin has been authenticated with the Pure1 REST API, the load metric will be available in the plugin. This metric (and its historical value) can be retrieved by selecting an array in the array list and choose the Load tab below the array list.

clipboard_e152237fc5622dfafe90a7082c9be6fa1.png

If load is not available, it is for one of the following reasons:

  • Pure1 is not authenticated with the plugin
  • The selected FlashArray is not in the authenticated Pure1 organization. This usually means that your company has more than one Pure1 organization. Currently the plugin can only store authentication for a single Pure1 organization.

The load metric is not a live value, so it can be delayed by up to an hour, though usually less. The chart allows 4 levels of granularity, the last 3 hours, the last day, the last week or the last month. The Pure1 load metrics is kept for up to 30 days in Pure1, so the plugin shows the maximum time window.

To change the time window, select the dropdown on the right-hand side and choose the desired duration:

clipboard_e842645c988cde4928c63b1f7dedbcbf3.png

Furthermore, you can select either to show average values (each data point is the average of the underlying sampled granularity) or the maximum (each data point is the maximum value of that granularity).

clipboard_e1c4a2d1f5ed0ef903a0794b9ceea29ee.png

The timestamp is set in UTC time (the time zone advertised in the Pure1 REST API). Localization of this timestamp in the plugin is being considered as a future enhancement.

Volume Groups/QoS Management

When selecting an array under the Pure Storage Plugin for the vSphere Client home screen, a tab called Volume Groups appears. For this tab to be accessible a customer must be on Purity 5.1 or later.

clipboard_e374d5fc2bb671d3c2bb906641a8a6d25.png

Viewing and Searching for Volume Groups or Volumes

When you choose the volume groups tab, the plugin will list all related volume groups and volumes to the current VMware environment.

clipboard_e83191ecb8b7c16f78ba7b904b5d993d5.png

For a volume to appear in this list, it must be in use as a VMFS datastore (RDMs currently do not appear in this list). Volumes in use as vVols are also not shown--they will be listed under the corresponding virtual machines under the vSphere Client VM and Templates view. 

The panel will also list all of the volume groups that are either empty or have volumes hosting a VMFS datastore in the VMware environment.

Volume groups will appear as folders:

clipboard_effa363e6eb96d0f4a7553ff4f3c9ffde.png

Datastores will appear as standalone volumes.

If a volume group has both an unrelated volume and a VMFS datastore volume, it will appear, but the unrelated volume information will be obscured.

clipboard_e59da7a411bbf8ad64d89b773439e0d5b.png

You can search through the volumes and volume groups by specifying, a FlashArray volume name, a VMFS datastore name, a volume group name, or a pod name.

For example: to search for all volumes in a pod named "activeDRPodA" enter the name of the pod plus to colons.

 clipboard_e2436a0585d7f12a9cb382519ecf46a60.png

Creating a Volume Group

To create a new volume group, click Create Volume Group:

clipboard_e39394ecd36430ade4fb350f09a2e9c3f.png

You can then enter a name and optionally an IOPS and/or bandwidth limit.

You can click on a volume group and more information will appear to the right of the volume listing.

clipboard_edd2f656033fcf6ddb9a8d900b5a43e36.png

Editing a Volume Group

This will display any QoS limits applied to that volume group. You can  rename the volume group or alter its limits by clicking Edit Volume Group.

clipboard_e791e7fbe539d69c8dc2d5f77e22fcb72.png

To remove a limit, clear the value (do not put in a zero) and click Edit to confirm the change.

In order to apply QoS limits to a volume group or individual volumes, the underlying array must be running Purity 5.3.x or later. Furthermore, if a volume in the group has its own limit set, a limit cannot be set on the group until the volume limit is cleared.

If you click on a volume, it will show the volume information as well as volume group information if it is in one.

clipboard_e79c51c6d261f553cc60dccb9d1cc76a9.png

Editing a Datastore

To change the configuration of the datastore, you can click on Edit Datastore.

clipboard_eb63b160d1572b3588a9252ab86ee6008.png

Here you can change a variety of configurations:

  • Volume name: Rename the FlashArray volume.
  • Datastore name: Rename the datastore name. Generally it is recommended to keep this consistent, but you can deselect the option "Same as volume name" if you wish to configure the names differently.
  • Volume group: the volume group it is in. If a volume is in a pod it currently cannot also be in a volume group. This is a Purity limitation. To remove a volume from a group, choose the option "None". Only volume groups that are empty or currently have volumes in use as VMFS datastores in the current VMware environment will appear in the list. Requires Purity 5.1+
  • Pod: The pod it is in. If a volume is in a volume group it cannot be put into a pod without first removing it from the volume group--if the volume is in a volume group this option will be grayed out. If a pod is stretched or has an active replica link, a volume cannot be moved into it. Only new volumes can be placed in stretched or replica link-enabled pods. Requires Purity 5.1+
  • Size. Changing this will resize the volume and grow the VMFS datastore to consume the new capacity. The datastore can only be grown--it cannot be shrunk.
  • Volume bandwidth limit. This dictates the total amount of bandwidth (read or write) that can be sent to that volume. This cannot be set if the volume is in a volume group that has its own limit set. To remove a limit, clear the value (do not put in a zero) and click Edit to confirm the change. Requires Purity 5.3+
  • Volume IOPS limit. This dictates the total amount of IOPS (read or write) that can be sent to that volume. This cannot be set if the volume is in a volume group that has its own limit set. To remove a limit, clear the value (do not put in a zero) and click Edit to confirm the change. Requires Purity 5.3+

Video Demo