Learn about Application Templates

Contributors netapp-tonacki Download PDF of this page

The Application Templates service enables you to standardize resource creation in your working environments. For example, you can hard-code required parameters in a "volume template" that are later applied when a storage admin creates a volume. This can include required disk type, size, protocol, snapshot policy, cloud provider, and more. You can also turn on certain services, like Cloud Backup, for every created volume.

Templates make it easy for your storage admins to create volumes that are optimized for the workload requirements for each deployed application; such as databases, email, or streaming services. And it makes life easier for your storage architects knowing that each volume is created optimally for each application.

Features

Application Templates offer the following features and benefits:

  • Automates and improves the design and development of your infrastructure

  • Provides a single location to activate different NetApp Cloud services

  • Enforces template settings on created resources with the "drift" feature (future)

Pricing and licenses

The Application Templates feature requires no licensing and is free to use by all Cloud Manager users.

Templates enable you to apply a cloud service onto a created resources, for example, enable Cloud Backup on every volume. In this case there is a cost for using the Backup service and for the object storage space used by the backup files.

Available template actions

A template is a chain of "actions" that have some pre-defined values. You can build templates that include the following actions:

  • Create a Cloud Volumes ONTAP volume

  • Create an Azure NetApp Files volume

  • Enable Cloud Backup on created volumes (Cloud Volumes ONTAP volumes only)

  • Enable Cloud Compliance on created volumes

More actions will be added over time by NetApp.

How Application Templates work

The Application Templates service is made up of 3 parts. The available template "actions", the customized application template, and the deployed resource as a result of running the template. The following image shows the relationship between each component:

A diagram of the different users involved in creating and using application templates.

At a high level, Templates work like this:

  1. NetApp defines the available template "actions".

    For example, an "action" to create a Cloud Volumes ONTAP volume or an Azure NetApp Files volume.

  2. Your storage architect selects the "actions" they want use to create an Application Template, and then they hard-code certain values for the listed parameters.

    For example, they select high speed disks and a large amount of RAM for Cloud Volumes ONTAP volumes that will be used to carry the workloads for Oracle databases. And they require that backups are made for each volume.

  3. Your storage admins use the templates to create resources that are optimized for the application they will be used for.

    For example, they create a volume that will be used for an Oracle database by using the volume template created for databases.

Limitations

  • The Application Templates service is not supported in any of the Gov Cloud regions or in "dark" sites.

  • You can’t use a template to create a Cloud Volumes ONTAP volume on an existing aggregate. New volumes are created in a new aggregate.

  • You can’t use a template to create a volume on a Cloud Volumes ONTAP system that includes multiple Storage VMs (SVMs).