vSphere Plugin: Online Deployment Procedure

User Guides for VMware Solutions
Audience
Public
Content Type
User Guides
Source Type
Documentation

Note:

When performing online deployment, upgrades, queries and tasks with puresw, access to deb.cloud-support.purestorage.comvia port 443 is required.

The appliance will need access to each vCenter it will be registered with on ports 8443 and 443. The FlashArray's that will be used with the plugin will need to be accessible via port 443 to the appliance.

For offline deployments that are unable to access deb.cloud-support.purestorage.com, please see the vSphere Plugin: Offline Deployment Procedure section of this KB.

Deployment of the Everpure Appliance is very similar to a typical OVA deployment.

  1. Right-click on the cluster you wish to deploy the VMware appliance to, and then select Deploy OVF Template...

  2. In the Deploy OVF template wizard, either provide the URL for the VMware appliance or if it has been downloaded locally, select Local File, then click on Upload Files and choose the OVA file from your local drive.
  3. Click Next when the OVA file has been specified.
  4. Optionally provide a unique Virtual machine name and select a folder for it to be deployed into. Click on Next when these selections have been made.

  5. Pick the ESXi cluster or Host where you want to deploy the VMware appliance. Click on Next once the selection has been made.

  6. Review the advanced configuration options and confirm the details selected thus far and then click on Next.

  7. Read the licensing agreement and then click the checkbox to accept to the licensing terms and click Next.

  8. Pick a storage device to install the VMware appliance template to. Optionally change the virtual disk format and/or select a VM storage policy and then click on Next.

  9. Pick the network you wish to use for the appliance. Note that it must be routable to the vCenter management network. Click on Next to continue.

  10. In the OVA customization template, at the top of the screen first pick the vSphere Remote Client Plugin option from the Appliance Type list.
    Note:

    Reminder: The Everpure VMware Appliance was released to support deployments of Everpure integrations such as the Remote Plugin for the vSphere Client and the VM Analytics Collector. The VMware appliance can only support a single integration per deployment; when multiple integrations are needed, more than one VMware appliance will need to be deployed.

    Note:

    If your environment does not have access to Pure1 during the VMware appliance deployment please see the Offline Deployment Procedure for this step.

  11. Select the DHCP checkbox if DCHP is preferred and skip 11a.; otherwise un-check the DHCP checkbox and follow 11a. below.
    Note: In order to change the Docker networking configuration after the VMware appliance has been successfully deployed, a new appliance will need to be deployed.

    Please keep in mind that because there is a single line for the docker network for the subnet and the gateway to not use just the subnet and CIDR notation, but the gateway followed by the CIDR. For example, use 172.17.0.1/16 but do not use 172.17.0.0/16.

    1. If a static IP address is to be associated with the Pure VMware Appliance, fill out the relevant networking information including IP address, netmask, gateway, DNS Server(s). Optionally specificy a custom hostname and if a Proxy is being used, supply the URL, Port and login information for the proxy.
    2. The field to provide the docker networking subnet is right after the proxy network. Please ensure that the subnet provided is not in use in your environment. This should be a unique and private network that only the appliance will use for communicating between the plugin container and the appliance networking. The remote vSphere plugin runs on Pure Storage's VMware appliance as a Docker container. Docker has its own bridge network configuration, with the default being a 172.17.0.1/16 subnet and 172.17.0.1 is the gateway. If your internal network configuration overlaps with this default, you must change the Docker bridge network via the field below (Docker IP Range) to avoid IP address conflicts. Note that the format is an IP/netmask address, not a subnet/netmask address, with a CIDR.
  12. Review the details of the VMware appliance deployment and then click on Finish to deploy.

  13. Once the VMware appliance has finished deployment within vCenter, power it on to finish its configuration and to make it available to login to.
  14. Follow Change pureuser's Password from VM Analytics Collector Creation, Deployment, and Configuration (you must be logged in to view the link) to change the default appliance password.
  15. If the vCenter's fully qualified domain name (FQDN) contains .local, run the following command from the command line of the VMware appliance to ensure you can add arrays properly from the plugin in vCenter: 
    
pureuser@purestorage-vmware-appliance:~$ puredns setattr --search {your .local domain suffix} --nameservers {ip or FQDN of DNS server}