Skip to main content
Cloud Volumes ONTAP
All cloud providers
  • Amazon Web Services
  • Google Cloud
  • Microsoft Azure
  • All cloud providers

Deploy Cloud Volumes ONTAP with Quick create

Contributors netapp-manini
PDFs

You can deploy Cloud Volumes ONTAP in Amazon Web Services (AWS) and Microsoft Azure using Quick create for faster deployment in both single node and high availability (HA) configurations. This simplified process reduces deployment steps compared to the advanced method by automatically setting default values on a single page and minimizing navigation.

Before you begin

Before getting started, make sure you have the following:

  1. A Console agent that's up and running and associated with your project or workspace. Keep in mind that the Console agent needs to run at all times. For information, refer to:

  2. An understanding of the configuration that you want to use. Before you begin, choose a configuration and obtain networking information from your administrator. For information, refer to:

    AWS

    Planning your configuration in AWS

    Azure

    Planning your configuration in Azure

  3. Knowledge of the licensing requirements for Cloud Volumes ONTAP. For information, refer to:

    AWS

    Set up licensing in AWS

    Azure

    Set up licensing in Azure

  4. DNS and Active Directory for CIFS configurations. For information, refer to:

    AWS

    Networking requirements in AWS

    Azure

    Networking requirements in Azure

Steps

  1. From the left navigation menu, select Storage > Management.

  2. On the Canvas page, click Add System and follow the prompts.

  3. Select your cloud provider (Amazon Web Services or Microsoft Azure) > Cloud Volumes ONTAP/Cloud Volumes ONTAP HA > Add new. The Quick create option is selected by default.

    Sample screenshots of the Quick create option
    AWS

    AWS Quick Create

    Azure

    Azure Quick Create

System details

  1. Cloud provider account/credentials: The account and subscription details are automatically populated based on your Console agent. If you have multiple accounts or subscriptions, select the one you want to use. If a Console agent is unavailable, you'll be prompted to create a Console agent.

  2. Name: Enter a name for your Cloud Volumes ONTAP system (also called the cluster name). The Console uses the system (cluster) name to name the Cloud Volumes ONTAP system and the VM instance. It also uses the name as the prefix for the predefined security group, if you select that option.

  3. ONTAP credentials: These are the credentials for the Cloud Volumes ONTAP cluster administrator account. You can use these credentials to connect to Cloud Volumes ONTAP through ONTAP System Manager or the ONTAP CLI. You can keep the default admin user name or change it to a custom user name.

  4. Tags: Tags are the metadata for your AWS or Azure resources. The Console adds the tags to the Cloud Volumes ONTAP instance and each resource associated with the instance. You can add up to 15 tags from the user interface when creating a Cloud Volumes ONTAP system, and then you can add more after it's created. For more information, refer to:

    AWS

    AWS Documentation: Tagging your Amazon EC2 Resources.

    Azure

    Azure Documentation: Tag resources.

Deployment and configuration

  1. Deployment type/topology: Select the deployment type that you want to use, single node, high availability (HA) in a single availability zone (AZ), or HA in multiple AZs.

  2. Network configuration: Enter the network information that you recorded in the planning worksheet for regions, VNets, and subnets.

    1. Region: By default, the region of the associated cloud account with the resources is selected.

    2. Availability zone: You can select the availability zone based on the deployment type you choose, and if the selected region supports the availability zone.

    3. Subnet: Select a subnet for the region.

      For AWS

      VPC: For AWS, enter a VPC for the region with a subnet as per your planned

      AWS High Availability

      If you selected an HA configuration, enter the following information:

      HA in single AZ

      1. Mediator Access: Specify the mediator access information. The mediator is a separate instance that monitors the health of the HA pair and provides quorum in case of a failure. Provide the key pair name to enable the mediator instance to connect to the AWS EC2 service, and select the connection method.

      HA in multiple AZ

      1. Availability zones and mediator: Select the availability zones (AZs) for each node and the mediator and the corresponding subnets where you want to deploy the Cloud Volumes ONTAP HA pair.

      2. Floating IPs: If you chose multiple AZs, specify the floating IP addresses for the NFS and CIFS services and cluster and SVM management. The IP addresses must be outside of the CIDR block for all VPCs in the region. For additional details, refer to AWS networking requirements for Cloud Volumes ONTAP HA in multiple AZs.

      3. Mediator Access: Specify the mediator access information. The mediator is a separate instance that monitors the health of the HA pair and provides quorum in case of a failure. Provide the key pair name to enable the mediator instance to connect to the AWS EC2 service, and select the connection method.

      4. Route Tables: If you chose multiple AZs, select the route tables that include routes to the floating IP addresses. If you have more than one route table, it is important to select the correct route tables. Otherwise, some clients might not have access to the Cloud Volumes ONTAP HA pair. For more information about route tables, refer to the AWS Documentation: Route Tables.

      Charging and Services

      Marketplace Subscription: In AWS, select the AWS marketplace subscription you want to use with this Cloud Volumes ONTAP system.

      For Azure

      VNET: For Azure, select the required VNET.

Charging and Services

  1. License: Select the license type you want to use with this Cloud Volumes ONTAP system. You can choose from Professional, Essentials, and Freemium licenses. For information about different licenses, refer to Learn about Cloud Volumes ONTAP licenses.

  2. Data services and features: Keep the services enabled or disable the services you don't want to use with Cloud Volumes ONTAP.

  3. NetApp Support Site account: If you have multiple accounts, select the one you want to use.

  4. Check or edit the details you entered, and then click Create.

In Azure, the Overview section displays the resources that will be allocated when the deployment process completes.

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

After you finish

The Console deploys the Cloud Volumes ONTAP system. You can track the progress on the Audit page.

If you experience any issues deploying the Cloud Volumes ONTAP system, review the failure message. You can also select Re-create environment on the system to continue with the deployment using the Advanced mode wizard.

Caution After the deployment process completes, do not modify the system-generated Cloud Volumes ONTAP configurations in the AWS or Azure cloud portal, especially the system tags. Any changes made to these configurations may lead to unexpected behavior or data loss.
Related links