Panzura Freedom 7 Deployment on ... - Cloud Object Storage · Cloud size (in TB) Cleversafe accesser name or IP address ... IBM Cloud Object Storage ... LAN/WAN, License, virtual

695 Campbell Technology Parkway Suite 225 San Jose, CA 95008 [email protected] 1-855-PANZURA (1-855-726-9872) +1 (408) 578-8888

Panzura Freedom 7 Deployment on VMware ESXi

© 2017 - Panzura, Inc. All rights reserved. All rights reserved. The information in this document is subject to change without notice. Originated in the USA. Any other trademarks appearing in this guide are the property of their respective companies. October 2017

mailto:[email protected]

Page: © 2017 - Panzura, Inc. All rights reserved.

2

Contents

OVERVIEW OF PANZURA FREEDOM FILER INSTALLATION ON VMWARE ESXI .......................................... 3

VM REQUIREMENTS .............................................................................................................................. 3

PREPARATION ....................................................................................................................................... 3

INSTALL THE PANZURA FILER ON AN ESXI HOST ..................................................................................... 3

PREPARE TO CONFIGURE THE FILER ....................................................................................................... 9

USE THE SETUP WIZARD TO SET UP THE FILER ...................................................................................... 15

USE THE OPTIONAL CONFIGURATION WIZARD MANAGER TO COMPLETE SETUP ................................... 24

APPENDIX: CLOUD CONNECTORS ........................................................................................................ 26

APPENDIX: CONFIGURE THE VM PLATFORM ........................................................................................ 27


3

Overview of Panzura Freedom Filer Installation on VMware ESXi

This document describes how to install and configure the Panzura Freedom Filer (Filer) on VMware ESXi. You can install the filer on ESXi version 5.5, 6.0, or 6.5.

The process consists of the following tasks. If you have completed all of the prerequisites and have all of the available information, the process of installation and configuration should take approximately one hour.

1. Install the Panzura Freedom Filer 7 OVA file in ESXi. - Download the file - Deploy the OVA file - Select the CPU and disk resources

2. Configure the filer in the Panzura setup wizard.

VM Requirements

The VM platform for the Filer must meet the following minimum requirements.

CPU cores: 16

RAM: 64-GB (thick provisioned/dedicated)

Datastore: 2TB SSD (thick provisioned/dedicated)

Preparation

Complete the following tasks before installing the filer.

1. Download Panzura filer build 11392 or higher Go to https://support3.panzura.com/ovf/ and sign in with username getpzos and password Pan5UR8. On the build page, click CloudController-vmcc.ova to download the file

2. Acquire a license token Obtain a license token from Panzura. You can skip this step if you have a secure environment with no external network connections.

Install the Panzura Filer on an ESXi host

The following procedure shows how to install Freedom 7 OVA file on ESXi 5.5, 6.0, or 6.5. The screen shots below are based on the VSphere web client version x.y.

Note: The user interface will vary based on the version of the ESXi host or VSphere web client you are using.

https://support3.panzura.com/ovf/


4

1. Log in to vSphere web client.

2. Select Home > Inventories > Host and Clusters.


5

3. Find your ESXi host by hostname or IP address. Right-click and select Deploy OVF Template, and click Allow to confirm that you want to deploy the template. In the following example, the ESXi host is 10.2.251.53.

4. Browse to the location of the OVF Template and Click Next. If you are deploying for first time, you might be prompted to download the Client Integration Plugin.


6

5. Accept the License Agreement and Click Next.

6. Specify a name and location for the Filer and Click Next.


7

6. Select the default minimal configuration and click Next.

7. Select Thick Provision Lazy Zeroed for the disk format, and select the destination datastore. Keep the default storage policy.


8

8. Keep the default network storage, and click Finish to complete the deployment of the OVF template.

When deployment is complete, task completion is indicated.

9. You can now power on the filer.

If you do not clearly see the login prompt after bootup is complete, press Enter to display the login prompt. This step may be required whenever the VM is rebooted.


9

Prepare to Configure the Filer

Add your values to this table before using the Panzura setup wizard to configure your Filer.

Item Your Value Comment

Filer IP address

IP address that was assigned to your Filer when you deployed the Filer VM.

Filer IP address

Name Email Title

Enter contact information for the Filer administrator.

Authentication credentials for the filer

Username

Password

Administrator username and password to access the Filer. Default is username admin and password admin.

Configuration Mode

Function that the filer will serve:

Master – The managing filer for a group of distributed filers. All licenses and configuration settings are added to the master filer and automatically propagate to the subordinate filers.

Subordinate – By default, all filers are set as subordinates, and are managed by the designated master.

HA-Global – The standby filer that can take over if an active filter in an HA-Global configuration becomes unavailable.

HA-Local – The standby filer that can take over if an active filter in the HA-Local configuration becomes unavailable.

Replacement filer – A filer that is configured to replace an existing master or subordinate filer.


10


Type of network deployment (one‐arm or inline):

One‐arm. In a one‐arm deployment, the Filer is connected to the network through a single interface. The Filer is not directly in the traffic path between the internal and external networks. Use this method only if the cloud and client traffic are on the same network.

Inline. This is the recommended deployment option, provided that the cloud traffic and client traffic are on different networks. In an inline deployment, the Filer is connected to the network by separate LAN and WAN interfaces.

Default is one-arm. In a VM environment network traffic is managed by the ESX server.

LAN (client side) addresses

DHCP or static addressing (best practice is to use static).

- For static addressing, need Filer IP address, subnet mask, and default gateway

- IP address of primary and

optional secondary DNS server

If static IP address is used refer to Appendix: Configure the VM platform for information on assigning the IP address to the VM.

Jumbo Frames Off Keep the default setting of OFF.

WAN (cloud) settings

For inline deployment only:

- IP address

- Subnet mask

- Default gateway

General Filer Settings

Filer hostname Hostname that resolves to an IP address.

Filer domain name Domain the Filer belongs to.

Location Physical location of the Filer, can be blank.

NTP server address Default is 0.pool.ntp.org

Master Filer information (if the Filer you are setting up is not a master):

Applies if the Filer is not a master; need master login information since the


11


- Master Filer hostname - Username and password to access the Web UI for the master Filer

subordinates will acquire Filer configuration and cluster settings from the master.

Hostname/IP address and filesystem name of the active Filer, if this Filer is an HA‐Local standby.

License Settings

License Token The token contains the license to operate, and additional storages services. During the setup the wizard will communicate with the license server to validate the token.

Cache Sizing

Current cloud storage managed by the Filer

The default is 1 TB. Estimated how much storage is currently will be moved to the cloud.

Percentage of the data that this site frequently accesses

This depends upon the use case typically 10% is a good starting point.

Virtual Disk Settings

For the automatic assignment option, ESX credentials are required: VM hostname/IP address, username, and password to access the host.

ESX credentials are needed if you want ESX server to provide a list of recommended datastores

You can use the manual assignment option, if disks have already been added your VM.

SSDs should be used for all storage. Hybrid capabilities are supported, but should be configured with assistance of Professional Services.

Cloud Provider Settings

Gather the information for your cloud provider that is listed in the following table.

Gather the information required for your cloud provider, as listed in the following table.

Item Your value

Amazon

S3 bucket path

S3 access key

S3 secret key


12

S3 bucket name

Cloud size (TB)

Cloud host IP address or hostname

AT&T

Folder name

User ID

Subtenant ID Subtenant ID:serviceclass=Policy Policy can be :serviceclass=policy1 or :serviceclass=policy2. Example: Subtenant ID:serviceclass=policy2 The policy types are case sensitive (they must be all lowercase). Refer to AT&T for information regarding policy1 and policy2.

Changing this setting requires a reboot of the Filer. Shared secret Atmos node nameYour Atmos (RMG) Resource Mgmt Group site node name

Shared secret

Cloud size (in TB)


CleverSafe

Path

User name

Password

Bucket

Cloud size (in TB)

Cleversafe accesser name or IP address

Dell EMC ‐ ECS

Path

User name

Password (secret access key)

Bucket

Cloud size (in TB)



13

Dell EMC ‐ Virtustream

Path

User name


Bucket

Cloud size (in TB)


EMC Atmos

Path

User

Shared secret

Subtenant ID

Cloud size (in TB)


Google

Path

User name

Password

Bucket name

Cloud size (in TB)


IBM Cloud Object Storage ‐ S3 Interface

Path

User name

Password

Vault

Hostname

IBM Cloud Object Storage ‐ Native Interface

Path

User name

Password

Vault

Hostname


14

IBM Cloud Object Storage ‐ Swift Interface

Path

User name

Password

Container

Hostname

AuthPath

IIJ

Path

User name


Bucket

Cloud size (in TB)


Microsoft Azure

Path

Storage account name

Access key

Container name

Cloud size (in TB)



15

Use the Setup Wizard to Set Up the Filer

The setup wizard includes all of the initial and basic setup to get the Filer up and running (password set, LAN/WAN, License, virtual disks for metadata and cache and cloud storage). The optional section allows you to enable file sharing protocols (SMB / NFS or both), to connect to Active Directory, and to mount shares. 1. Use a Chrome browser to connect to the Panzura VM using the IP address assigned to the Filer

during VM deployment. https://<ipaddress>

2. Log in with user name admin and password admin. You can ignore the field above Username.

3. Click Start.


16

4. Review and accept the End User License Agreement to continue the installation; include your name, email

address, and title. Click Next.

5. Review the required information and click Next. Note: NFS and SMB setup is optional.

6. Change the default password for the admin account to a secure password that meets your corporate policy for creating secure passwords.


17

7. Set the configuration for authentication key management and click NEXT. If this is the first Filer, configure it as the master. All additional filers must be configured as subordinates. The subordinate filers inherit cluster configuration settings, including licenses, encryption certification, authentication keys, SMB and NFS settings from the master.

Select the filer mode from the Configuration Mode dropdown. o Master. First filer you are configuring. o Subordinate. Additional filer that will be part of a cluster. o HA-Local. Stand-by filer to take over if the active is down. o HA-Global. Stand-by filer to take over if any filer in the cluster is down. o Replacement. To replace an existing master or subordinate filer.

Select from the Network Deployment Mode dropdown. o In-line. Recommended for deployments where independent ports are available for client

(LAN) and cloud (WAN) traffic, for example, in hardware appliances. o One-arm. recommended for software deployments where a single interface is shared for

client and cloud traffic, for example, ESC/VM deployments.

If the filer is configured as the master, select Configure as Key Master. Click Export . This will automatically download pairing.key file to your local system. You will need to upload the pairing.key file to all the subordinates in the cluster to securely communicate to the master.

If the Filer is configured as one of the other modes, click Upload to upload the same pairing.key file that was downloaded from the master.


18

8. Configure LAN (client) settings If you select Static for the interface mode, the following settings appear. Configure the following and click NEXT. - IP address - Subnet mask - Default gateway address - Primary DNS server - Secondary DNS server (optional)


19

If you select DHCP for the interface mode, the following settings appear. Configure the following and click NEXT.

- Primary DNS server - Secondary DNS server (optional)

8. General Settings Configure the following filer settings and click NEXT.

Hostname. Assign a hostname to the Filer.

Domain name. Enter the domain name for the Filer network.

Location: location of the Filer

NTP server: Enter a valid IP address / name of the NTP server used for time synchronization


20

9. License Settings Enter the license token provided by Panzura, and click NEXT. The system connects to the license portal to validate the token before continuing.

Note: For environments where there is no outside network connectivity, leave the License Token field blank.

10. Cache Sizing The settings in this section enable the wizard to determine appropriate datastores to select based on the storage needs. Enter the following and click NEXT.

Amount of data that will be moved to the cloud storage and managed by the Filer. This amount is the raw capacity of the Filer (data that is not compressed or deduplicated by the Filer).

Enter the percentage of the data is accessed frequently. A value of 10 (percent) is appropriate for many environments.


21

11. Virtual Disk Settings (File Host or Host) Panzura requires SSDs for metadata and cache storage, which can be assigned automatically or manually. The datastores must in RAID groups to spread the load across multiple drives and preserve access to data in the event of drive failures.

Automatic datastore configuration

With the Automatic option, the wizard presents recommended metadata and cache datastore disks based on the amount of data to be managed by the Filer entered in the previous page. For the wizard to discover and allocate the disks, select Automatic and enter the following.

ESXi host IP address

Username for access to the ESXi host

Password for access to the ESXi host

For the automatic option, the wizard presents the recommended sizes for metadata and cache storage. Do the following and click NEXT.

- Select the datastores for metadata and cache from the dropdown lists, and select the type of storage (SSD or HDD). If you have a hybrid disk configuration, make sure to use an SSD datastore for metadata, and select SDD for class.

- Modify the storage sizes only if needed.


22

Manual datastore configuration

For manual datastore configuration, complete the manual addition of hard disks (SSD/HDD) to the VM, as described in the Prerequisites section of this document. Select Manual to view a list of the disks that assigned to the VM, select the ones to use for metadata and cache, and click NEXT. You must select SSDs.

Select an entry for cache, and click ADD TO CACHE.

Select an entry for metadata, and click ADD TO CACHE.


23

12. Cloud Provider Enter the information for the cloud provider that the Filer will use to store the data in the cloud. Refer to the tables in the appendix for details on the available cloud providers and the information required for each. Note: If you would prefer to configure the cloud provider settings later, select NONE. Click NEXT.

The required settings depend on the cloud provider. The following screenshot shows the settings for Amazon.

13. Summary Review the settings you have configured. Click BACK if you need to make any changes, and click FINISH to complete the basic configuration.


24

The wizard closes, and the process of applying the configuration begins. You will see progress messages as the process proceeds. The process takes approximately 5 minutes. When complete, you are given the option to continue with the optional wizards. Click Continue with Optional Wizards for the optional setup, or click the Home button at the top of the page to go to the Home page without doing the additional setup.

Use the optional configuration wizard manager to complete setup

The configuration wizard manager opens when you click CONTINUE WITH OPTIONAL WIZARDS at the end of the setup wizard. The optional section allows you to enable file sharing protocols (SMB / NFS or both), to connect to Active Directory, and to mount shares.

1. Click START.

2. Verify the time settings and click NEXT.


25

3. Select the type of file systems to support and click NEXT.

4. Specify the Active Directory configuration.

— Enter the AD domain name and domain NETBIOS (optional).

— Search for the domain controller by name, or by clicking Search. After you click Search, the matching controllers are available in the domain controller list, and you can make a selection. Click Save Domain to save your selection.

— Click Join Domain. You are prompted to enter the user name and password for the domain controller. Confirm your selection to proceed with the join. When the join is complete, a message is presented. Current Active Directory Domain Controller Status: joined Click Next.

5. Click Apply and then Apply Changes. The configuration process is now complete, and you can proceed with operations.


26

Appendix: Cloud Connectors

The following table lists information about the available cloud providers.

Object Store Type Latest Tested Version

Connector Port (https) Notes

AT&T Public Date of PZOS release

AT&T 443 Prior to 6.3.1.0 use Atmos connector.

Azure Public Date of PZOS release

MS Azure 443 LRS only. ZRS, GRS and RA-GRS are not supported. Includes Azure Gov cloud

Dell/EMC - Atmos Private ECS 3.0 Atmos 443

Dell/EMC - ECS S3 Private ECS 3.0 Dell/EMC ECS

9021 (https) 9020 (http)

Prior to 6.3.1.0 use Amazon and disable dp.

Dell/EMC - Virtustream

Private TBD Dell Virtustream

443 Prior to 6.3.1.0 use Amazon and disable dp.

Google Public Date of PZOS release

Google 443 Regional Storage only. Multi-Regional Storage, Nearline and ColdLine are not supported.

IBM Cloud Object Storage - Native

Private 3.8.3.108 IBM Native 443 Second choice of the IBM choices per IBM. Must be 3.7 or higher.

IBM - Cloud Object Storage - S3

Public 3.8.3.108 IBM S3 443 First of the IBM choices per IBM. Object store must be running 3.7 or higher.

IBM - Cloud Object Storage - Swift

Public Date of PZOS release

IBM Swift 443 Third choice of the IBM choices per IBM.

IIJ Public Date of PZOS release

IIJ 443


27

Appendix: Configure the VM platform

Do these tasks after the VM is deployed.

Configure a static IP address for the filer, if needed

If your environment requires a static IP address or if DHCP is not available, acquire an unallocated IP address and set the IP address using the VM console. The sample screen shows the interface for vSphere 5.5.

Verify that the IP address is not being used in the environment by testing to see if you get a response:

ping <IP address>

Log in to the VM console and set the static IP address on the filer. Username: admin

Password: (password is admin)

cloudfs> enable

Password: (password is enable)

cloudfs cloudfs(config)# mgmt-if-mode Static (Static must be capitalized)

cloudfs(config)# mgmt-if-addr 10.2.3.4. 255.255.255.0 10.2.3.1 (Static IP,

Net. Mask, Gateway)

cloudfs (config)# exit

cloudfs# write memory

cloudfs# logout

Manually add hard disks (SSD / HDD) to the VM

In vSphere, navigate to VMs and Templates, and edit the settings for the deployed Filer VM.

1. Add one or more hard disks for metadata and one or more for cache. Make sure you select SSD disks.

2. Choose the capacity to fit your environment. The Panzura defaults are 100 GB for metadata and 200 GB for cache.


28

3. If you want to provision multiple disks of each type for resiliency, verify that the combined capacity meets your requirements. For example, if you are configuring two disks for a total of 100 GB metadata, each disk should be 50 GB.

Verify connection to the filer IP address

VM IP. Verify that the configured IP address is reachable from another system on the network.

ping <ip address>

Validate

Prior to starting the wizard, validate that following services are up and accessible for the filer to connect.

Cloud storage. Verify that the cloud storage exists, and connect with the provided credentials using a tool such as cyberduck or Cloudberry.

Use the ping command to verify that you can reach your NTP server, Active Directory server, and gateway.

Documents

Panzura Freedom 7 Deployment on ... - Cloud Object Storage · Cloud size (in TB) Cleversafe accesser name or IP address ... IBM Cloud Object Storage ... LAN/WAN, License, virtual