5.5.0 Release Notes

General

Version 5.5.0 of the Everpure vSphere HTML Remote Client Plugin supports vSphere (vCenter and ESXi) version 6.7U3 and later and Purity version 6.1.x and later. Users can upgrade to this version of the plugin via deploying the Everpure VMware Appliance. This version is certified with VMware.

Important notices regarding the vSphere Client Plugin:

• Starting in vSphere 8.0, VMware no longer supports local plugins to be installed in vCenter (Everpure vSphere Plugin versions 4.5.2 and below). Please use the remote versions of Everpure's vSphere plugin (Everpure vSphere Plugin versions 5.0.0 and above). For more information please refer to this VMware KB.

• This version of the plugin uses the VMware Remote Plugin Architecture

  • More information on the VMware Remote Plugin Architecture can be found

    here.

  • More information on why Everpure is using this can be found here.

• Release notes for Everpure's VMware Appliance (OVA) can be found at this page. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be downloaded here. The installation guide for the remote vSphere plugin can be found here

What's New

• TMAN-22149: Added support for Fusion to the vSphere Plugin. This includes support for Fleet management, Fusion Presets and the ability to deploy Fusion workloads when creating datastores with the vSphere Plugin.
  • TMAN-22209: The plugin home page has been completely redesigned to support Fusion. The vSphere Plugin user guide has been added to provide context for the changes.

    • 

  • TMAN-22211: When registering an array from a Fusion Fleet, all arrays in the Fleet will be added to the list of arrays.
  • TMAN-22210: Support for Fleet Management has been added. This includes creating a fleet from an array not in a fleet, adding an array to a fleet, removing an array from a fleet and removing a fleet registration.
  • TMAN-22213: vSphere User mappings for FlashArray and Fleet Credentials.

    As part of adding support for Fusion, the permissions to FlashArrays registering with the plugin was re-worked. Now that Fleets and Arrays have a default user that is shared with all vSphere Users, it is recommended that the default credentials used are with a read-only user.

    vSphere plugin users are able to add their own credentials for the Fleet or individual arrays that will only be used for that vSphere user. It is expected that any vSphere user that needs permissions to arrays that are not read only will be able to provide credentials for the fleet or array that they have permissions for. Because Fusion (at the time of this release) requires LDAP integration, the best practice for the vSphere User is to add their LDAP credentials to the Fleet or Array credentials.

    Further information can be found in the user guide.

    • 

  • TMAN-22214: Added Fusion workload creation based on Fusion presets. This option is available when using the create datastore wizard with the plugin.

    • 

  • TMAN-22217: Modified add/update host groups to include options to manage the entire Fusion Fleet.

    • 

Fixed Issues

• TMAN-21543: SPBM Wizard - updated messaging and added additional information on ransomware protection.
• TMAN-21903: Fixed an issue where datastores would fail to load on the array view page after a vVols Storage Container (pod) was manually destroyed on the array.
• TMAN-22976: Added messaging for the reasoning why the default storage container can not be resized.

Known Issues

• TMAN-23218: Create snapshots dialog displays duplicate datastore and array names for VMFS datastores backed by a stretched pod.
• TMAN-23202: Fusion preset: If a host from a cluster is not configured on the array, the user is not notified with a warning.
• TMAN-23234: Add/Updating a host fails to create the host object in the array when existing hosts of the Cluster belong to multiple host groups.
• TMAN-23133: 'Create’ button remains enabled even when no configuration changes are detected for Add/Update Host