Skip to main content
NetApp Knowledge Base

OTV 10- What is storage backend global and local scope?

  1. Last updated
  2. Save as PDF
Views:
372
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • ONTAP Tools for VMware vSphere (OTV) 10.x
  • VMware vSphere

Answer

What is ONTAP tools for VMware vSphere Storage backends?

  • This consists of the underlying storage infrastructure that the VMware vCenter Elastic Sky X Integrated (ESXi) host uses to store virtual machine files, data, and other resources.
  • Storage backends allow the ESXi host to access and manage persistent data, providing the required storage capability and performance for a virtualized environment.
  • In ONTAP Tools for VMware vSphere 10, the terms "Local Scope" and "Global Scope" refer to how a storage backend (e.g., an ONTAP cluster) is added and managed within the VMware vSphere environment.
  • In OTV 9, to use VASA Provider, storage backends had to be added using the storage cluster management lif, which was called "cluster scope". 
  • In OTV 10, this requirement limitation was removed

Global Scope Defined in ONTAP Tools Manager:

  • Global scope refers to settings, configurations, or objects that are accessible and applicable across the entire ONTAP Tools for VMware environment.
  • This scope makes the storage backend accessible to all vCenter servers that are configured to use ONTAP Tools.
  • This is particularly useful in multitenant environments where multiple vCenter servers need to access the same storage backend.
  • Global storage backends, available only with ONTAP cluster credentials, are onboarded through the ONTAP tools Manager interface that is accessed via the URL: https://OTV-IP:8443/virtualization/ui
  • These storage backends can be added with minimal privileges to enable the discovery of essential cluster resources needed for virtual volumes (vVols) management.
  • Global clusters are ideal for multitenancy scenarios where an SVM user is added locally for vVols management.
  • This means that the configurations set at this level can be utilized by all users and virtual machines (VMs) within the environment.

Examples:

  • Global Policies: Storage policies that apply to all datastores managed by ONTAP Tools.
  • Global Settings: Network configurations, authentication settings, or general preferences that affect the entire system.
  • Global Resources: Storage resources or templates that are available to all VMs and users.
  • ONTAP storage clusters are added globally and then automatically mapped to vCenter Server instances.
  • Storage Virtual Machines (SVM) shouldn't be added globally and instead, should be added locally.
  • Requires cluster credentials:
When using global scope, you typically use ONTAP cluster credentials to onboard the storage backend.

Local Scope Defined in VMware vSphere OTV Plugin UI:

  • Local scope, on the other hand, refers to settings, configurations, or objects that are restricted to a specific context, such as a particular VM, datastore, or user.
  • Local storage backends with cluster or SVM credentials are added through the ONTAP tools user plugin interface and are limited to a vCenter.
  • Adding an SVM in the Local Scope is limited to a single vCenter.
  • When using cluster credentials locally, the associated SVMs automatically map with the vCenter to manage vVols or VMFS datastores.
  • For VMFS management, including SRA, ONTAP tools supports SVM credentials without needing a global cluster scope.
  • These configurations are not shared across the entire environment and are only applicable within the defined local context.

Examples:

  • Local Policies: Storage policies that apply only to a specific datastore or a set of VMs.
  • Local Settings: Custom configurations for a particular VM or user that do not affect the broader environment.
  • Local Resources: Storage allocations or snapshots that are specific to a particular VM or datastore.

Key Differences Scope of Impact:

  • Global: Affects the entire ONTAP Tools environment.
  • Local: Affects only a specific part of the environment.

Accessibility:

  • Global: Accessible by all users and VMs.
  • Local: Accessible only within the defined local context.

Practical Implications:

  • Global Scope is useful for maintaining consistent policies and settings across your entire virtualized environment, ensuring uniformity and simplifying management.
  • Local Scope allows for customization and fine-tuning specific to individual VMs or users, providing flexibility to address unique requirements or constraints.
  • Understanding and appropriately applying these scopes can help you optimize your ONTAP Tools for VMware setup, ensuring both broad consistency and local customization where needed.

OTV 10 Use Cases:

  • If you intend to use VASA Provider, vVols, and you want VASA Provider to access storage using local or SVM scope, then your configuration should consist of the following steps. With this configuration, you can now use direct SVMs for VASA Provider.
  1. Adding storage using the cluster mgmt LIF in ONTAP Tools Manager
  2. Adding the SVM management LIF to the OTV UI, which is the NetApp ONTAP Tools plugin
  • If you have no intention of using VASA Provider or vVols with direct SVMs, you only need to add your cluster storage to the vSphere NetApp ONTAP Tools plugin

Additional Information

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.