Deployment overview for Cloud Volumes ONTAP in Azure
For deploying Cloud Volumes ONTAP, you first need to know about your Azure subscription and Cloud Volumes ONTAP licenses. You must also verify that you have a NetApp Console agent created for your Azure subscription and organization. Much of the information in this topic needs to be performed as part of your Console setup before you begin to even deploy Cloud Volumes ONTAP.
| Task | Description | Reference | Notes for private mode deployments |
|---|---|---|---|
Create a Console agent |
If you don't have a Console agent yet, create one before deploying Cloud Volumes ONTAP. |
Refer to the Console setup guide: |
If deploying in a subnet with no internet access, manually install the Console agent and access the NetApp Console user interface that's running on that Console agent. Refer to the Console setup guide: |
Plan your configuration |
The Console offers preconfigured packages that match your workload requirements, or you can create your own configuration. If you choose your own configuration, you should understand the options available to you. |
You need to have similar planning considerations for private mode deployments. |
|
Set up your networking |
|
Outbound internet access for AutoSupport is not required. All other networking requirements remain the same. |
|
Deploy Cloud Volumes ONTAP from the Console |
When you have performed all prerequisites, you can complete the steps in the wizard to deploy Cloud Volumes ONTAP in Azure. |
Before beginning the deployment, ensure that you have purchased a Cloud Volumes ONTAP license from NetApp. Private mode deployments require a node-based BYOL licenses. Marketplace subscriptions are not supported for charging your Cloud Volumes ONTAP usage. Obtain the license file from NetApp, and upload it during deployment. Refer to: |