Flexible Deployments of IsilonSD Clusters: Frequently Asked Questions

Note: This topic is part of the EMC IsilonSD Edge: Frequently Asked Questions.

 

This collection of frequently asked questions applies to flexible deployments that are supported by IsilonSD Edge.

 

What is a flexible deployment?

A flexible deployment allows you to configure your IsilonSD cluster using one or more ESXi hosts using a lower hardware footprint. You can choose either VMFS or vSAN as your storage option for such deployments.

 

How are drives mapped to the VMware ESXi hosts in a flexible deployment?

  • Direct attached disks without RAID
  • Direct attached disks with RAID
  • Direct attached disks with vSAN
  • SAN LUNs
  • iSCSI LUNs

 

Which versions of IsilonSD Management Server and OneFS support the flexible deployments?

IsilonSD Management Server 1.0.2 and later and OneFS 8.1.x.

 

What are the flexible deployment configurations supported for an IsilonSD cluster?

For the VMFS storage type, the following datastore configuration is available to support flexible deployment of IsilonSD clusters:

  • One datastore per ESXi host: One datastore is used for all the nodes (data disks, boot disks, and journal disks) that are deployed on that ESXi host.
  • One datastore per OneFS virtual node: Each OneFS virtual node has its own dedicated datastore.
  • One datastore per virtual data disk: A separate datastore is assigned for each OneFS disk. A 1:1 mapping is maintained between the OneFS disk and VMFS datastore.

The vSAN storage type allows one datastore per ESXi host to support a flexible deployment of IsilonSD clusters.

 

What is the recommended IsilonSD cluster deployment configuration?

We highly recommend deploying an IsilonSD cluster using the configuration that supports one datastore per virtual data disk using VMFS storage for high availability and for production deployments.

 

Has a new license been introduced to support the flexible deployment of IsilonSD clusters?

A new license, EDGE-FLEX, is available with IsilonSD Management Server version 1.0.2 or later to support flexible deployments of IsilonSD clusters. The FREE license is enhanced to support all of the flexible configurations.

 

What are the differences between the FREE, EDGE, and EDGE-FLEX licenses?

A FREE license supports all of the configurations including the flexible configurations. An EDGE  license supports multiple hosts (1:1 mapping) with multiple datastores (1:1 mapping) using VMFS storage. An EDGE-FLEX license supports all of the configurations.

 

Is EDGE-FLEX a paid license?

Yes, EDGE-FLEX is a paid license.

 

What are the maximum number of nodes supported with the FREE, EDGE, and EDGE-FLEX licenses?

All the three licenses support a maximum of six nodes.

 

What are the other IsilonSD cluster deployment requirements for the FREE, EDGE, and EDGE-FLEX  licenses?

  • Maximum cluster capacity: 36 TB
  • Maximum CPUs per node: 16
  • 4, 6, or 12 data disks
  • Maximum memory per node: 256 GB


Are all the OneFS features supported with the FREE, EDGE, and EDGE-FLEX licenses?

With the free license, all the OneFS features except CloudPools and SmartLock are supported. All the OneFS features are supported with the EDGE and EDGE-FLEX licenses.

 

Why do I see a warning message when I try to deploy an IsilonSD cluster using a flexible deployment configuration?

Flexible deployments do not support the failover capability and also do not guarantee high availability. So you will see the following message when you try to deploy an IsilonSD cluster using any flexible deployment method:

 

ifs_g_isd_mttdl_reminder.pngNote: This topic is part of the IsilonSD Edge - Isilon Info Hub.

 

After deploying an IsilonSD cluster, can I change my cluster deployment type?

No. Back up your data and redeploy the cluster using an alternate deployment type.

 

Where can I find all the details about flexible deployments of IsilonSD Edge?

Refer to the latest version of the IsilonSD Edge with IsilonSD Management Server Installation and Administration Guide for the relevant details.