OnCommand Cloud Manager New Features

Version 3.4.5 Policy changes required for Azure

Cloud Manager 3.4.5 includes several new features and enhancements.

Support for RHEL 7.4 and CentOS 7.4

Cloud Manager is now supported on Red Hat Enterprise Linux 7.4 and CentOS 7.4.

Cloud Manager can now enable programmatic deployments

In previous releases, you had to manually enable programmatic deployments of ONTAP Cloud from the Azure Marketplace for each Azure subscription. Cloud Manager can now do this for you. To enable programmatic deployments for an Azure subscription, Cloud Manager requires the following permissions: "Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/read" "Microsoft.MarketplaceOrdering/offertypes/publishers/offers/plans/agreements/write"

You should update the role definition for the Cloud Manager Operator role to include these permissions.

You can find the entire list of required permissions in the policies provided by NetApp.

Changes coming soon

NetApp occasionally announces changes that will be made in upcoming releases of Cloud Manager and ONTAP Cloud so that you are provided advance notice.

Deprecation of EC2 instance types

In June 2018, all versions of ONTAP Cloud will no longer support several EC2 instance types. Existing ONTAP Cloud systems running these instance types will continue to operate normally; however, NetApp strongly recommends changing to a different instance type.

To review pricing differences between instance types and NetApp licenses, go to the AWS Marketplace for single-node ONTAP Cloud systems and for ONTAP Cloud HA pairs.

Instance type no longer supported Recommended instance type
c3.2xlarge m4.xlarge
c4.2xlarge m4.2xlarge
m3.xlarge m4.xlarge
m3.2xlarge m4.2xlarge
r3.xlarge m4.xlarge
r3.2xlarge m4.2xlarge

M3 and R3 instance types are not supported with ONTAP Cloud data tiering and enhanced performance, so moving to the M4 and R4 instance types allows you to take advantage of those features.

New permissions required for ONTAP Cloud 9.4

Cloud Manager will require new permissions for key features in the upcoming ONTAP Cloud 9.4 release. To ensure that your Cloud Manager systems are ready to deploy and manage ONTAP Cloud 9.4 systems, we recommend that you update your Cloud Manager policy now by adding the following permissions:

You can find the entire list of required permissions in the policies provided by NetApp.

Version 3.4.4 Policy changes required for Azure and AWS

Cloud Manager 3.4.4 includes several new features and enhancements.

Support for Azure France Central region

Cloud Manager and ONTAP Cloud are now supported in the France Central region.

Enhancement to default disk size selection in AWS

Cloud Manager now chooses larger disks as ONTAP Cloud systems grow in AWS.

When Cloud Manager creates new aggregates for ONTAP Cloud systems in AWS, it steadily increases the disk size in an aggregate, as the number of aggregates in the system increases. Cloud Manager does this to ensure that you can utilize the system’s maximum capacity before it reaches the maximum number of data disks allowed by AWS.

For example, Cloud Manager might choose the following disk sizes for aggregates in an ONTAP Cloud Premium or BYOL system:

Aggregate number Disk Size Max aggregate capacity
1 500 MB 3 TB
4 1 TB 6 TB
6 2 TB 12 TB

You can choose the disk size yourself by using the advanced allocation option.

Version 3.4.2

Cloud Manager 3.4.2 includes several new features and enhancements.

Enhancements to the Cloud Storage Automation Report

The Cloud Storage Automation Report identifies several savings opportunities, including savings for unattached EBS volumes and unassociated snapshots. Starting in version 3.4.2, Cloud Manager now shows you the list of those volumes and snapshots and enables you to delete them.

The following image shows how you can access the list of unattached volumes and unassociated snapshots:

The following image shows an example of how you can delete unattached EBS volumes:

Support for multiple AWS accounts when using an IAM role

Cloud Manager now enables you to choose the AWS account to use when launching an ONTAP Cloud system:



This feature is supported if you associated the Cloud Manager instance with an IAM role.

Before you can choose from multiple AWS accounts, you must first delegate access across those accounts.

Adding additional AWS accounts to Cloud Manager

Support for multiple Azure accounts

Cloud Manager now enables you to choose the Azure subscription to use when deploying an ONTAP Cloud system:



Before you can choose from multiple Azure subscriptions, you must first bind the Active Directory service principal to multiple Azure subscriptions.

Granting Azure permissions to Cloud Manager

Note: This change is possible because Cloud Manager no longer associates user accounts with specific Azure subscriptions. Instead, Cloud Manager obtains the list of Azure subscriptions that are bound to the Active Directory service principal.

Security group selection for the HA mediator

You can now choose an existing security group for the HA mediator when you deploy a new ONTAP Cloud HA system. Cloud Manager always created this security group in previous releases.

Version 3.4.1

Cloud Manager 3.4.1 includes several new features and enhancements.

Cloud Storage Automation

Cloud Manager can now analyze your cloud storage to show you savings opportunities, data protection enhancements, and operations that can optimize the cloud storage associated with your AWS account. For example, Cloud Manager identifies savings opportunities for unassociated EBS volumes and snapshots, the EBS volumes that impact your recovery point objective, and EBS volumes that are running out of space.

Improved reliability when upgrading ONTAP Cloud systems

Cloud Manager now leverages Amazon S3 Transfer Acceleration when upgrading ONTAP Cloud software. This enhancement improves the reliability of downloading the software image, which reduces the chances of timeouts and proxy failures.

Resource group naming in Azure

You can now specify the name of the Azure resource group that Cloud Manager creates for an ONTAP Cloud system when you create a new working environment.

Support for additional AWS regions

Cloud Manager and ONTAP Cloud are now supported in the AWS France region.

Support for Azure US Gov regions

You can now deploy Cloud Manager and ONTAP Cloud BYOL in the following Azure regions:

To deploy Cloud Manager in these regions, you must create a CentOS 7.3 virtual machine from the Azure Marketplace, download the Cloud Manager installer from the NetApp Support Site, and then install the software. After Cloud Manager is running, you can deploy ONTAP Cloud BYOL systems in the these regions just like any other region.

Improvement when replicating data from on-premises ONTAP systems

When you replicate data from an on-premises ONTAP system, Cloud Manager now associates the LIF to the default IPspace.

Version 3.4

OnCommand Cloud Manager is now integrated with NetApp Cloud Data Services

NetApp Cloud Data Services is a suite of data-driven services that allows you to run critical applications in the cloud, create automated DR sites, back up your SaaS data, and effectively migrate and control data across multiple clouds leveraging NetApp's prominent data management expertise and technologies.

Cloud Manager's integration with NetApp Cloud Data Services provides several benefits, including a simplified deployment experience, a single location to view and manage multiple Cloud Manager systems, and centralized user authentication.

With centralized user authentication, you can use the same set of credentials across Cloud Manager systems and between Cloud Manager and other data services, such as Cloud Sync. It's also easy to reset your password if you forgot it.

You can keep using your existing Cloud Manager systems as is, but if you would like to use this new experience, you can deploy a new Cloud Manager 3.4 system from NetApp Cloud Data Services and then discover any existing ONTAP Cloud systems from the new Cloud Manager system.

Version 3.3.4

OnCommand Cloud Manager 3.3.4 includes bug fixes.

Version 3.3.3

OnCommand Cloud Manager 3.3.3 includes several new features and enhancements.

Support for installing Cloud Manager in the IBM Cloud

Cloud Manager software is now supported in the IBM Cloud. You can download the software from the NetApp Support Site and install it on an existing host. Cloud Manager must have networking connections to other networks so it can deploy ONTAP Cloud in AWS or Azure and so it can discover ONTAP clusters.

Management of ONTAP in the IBM Cloud

Cloud Manager supports discovery of ONTAP clusters in the IBM Cloud. After you discover an ONTAP cluster, you can provision storage create volumes on existing aggregates and replicate data to and from the cluster.

Selection of IAM roles when launching ONTAP Cloud in AWS

In previous releases, Cloud Manager automatically created the required IAM roles for ONTAP Cloud in AWS. Now when you launch a new ONTAP Cloud system, you can select existing roles in your account that meet policy requirements or you can let Cloud Manager create the roles for you. Click here to see policy requirements.

Version 3.3.2

OnCommand Cloud Manager 3.3.2 includes several new features and enhancements.

ONTAP Cloud Notification Report

Cloud Manager can now email users an ONTAP Cloud Notification Report. Cloud Manager sends the report when an action requires your approval and when Cloud Manager automatically performs capacity-related actions, such as purchasing additional disks. This feature is automatically enabled when upgrading to Cloud Manager 3.3.2. You can change the setting by editing Cloud Manager user accounts.

Automatic ONTAP Cloud updates when creating new systems

When you deploy new ONTAP Cloud systems, Cloud Manager can now automatically update the software during working environment creation if a newer Release Candidate, General Availability, or patch release is available for the selected version. For example, the update occurs if you select ONTAP Cloud 9.2 RC1 and ONTAP Cloud 9.2 GA is available. The update does not occur from one release to another—for example, from 9.2 to 9.3. This feature is automatically enabled when upgrading to Cloud Manager 3.3.2. You can change the setting in the Settings page.

Support for ONTAP Cloud storage tiering in the AWS GovCloud (US) region

You can now use EBS as a performance tier and AWS S3 as a capacity tier in the AWS GovCloud (US) region when choosing the disk type for ONTAP Cloud volumes.

Azure virtual machine types supported with new ONTAP Cloud systems

When you deploy new ONTAP Cloud systems in Azure, you can choose from several v2 virtual machine types. v1 VM types are no longer supported with new systems.

Fixed issue

The following known issue was fixed in this release: ONTAP Cloud upgrades might not complete properly

Version 3.3.1 Policy changes required for Azure

OnCommand Cloud Manager 3.3.1 includes several new features and enhancements.

General Availability release of ONTAP Cloud 9.2

Cloud Manager now supports the General Availability release of ONTAP Cloud 9.2.

Support for 2 TB and 4 TB disks in Azure

You can now choose 2 TB and 4 TB disks when provisioning storage for ONTAP Cloud in Azure. These disk sizes enable aggregates up to 24 TB and 48 TB, respectively.

Increased license capacity limit in Azure

ONTAP Cloud Premium and BYOL now support up to 124 TB of raw capacity in Azure.

Support for Azure managed disks

When Cloud Manager deploys new ONTAP Cloud systems in Azure, it purchases Azure managed disks for the systems. All existing systems continue to use Azure unmanaged disks.

iSCSI supported with additional Azure VM types

ONTAP Cloud now supports iSCSI when you choose the DS3 or DS3_v2 virtual machine type.

Vormetric support

ONTAP Cloud for AWS now support Vormetric Data Security Manager when using ONTAP Cloud-managed encryption. The supported OS version is Vormetric 6.0. For instructions, see NetApp KB article 000033069.

Azure policy changes required for Cloud Manager

The Cloud Manager Azure policy was updated for the 3.3.1 release because Cloud Manager needs additional privileges. You must use the new policy to update the custom role that you assigned to the Active Directory service principal. Cloud Manager now uses the following actions to obtain information about regions and to manage availability sets and Azure managed snapshots for ONTAP Cloud:

Version 3.3 IAM policy changes required

OnCommand Cloud Manager 3.3 includes several new features and enhancements.

Preconfigured packages for ONTAP Cloud

You can now deploy ONTAP Cloud faster by selecting a preconfigured package. When you create a working environment, you can choose a preconfigured system that matches your workload requirements:

Changes specific to AWS

Cloud Manager enables several new features introduced with ONTAP Cloud 9.2 for AWS. See the ONTAP Cloud Release Notes for additional information.

Support for storage tiers

You can reduce your storage costs by using EBS as a performance tier and AWS S3 as a capacity tier:

A tiered storage configuration is a good choice if your data changes frequently or if you use ONTAP Cloud for disaster recovery or long-term retention:

Deploying and managing ONTAP Cloud systems: Choosing an AWS disk type

Enhanced write performance

Write performance for ONTAP Cloud has been improved. The enhancements are supported with ONTAP Cloud Standard, Premium, BYOL, and with most instance types.

Note: Write performance enhancements are not supported with ONTAP Cloud Explore and with M3 and R3 instance types when using Standard and Premium.

Support for Provisioned IOPS SSDs

You can now use Provisioned IOPS SSDs as an underlying AWS disk for ONTAP Cloud. These SSDs are a good choice for critical applications that require the highest performance at a higher cost.

Note: These disks are supported in the Storage System View only.

Deploying and managing ONTAP Cloud systems: Choosing an AWS disk type

Support for 16 TB disks

You can now choose 16 TB EBS disks when provisioning storage for ONTAP Cloud. This enables aggregates up to 96 TB.

Note: Total capacity limits for ONTAP Cloud systems remain the same.

Support for the m4.4xlarge instance type

You can now launch ONTAP Cloud instances in AWS using the m4.4xlarge instance type with ONTAP Cloud Premium and BYOL.

Additional internet connection methods for the HA mediator

When launching an ONTAP Cloud HA pair, you can now specify whether the HA mediator should use a public IP address, proxy, or NAT instance for outbound internet access.

Changes specific to Azure

Additional disks and regions are now supported in Azure.

Support for 12 disks per aggregate

ONTAP Cloud systems now support up to 12 disks per aggregate. This enables aggregates up to 12 TB.

Note: Total capacity limits for ONTAP Cloud systems remain the same.

Support for additional regions

You can now deploy Cloud Manager and ONTAP Cloud systems in the following Azure regions:

Related information

Find the Release Notes for your version of ONTAP Cloud

Version 3.2.1

ONTAP Cloud HA enhancement

When you deploy ONTAP Cloud HA configurations in multiple AWS Availability Zones, Cloud Manager now creates a separate set of NFS and CIFS IP addresses that you can use for client access from outside the VPC. These IP addresses are static—they cannot migrate between nodes when failures occur. You must manually remount volumes to clients using the IP address on the other node. You can identify the correct IP address by selecting a volume and clicking Mount Command.

Change to Cloud Sync trial period

The Cloud Sync trial period was reduced to 14 days.

Fixed issues

The following known issues were fixed:

Version 3.2 IAM policy changes required

Support for ONTAP Cloud HA in a single Availability Zone

A new high availability (HA) deployment model enables you to deploy an ONTAP Cloud HA configuration in a single AWS Availability Zone (AZ). This configuration, which uses private IP addresses instead of floating IP addresses, ensures high availability of your data if an instance that runs an ONTAP Cloud node fails. It does not protect against AZ failures. All data is natively accessible from outside of the VPC.

Support for adding private IP addresses to an HA configuration using documented instructions

Cloud Manager documentation now includes instructions for adding private IP addresses to an ONTAP Cloud HA configuration deployed in multiple Availability Zones. Adding private IPs enables NFS and CIFS data access from outside of the VPC. However, the private IP addresses do not automatically fail over between nodes if a failure occurs. You must manually remount volumes to clients using the IP address on the other node.

Integration with the Data Fabric Cloud Sync service

You can now sync ONTAP volumes to an AWS S3 bucket by integrating a working environment with the NetApp Data Fabric Cloud Sync service. You can then use the synced data as a secondary copy or for data processing using AWS services like EMR and Redshift.
The integration works with ONTAP Cloud working environments, as well as ONTAP clusters that are on-premises or part of a NetApp Private Storage (NPS) configuration.

Amazon EBS encryption using customer-managed CMKs

When you set up an ONTAP Cloud system in AWS, you can choose AWS-managed encryption using the AWS Key Management Service (KMS). You can now choose the customer master key (CMK) that you want to use with an ONTAP Cloud system. The CMK can be an AWS-managed CMK or a customer-managed CMK.

Support for new AWS regions

You can now launch Cloud Manager and ONTAP Cloud instances in the Canada (Central) and EU (London) regions.

Support for dedicated EC2 instances

When you select an EC2 instance type for ONTAP Cloud, you can now specify whether it is a shared instance or a dedicated instance.

Support for new ONTAP Cloud configurations

Cloud Manager now verifies connectivity to VPCs

Immediately after you create an AWS working environment, Cloud Manager launches a test instance in the specified VPC to verify connectivity. If successful, Cloud Manager immediately terminates the instance and then starts deploying the ONTAP Cloud system. If Cloud Manager cannot verify connectivity, creation of the working environment fails. The test instance is either a t2.nano (for default VPC tenancy) or m3.medium (for dedicated VPC tenancy).

New option to recreate failed working environments

If Cloud Manager fails to create a working environment, you can now use the Recreate Environment action to return to the wizard and modify the request.

Support for adding and editing more AWS tags

After you launch an ONTAP Cloud instance, you can now specify up to 20 AWS tags and you can edit the tags, as well.

Version 3.1

ONTAP Cloud 9.1 support

Support for Microsoft Azure coming soon

Storage enhancements

Nondisruptive upgrades for ONTAP Cloud HA configurations

Additional features and enhancements