Deploying Panzura as Azure Virtual Machine

This document provides instructions on how to deploy a Panzura node as an Azure Virtual Machine.

Azure Prerequisites to Deploy the Node

The following information is required:

• An Azure account with Portal access

• A configured Azure virtual private network (VPN).

o https://docs.microsoft.com/en-us/azure/vpn-gateway/create-routebased-vpngateway-portal

• An Azure Resource group.

o https://docs.microsoft.com/en-us/azure/azure-resourcemanager/management/manage-resource-groups-portal

• An Azure storage account.

o https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-createaccount-block-blob

• An Azure BLOB container.

o https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstartblobs-portal

Panzura Information and Prerequisites

• A License token

• A Peer-to-peer authentication key (If installing a subordinate/HA node)

• Networking information (Associated Subnet for DHCP)

• DNS server IP addresses and domain name.

• Active Directory domain name/Netbios name, plus administrative account credentials to join.

• NTP server hostname/IP address.

• Cloud provider information, obtained from Azure:

o Storage account name

o Access key

o Container name

• Additional Cloud information:

o Cloud Hostname is: windows.net

o Cloud Size: 1-10PB

o Path: Name of a folder to create within the container

Azure Virtual Machine Instance Sizing

The following applies to node deployments within Azure.

Supported node deployments on Azure

D8S_v3 8 vCPUs 32GB RAM Premium SSD Storage, Read/Write Host Disk Caching
DS13_v2 8 CPUs  56GB RAM Premium SSD Storage, Read/Write Host Disk Caching
D16S_v3 16 vCPUs 64GB RAM Premium SSD Storage, Read/Write Host Disk Caching
DS15_v2  16 vCPUs 64GB RAM Premium SSD Storage, Read/Write Host Disk Caching
D32S_v3 20 vCPUs 140GB RAM Premium SSD Storage, Read/Write Host Disk Caching
D64S_v3 64 vCPUs 256GB RAM Premium SSD Storage, Read/Write Host Disk Caching

Deploying a Node as an Azure VM

  1. Sign into the Azure portal (https://portal.azure.com).
  2. Search for Panzura and select the appropriate Panzura version from the Marketplace.
    Read the overview and click Create.
    • Resource group
    • Virtual machine name
    • Region - Where the node will be hosted
    • Image - Current GA or version to match an existing deployment
    • Size - A suitable supported instance type
    • Authentication Type - Switch to Password and use panzuraadmin with a 12 character password.Complete the Basic section by entering the parameters for the deployment:
  3. Click Next: Disks >
  4. Creating Disks Panzura supports only Premium SSD for use with Azure Machine Instances (ZMI), the following table makes reference to the most common deployments:
    512 GB P20 2300 IPS
    513-1024 GB P30 5000 IPS
    1025 - 2048 GB P40 7500 IPS
    The smallest supported disk is 512 GB with an increment of 6 disks. The recommended maximum is 1024 GB up to an increment of 24 disks. An increment of up to 12-24 disks yields the most throughput* The above example shows the smallest supported configuration. Click Next: Networking >
  5. Configure NetworkingUsing the previously generated Azure prerequisites, apply the resource group with the associated VPN configuration.
    The network security group (NSG) is a type of firewall, the Panzura node requires various ports to be successful, all of which can be viewed within Required Ports. By default, the following rules are applied:
    Inbound Protocol Source
    ssh (22)  Anywhere
    https (443) Anywhere
    Outbound Protocol Destination
    Any Anywhere
  6. Additional Information:
    If no additional information is required by the business the remaining pages maybe skipped by clicking:
    Review + Create
    Some businesses require Tags to be associated with Azure Machine Instances (ZMI), the other two pages are left default. To add tags, click the Tags option from the top of the page, once satisfied, continue to:
    Review + Create

7. Final Creation

Satisfy any remaining requirements such as:

Preferred e-mail address

Preferred phone number

 

Click Create.

8. Once complete click Go to Resource

9. Collect the assigned Private IP Address from the resource overview page

Using the Panzura Configuration Wizard

1. Using Chrome or Firefox connect to the Panzura node using the previously collected IP address. https://

https:<node-ip-address>

2. Log in with username admin and the password specified with panzuraadmin.

The Configuration Wizard includes all of the settings to get the node operational.

Click Start

3. Read the EULA, flip the toggle to “Accept” and enter appropriate details.

Click Next

4. This page contains information on the prerequisites for a successful Panzura node deployment, ensuring that the prerequisites are satisfied.

Click Next

5. Enter a new node password, this will be used to login to the WebUI going forward. If the node being deployed is a subordinate, the password will be inherited from the Master node later. Click Next

6. Network (Client & Cloud) Settings

Azure nodes are set to DHCP, Microsoft Azure does not permit changing the network information at this location. Enter DNS IP addresses and click Next.

7. System settings The hostname will have been inherited from the Azure configuration earlier, change the node location as required and set the DNS Domain Name. Click Next when complete.

8. Role Settings, using the drop down select the required node role and enable Support Assistance as needed.

Role Description Prerequisites
Master Configuration settings are added to the Master Node and automatically propagate to the Subordinate nodes.  
Subordinate A node in the CloudFS that receives its configuration settings from the CloudFS Master node. Pairing key from an associated Master node.
HA Local This node will be a dedicated standby for a single active node. Pairing key from an associated Master node.
HA Global This node will be a dedicated standby in the cloudfs capable of taking over for any node in the CloudFS Pairing key from an associated Master node.

It is recommended to enable Support Assistance (SA), the node will upload diagnostic statistics and enable remote support from Panzura Support Services.

Click Next to continue.

9. Time Settings

Switch the toggle to enable NTP and provide a FQDN or IP address for the NTP source, then alter the time zone to suit. Click Next to continue.

10. Datastore Settings

Disks were added earlier in the process and here the manual radio button has been selected, greying out the other option. The remaining settings are for the Automatic datastore deployment, however, enter the values as shown to proceed, clicking Next to continue.

11. Datastore Allocation

Assign the previously allocated Premium SSD disks to their role within the node. The specific roles are only defined for use with hybrid configurations, which are not supported within an Azure machine instance (ZMI), set the configuration similar to shown, this configuration will balance Metadata and Persistent Read Cache (PRC) across all available disks. Once complete, click Next.

12. Acknowledge that once the disks have been added to the node, they cannot be removed without a complete rebuild of the instance. Click Proceed to continue.

13. Panzura Licensing - enter the License token supplied by Panzura and click Next.

14. Cloud Service Provider - enter the cloud credentials for your object store and click Next.

15. Acknowledge changing the cloud storage provider afterwards will require a factory reset and click Proceed.

The node will now contact the license portal and configure the Azure machine instance to the designated cloud provider, this step can take several minutes to complete. Once successful the node will start booting the Panzura services.

16. Protocol Settings, the most common deployment is SMB-only, however, Panzura also supports NFS and both protocol access to the node. Select the appropriate protocol(s) and click Next.

17. Active Directory Setup, apply the required AD domain name, NetBIOS, if applicable, along with account credentials capable of joining a client to the domain.

The process will attempt to add the node to the AD DNS if permitted, if using a non-Microsoft DNS or not permitting dynamic DNS entries, create an A record for the new node.

18. Finally review the configuration setting summary and click Finish.