Skip to main content
Pure1 Support Portal

HTML5 vSphere Plugin Beta Support

Pure Storage will be inviting some customers to participate in a beta for the upcoming HTML5 vSphere Plugin.  This KB covers each process of a TSE being able to support the customer in this process, what information is there for the customers, what Pure would like them to look for and what to do with issues or bugs reported.

Getting Started

For the HTML5 vSphere Plugin Beta we will be requiring Account Teams and Customers to work through a Salesforce Case that a TSE will own for that Beta duration.  Prior to the Case being opened, the Account Team and customer will be working with PM to get put on the Beta.  After that is approved they will want to open up a Support Case.  They need to make sure that Craig Waters (craig.waters@purestorage.com) is CC'd on that Support Case.  Craig will confirm if the Customer is on the Beta and they have been approved to move forward with getting the Plugin installed.

Support will want to leave the Salesforce Case opened until the customer has finished the Beta and the Beta Plugin is removed from the FlashArray.  This way the customer can use the same case to give feedback, report issues and ask follow up questions about the Plugin.

This KB will cover the following:

  1. Manually Updating the Plugin
  2. Installing the Plugin
  3. Using the Plugin
  4. Support for the Beta Plugin
  5. Removing the Beta Plugin

 

Requirements

Customers will need to be running either vCenter 6.5 U2 or be running on vCenter 6.7+ in order to use the HTML5 Plugin.

Manually Updating the Plugin

After the Customer opens up the support case asking to update their plugin to the HTML5 Beta and the correct parties have signed off, you'll want to follow this process to update the Plugin on the Array.

The process in and of itself is simple

  1. Have the Customer open an RA to the Array
  2. Use Vats on fuse to upload the files to the Array
  3. Copy the files to the peer controller
  4. Backup and Copy the existing plugin
  5. Move the files to the plugin folder
  6. Update ownership of the files in the plugin folder
  7. Update links in the plugin folder
  8. Repeat the steps on the peer controller
  9. Let the customer know that the beta plugin is installed

Okay, now that we have a process overview, here is an example of running through this process after the RA is open. 

  1. Check to make sure the beta plugin files are on fuse
    ls -la /support/HTML5-Beta/
    
    ls -la /support/HTML5-Beta/
    total 28564
    drwxr-sr-x   2 alex.carver fuseuser     6144 Oct 18 23:51 ./
    drwxrwsrwx 740 root        fuseuser    71680 Oct 18 23:46 ../
    -rw-r--r--   1 alex.carver fuseuser  6785052 Oct 18 23:50 PureStorage_vSphere_installer.jar
    -rw-r--r--   1 alex.carver fuseuser 22387912 Oct 18 23:52 purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
  2. Use Vats to upload the Beta Plugin files to the array
    vats push /support/HTML5-Beta/PureStorage_vSphere_installer.jar <array-name>-ct1.<array-domain>.com
    
    vats push /support/HTML5-Beta/purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip <array-name>-ct1.<array-domain>.com
    
    vats push /support/HTML5-Beta/PureStorage_vSphere_installer.jar sn1-405-c12-21-ct1.purestorage.com
    Requesting RA List (may take up to 15 seconds)
    -------------------------------------
    You have selected the following array
    Name: sn1-405-c12-21-ct1.purestorage.com
    ID: 1013864-259203980-7182999116483707531
    -------------------------------------
    Are you sure this is the array you want?
    NOTE: All actions after this point are permanently logged
    y/N [N]: y
    Preparing file '/support/HTML5-Beta/PureStorage_vSphere_installer.jar' for SCP
    File prepared, sending to array
    VATS SSH starting, requesting BLESS key (may take up to 30 seconds)
    BLESS key acquired, finalizing local environment
    VATS log at: https://owl.dev.purestorage.com/ra-display/detail/fafd8e3d-132e-4821-b807-9ebce92fbb74
    Warning: Permanently added '[internal-vats-bastion-364130995.us-west-2.elb.amazonaws.com]:2022,[172.16.144.236]:2022' (ECDSA) to the list of known hosts.
    File will be uploaded to array as: /home/os76/PureStorage_vSphere_installer.jar
    
    
    Warning: Permanently added 'sn1-405-c12-21-ct1.purestorage.com' (ECDSA) to the list of known hosts.
    
    
    os76@sn1-405-c12-21-ct1.purestorage.com's password:
    PureStorage_vSphere_installer.jar             100% 6626KB   6.5MB/s   00:00
    Connection to internal-vats-bastion-364130995.us-west-2.elb.amazonaws.com closed.
    VATS SSH cleanup complete, goodbye
    SCP complete for '/support/HTML5-Beta/PureStorage_vSphere_installer.jar'
    
    
    --
    
    
    vats push /support/HTML5-Beta/purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip sn1-405-c12-21-ct1.purestorage.com
    Requesting RA List (may take up to 15 seconds)
    -------------------------------------
    You have selected the following array
    Name: sn1-405-c12-21-ct1.purestorage.com
    ID: 1013864-259203980-7182999116483707531
    -------------------------------------
    Are you sure this is the array you want?
    NOTE: All actions after this point are permanently logged
    y/N [N]: y
    Preparing file '/support/HTML5-Beta/purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip' for SCP
    File prepared, sending to array
    VATS SSH starting, requesting BLESS key (may take up to 30 seconds)
    BLESS key acquired, finalizing local environment
    VATS log at: https://owl.dev.purestorage.com/ra-display/detail/e92d3461-4c6d-455d-8526-5fc792e4b625
    Warning: Permanently added '[internal-vats-bastion-364130995.us-west-2.elb.amazonaws.com]:2022,[172.16.145.72]:2022' (ECDSA) to the list of known hosts.
    File will be uploaded to array as: /home/os76/purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    
    
    Warning: Permanently added 'sn1-405-c12-21-ct1.purestorage.com' (ECDSA) to the list of known hosts.
    
    
    os76@sn1-405-c12-21-ct1.purestorage.com's password:
    purestorage-vsphere-plugin-4.0.999999_2018101 100%   21MB   2.4MB/s   00:09
    Connection to internal-vats-bastion-364130995.us-west-2.elb.amazonaws.com closed.
    VATS SSH cleanup complete, goodbye
    SCP complete for '/support/HTML5-Beta/purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip'
  3. RA to the Array and navigate to the /home/os76/ directory.
    vats
    
    cd /home/os76/
    
    /logs/purestorage.com/sn1-405-c12-21-ct0/2018_10_22 $ vats
    No command provided, assuming you wanted 'vats auto'
    Assuming hostname: sn1-405-c12-21-ct0.purestorage.com
    Requesting RA List (may take up to 15 seconds)
    Trying alternate controller name: sn1-405-c12-21-ct1.purestorage.com
    -------------------------------------
    You have selected the following array
    Name: sn1-405-c12-21-ct1.purestorage.com
    ID: 1013864-259203980-7182999116483707531
    -------------------------------------
    Are you sure this is the array you want?
    NOTE: All actions after this point are permanently logged
    y/N [N]: y
    VATS SSH starting, requesting BLESS key (may take up to 30 seconds)
    BLESS key acquired, finalizing local environment
    VATS log at: https://owl.dev.purestorage.com/ra-display/detail/0c27eb81-7a0b-4a1f-a32a-42a4e37222ae
    System GUI available at: https://i-0386fa8ea754e14fb.dev.purestorage.com:52000
    Warning: Permanently added '[internal-vats-bastion-364130995.us-west-2.elb.amazonaws.com]:2022,[172.16.144.126]:2022' (ECDSA) to the list of known hosts.
    My challenge is: hybrid tombe wainer 1013864-259203980-7182999116483707531
    My response is: 3f1b6-b6209-dd82f-77f6e-6e750-ed2f3-4909a-9d481-a0cad-c6108-0734a-7cb64-b3522-e04cc-95ebd-fa3b9-35f89-b4c51-d8d25-e
    ...
    Mon Oct 22 16:26:56 2018
    Welcome pureeng. This is Purity Version 5.1.5 on FlashArray sn1-405-c12-21
    http://www.purestorage.com/
    
    root@sn1-405-c12-21-ct1:~# cd /home/os76/
    root@sn1-405-c12-21-ct1:/home/os76#

     

  4. Copy the files to the peer controller
    scp PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip peer:/home/os76/
    
    root@sn1-405-c12-21-ct1:/home/os76# scp PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip peer:/home/os76/
    PureStorage_vSphere_installer.jar                                                                                                                                                                                                             100% 6626KB   6.5MB/s   00:00
    purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip                                                                                                                                                                         100%   21MB  21.4MB/s   00:01
    
  5. Backup a copy of the current plugin to /home/os76/
    The plugin version currently may differ from the example, in this one the current plugin is 3.1.1
    mkdir /home/os76/flash_plugin_backup/
    cp /opt/Purity/ui/plugins/vsphere/purestorage-vsphere-plugin-3.1.1_201807131549+966d3cd-rel_3_1_1.zip /home/os76/flash_plugin_backup/
    cp /opt/Purity/ui/plugins/vsphere/PureStorage_vSphere_installer.jar
    
    root@sn1-405-c12-21-ct1:/home/os76# mkdir /home/os76/flash_plugin_backup/
    root@sn1-405-c12-21-ct1:/home/os76#
    root@sn1-405-c12-21-ct1:/home/os76# cp /opt/Purity/ui/plugins/vsphere/purestorage-vsphere-plugin-3.1.1_201807131549+966d3cd-rel_3_1_1.zip /home/os76/flash_plugin_backup/
    root@sn1-405-c12-21-ct1:/home/os76#
    root@sn1-405-c12-21-ct1:/home/os76# cp /opt/Purity/ui/plugins/vsphere/PureStorage_vSphere_installer.jar /home/os76/flash_plugin_backup/
    root@sn1-405-c12-21-ct1:/home/os76#
    root@sn1-405-c12-21-ct1:/home/os76# ls -la /home/os76/flash_plugin_backup/
    total 26624
    drwxr-xr-x  2 root root     4096 Oct 22 19:02 .
    drwx------ 10 os76 os76     4096 Oct 22 19:01 ..
    -rw-r--r--  1 root root  6784996 Oct 22 19:02 PureStorage_vSphere_installer.jar
    -rw-r--r--  1 root root 20462269 Oct 22 19:02 purestorage-vsphere-plugin-3.1.1_201807131549+966d3cd-rel_3_1_1.zip
    
  6. Move the files to the plugin directory
    mv -t /opt/Purity/ui/plugins/vsphere PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    
    root@sn1-405-c12-21-ct1:/home/os76# mv -t /opt/Purity/ui/plugins/vsphere PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    root@sn1-405-c12-21-ct1:/home/os76#                                                                                                                                                                      100%   21MB  21.4MB/s   00:01
  7. Navigate to the plugin directory
    cd /opt/Purity/ui/plugins/vsphere/
    
    root@sn1-405-c12-21-ct1:/home/os76# cd /opt/Purity/ui/plugins/vsphere/
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ls -la
    total 47704
    drwxr-xr-x 2 root root     4096 Oct 18 17:17 .
    drwxr-xr-x 3 root root     4096 Oct 18 16:26 ..
    -rw-rw-r-- 1 os76 os76  6785052 Oct 18 16:56 PureStorage_vSphere_installer.jar
    -rw-r--r-- 1 root root 19656830 Oct 17 12:23 purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    -rw-rw-r-- 1 os76 os76 22387912 Oct 18 16:57 purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    lrwxrwxrwx 1 root root       67 Oct 18 16:26 purestorage-vsphere-plugin.zip -> purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip                                                                                                                                                                  100%   21MB  21.4MB/s   00:01
  8. Update the file ownership
    chown root:root purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    
    chown root:root PureStorage_vSphere_installer.jar
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# chown root:root purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# chown root:root PureStorage_vSphere_installer.jar
    
  9. Update the Links in the plugin directory
    ln -sf purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip purestorage-vsphere-plugin.zip
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ln -sf purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip purestorage-vsphere-plugin.zip
    
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ls -la
    total 47704
    drwxr-xr-x 2 root root        4096 Oct 18 17:21 .
    drwxr-xr-x 3 root root        4096 Oct 18 16:26 ..
    -rw-rw-r-- 1 root root     6785052 Oct 18 16:56 PureStorage_vSphere_installer.jar
    -rw-r--r-- 1 root root    19656830 Oct 17 12:23 purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    -rw-rw-r-- 1 root root    22387912 Oct 18 16:57 purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    lrwxrwxrwx 1 root pureeng       69 Oct 18 17:21 purestorage-vsphere-plugin.zip -> purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    
  10. Repeat steps 5 through 9 for the peer controller
  11. Confirm with the customer that the plugin is updated in the FlashArray GUI.
    Before the Plugin is manually updated
    HTML5 Beta Plugin - 01.png
    After the Plugin is manually updated
    HTML5 Beta Plugin - 02.png

     

 


 

Installing the Plugin

After the array has been updated with the beta plugin, the customer will be able to install the plugin.  It's unlikely that the TSE will need to help the customer with this, but fort he sake of completeness, here is the process.

  1. Log into the FlashArray with the Beta Plugin
  2. Navigate to Settings and then click on Software
  3. Click on Edit vSphere Plugin Configuration Button
    HTML5 Beta Plugin - 02 - 02.png
  4. Enter the information and credentials for the vCenter that the Plugin will be installed to.
    HTML5 Beta Plugin - 03.png
  5. Confirm that the vCenter is connected successfully and click the install button
    HTML5 Beta Plugin - 04.png
  6. Confirm that the Beta Plugin shows up installed in the FlashArray GUI
    HTML5 Beta Plugin - 05.png
  7. Have the customer log into their vCenter HTML5 Client and confirm that the Plugin shows up
    HTML5 Beta Plugin - 06.png

    The Customer may need to log out and log back into their vCenter Client.  Otherwise they should get a banner asking them to refresh to show the plugin like the one above shows.
  8. If there was a previous plugin installed and arrays were registered, those arrays will carry over to the HTML5 Plugin
    HTML5 Beta Plugin - 07.png
  9. The customer can add new arrays or update the existing array information as needed.
  10. The customer may need to edit the existing arrays and update the registration information.  If the imbedded array GUI isn't showing up or the plugin options for that array aren't showing up correctly, there will be a notice saying to update the array registration.

 

Using the Plugin

Now, there will be a few differences with the HTML5 Plugin vs the existing Flash Plugin.  Here are some examples of what it looks like and where to use the plugin.

Plugin Icon and Location
HTML5 Beta Plugin - 06.png
FlashArray Summary - Add Edit or Remove
HTML5 Beta Plugin - 07.png
Right Click on Datacenter Options
HTML5 Beta Plugin - 22.png
Right Click on Cluster Options
HTML5 Beta Plugin - 20.png
Right Click on Host Options
HTML5 Beta Plugin - 21.png
Right Click on Datastore Options
HTML5 Beta Plugin - 19.png
Datastore View
Configure - FlashArray Snapshots
HTML5 Beta Plugin - 08.png
Datastore Monitor
Capacity - 
HTML5 Beta Plugin - 09.png
Datastore Monitor
Capacity - VMFS Used Space

HTML5 Beta Plugin - 10.png
HTML5 Beta Plugin - 13.png
Datastore Monitor
Capacity - Host Written Space
HTML5 Beta Plugin - 11.png

HTML5 Beta Plugin - 14.png
Datastore Monitor
Capacity - Unique Space
HTML5 Beta Plugin - 12.png
HTML5 Beta Plugin - 15.png
Datastore Monitor
​​​​​​​Performance - IOPS
HTML5 Beta Plugin - 16.png
Datastore Monitor
​​​​​​​Performance - Latency
HTML5 Beta Plugin - 17.png
Datastore Monitor
​​​​​​​Performance - Bandwidth

HTML5 Beta Plugin - 18.png

 


 

Support for the Beta Plugin

Okay, you are a TSE and a customer has a Beta plugin question in their beta plugin case, what do you need to do?

The customer should have a getting started or beta user guide provided to them as part of the beta (not yet created).  If they have questions about basic usage, you'll want to make sure they've been through that.

A big part of the plugin is to find issues with it, get feedback on what we need to change, what's good and not good, etc.  If there is an issue with it, make sure you get a JIRA opened, ping Cody Hosterman and Alex Carver in the JIRA after getting everything timelined out and getting the logs from the customer (virgo).  Once there are logs and a solid timeline, then engineering can get involved.  It's important to document the steps needed to reproduce the issue.  


 

Removing the Beta Plugin

When the Customer is done with the Beta, they have a couple options. 

  1. Leave the Beta Plugin installed and upgrade the HTML5 Plugin to GA once it's released.
  2. Uninstall the 4.0.0-beta plugin via the FlashArray GUI and have support update the plugin on the Array to 3.1.x.

Please keep in mind that if the HTML5 plugin is uninstalled, it will remove all settings used by the flex plugin as well, such as registered arrays and RBAC settings.

Support will need to let the customer know about this if they choose to uninstall the HTML5 Plugin.


Here is the process to roll back the plugin on the array from the beta to 3.1.x.

The process will be fairly simple and really just be repeating steps 6 through 9 on each controller for the manual update process.

Basing it off of that, here are the steps for support to do this.

  1. Move the backed up files to the plugin directory
    cd /home/os76/flash_plugin_backup/
    mv -t /opt/Purity/ui/plugins/vsphere PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    
    root@sn1-405-c12-21-ct1:/home/os76/flash_plugin_backup/# mv -t /opt/Purity/ui/plugins/vsphere PureStorage_vSphere_installer.jar purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    root@sn1-405-c12-21-ct1:/home/os76/flash_plugin_backup/#                                                                                                                                                                      100%   21MB  21.4MB/s   00:01
  2. Navigate to the plugin directory
    cd /opt/Purity/ui/plugins/vsphere/
    
    root@sn1-405-c12-21-ct1:/home/os76# cd /opt/Purity/ui/plugins/vsphere/
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ls -la
    total 47704
    drwxr-xr-x 2 root root     4096 Oct 18 17:17 .
    drwxr-xr-x 3 root root     4096 Oct 18 16:26 ..
    -rw-rw-r-- 1 os76 os76  6785052 Oct 18 16:56 PureStorage_vSphere_installer.jar
    -rw-r--r-- 1 root root 19656830 Oct 17 12:23 purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    -rw-rw-r-- 1 os76 os76 22387912 Oct 18 16:57 purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    lrwxrwxrwx 1 root root       67 Oct 18 16:26 purestorage-vsphere-plugin.zip -> purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip                                                                                                                                                                  100%   21MB  21.4MB/s   00:01
  3. Update the file ownership
    chown root:root purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    
    chown root:root PureStorage_vSphere_installer.jar
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# chown root:root purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# chown root:root PureStorage_vSphere_installer.jar
    
  4. Update the Links in the plugin directory
    ln -sf purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip purestorage-vsphere-plugin.zip
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ln -sf purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip purestorage-vsphere-plugin.zip
    
    
    root@sn1-405-c12-21-ct1:/opt/Purity/ui/plugins/vsphere# ls -la
    total 47704
    drwxr-xr-x 2 root root        4096 Oct 18 17:21 .
    drwxr-xr-x 3 root root        4096 Oct 18 16:26 ..
    -rw-rw-r-- 1 root root     6785052 Oct 18 16:56 PureStorage_vSphere_installer.jar
    -rw-r--r-- 1 root root    19656830 Oct 17 12:23 purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    -rw-rw-r-- 1 root root    22387912 Oct 18 16:57 purestorage-vsphere-plugin-4.0.999999_201810172200+b4d3c1d-master.zip
    lrwxrwxrwx 1 root pureeng       69 Oct 18 17:21 purestorage-vsphere-plugin.zip -> purestorage-vsphere-plugin-3.1.0_201803280019+6193675-rel_3_1_x.zip
    
  5. Repeat steps 1 through 4 for the peer controller
  6. Confirm with the customer that the plugin is updated in the FlashArray GUI.
    Before the Plugin is manually updated
    HTML5 Beta Plugin - 02.png
    After the Plugin is manually updated
    HTML5 Beta Plugin - 01.png
  7. The Flex should still be installed if the HTML5 plugin is removed, but if the customer is having issues with it, have them install it again.