Cloud Manager 3.6.2 (2 Jan 2019)
Cloud Manager 3.6.2 includes new features and enhancements.
AWS spread placement group for Cloud Volumes ONTAP HA in a single AZ
When you deploy Cloud Volumes ONTAP HA in a single AWS Availability Zone, Cloud Manager now launches the two HA nodes and the mediator in an AWS spread placement group. The placement group reduces the risk of simultaneous failures by spreading the instances across distinct underlying hardware.
|This feature improves redundancy from a compute perspective and not from disk failure perspective.|
Cloud Manager requires new permissions for this feature. Ensure that the IAM policy that provides Cloud Manager with permissions includes the following actions:
You can find the entire list of required permissions in the latest AWS policy for Cloud Manager.
Ransomware attacks can cost a business time, resources, and reputation. Cloud Manager now enables you to implement the NetApp solution for ransomware, which provides effective tools for visibility, detection, and remediation.
Cloud Manager identifies volumes that are not protected by a Snapshot policy and enables you to activate the default Snapshot policy on those volumes.
Snapshot copies are read-only, which prevents ransomware corruption. They can also provide the granularity to create images of a single file copy or a complete disaster recovery solution.
Cloud Manager also enables you to block common ransomware file extensions by enabling ONTAP’s FPolicy solution.
New data replication policies
Cloud Manager includes five new data replication policies that you can use for data protection.
Three of the policies configure disaster recovery and long-term retention of backups on the same destination volume. Each policy provides a different backup retention period:
Mirror and Backup (7 year retention)
Mirror and Backup (7 year retention with more weekly backups)
Mirror and Backup (1 year retention, monthly)
The remaining policies provide more options for long-term retention of backups:
Backup (1 month retention)
Backup (1 week retention)
Simply drag-and-drop a working environment to select one of the new policies.
Volume access control for Kubernetes
You can now configure the export policy for Kubernetes Persistent Volumes. The export policy can enable access to clients if the Kubernetes cluster is in a different network than the Cloud Volumes ONTAP system.
You can configure the export policy when you connect a working environment to a Kubernetes cluster and by editing an existing volume.
Cloud Manager 3.6.1 (4 Dec 2018)
Cloud Manager 3.6.1 includes new features and enhancements.
Support for Cloud Volumes ONTAP 9.5 in Azure
Cloud Manager now supports the Cloud Volumes ONTAP 9.5 release in Microsoft Azure, which includes a preview of high-availability (HA) pairs. You can request a preview license for an Azure HA pair by contacting us at ng-Cloud-Volume-ONTAPemail@example.com.
For more details about the 9.5 release, see the Cloud Volumes ONTAP 9.5 Release Notes.
New Azure permissions required for Cloud Volumes ONTAP 9.5
Cloud Manager requires new Azure permissions for key features in the Cloud Volumes ONTAP 9.5 release. To ensure that Cloud Manager can deploy and manage Cloud Volumes ONTAP 9.5 systems, you should update your Cloud Manager policy by adding the following permissions:
"Microsoft.Network/loadBalancers/read", "Microsoft.Network/loadBalancers/write", "Microsoft.Network/loadBalancers/delete", "Microsoft.Network/loadBalancers/backendAddressPools/read", "Microsoft.Network/loadBalancers/backendAddressPools/join/action", "Microsoft.Network/loadBalancers/frontendIPConfigurations/read", "Microsoft.Network/loadBalancers/loadBalancingRules/read", "Microsoft.Network/loadBalancers/probes/read", "Microsoft.Network/loadBalancers/probes/join/action", "Microsoft.Network/routeTables/join/action" "Microsoft.Authorization/roleDefinitions/write", "Microsoft.Authorization/roleAssignments/write", "Microsoft.Web/sites/*" "Microsoft.Storage/storageAccounts/delete", "Microsoft.Storage/usages/read",
You can find the entire list of required permissions in the latest Azure policy for Cloud Manager.
Cloud Provider Accounts
It’s now easier to manage multiple AWS and Azure accounts in Cloud Manager by using Cloud Provider Accounts.
In previous releases, you needed to specify cloud provider permissions for each Cloud Manager user account. The permissions are now managed at the Cloud Manager system level by using Cloud Provider Accounts.
When you create a new working environment, you simply select the account in which you want to deploy the Cloud Volumes ONTAP system:
When you upgrade to 3.6.1, Cloud Manager automatically creates Cloud Provider Accounts for you, based on your current configuration. If you have scripts, backwards compatibility is in place so nothing breaks.
Enhancements to the AWS Cost report
The AWS Cost report now provides more information and is easier to set up.
The report breaks down the monthly resource costs associated with running Cloud Volumes ONTAP in AWS. You can view monthly costs for compute, EBS storage (including EBS snapshots), S3 storage, and data transfers.
The report now shows cost savings when you tier cold data to S3.
We also simplified how Cloud Manager obtains cost data from AWS.
Cloud Manager no longer needs access to billing reports that you store in an S3 bucket. Instead, Cloud Manager uses the Cost Explorer API. You just need to ensure that the IAM policy that provides Cloud Manager with permissions includes the following actions:
"ce:GetReservationUtilization", "ce:GetDimensionValues", "ce:GetCostAndUsage", "ce:GetTags"
These actions are included in the latest NetApp-provided policy. New systems deployed from NetApp Cloud Central automatically include these permissions.
Support for new Azure regions
You can now deploy Cloud Manager and Cloud Volumes ONTAP in the France Central region.
Cloud Manager 3.6 (4 Nov 2018)
Cloud Manager 3.6 includes a new feature.
Using Cloud Volumes ONTAP as persistent storage for a Kubernetes cluster
Cloud Manager can now automate the deployment of NetApp Trident on a single Kubernetes cluster so you can use Cloud Volumes ONTAP as persistent storage for containers. Users can then request and manage Persistent Volumes using native Kubernetes interfaces and constructs, while taking advantage of ONTAP’s advanced data management features without having to know anything about it.