ViPR Controller 2.3 - New Features

Table of Contents

ViPR Controller 2.3.0 new features and changes

New features and changes introduced in ViPR Controller 2.3.0.x are described in the following sections.

All documents referenced in the following sections are available from the ViPR Controller Product Documentation Index.

ViPR Controller Deployment

The ViPR Controller deployment on Microsoft Hyper-V, and VMware without a vApp has been improved for ease of use, and a consistent user experience installing on either system.

When installing on VMware, VMware tools (open-vm-tools) are included in ViPR Controller installation (3rd-party independent).

Backup and Recovery of ViPR Controller

The following additions and enhancements have been made to the backup and restore options for the ViPR Controller.

ViPR Controller minority node recovery has been added to the ViPR Controller UI functionality. Minority node recovery can be used when:

Minority node recovery can be performed by Security Administrators from the ViPR Controller UI Settings > Recovery > Node Recovery page. Security Administrators, System Administrators, and System Monitors can view the status of a Node Recovery.

The following enhancements have been made to the ViPR Controller native backup and restore functionality when ViPR Controller is configured with a single virtual data center.

For details see the ViPR Controller Installation, Upgrade, and Maintenance Guide.

Database Consistency Check

The database consistency check allows System Administrators to check if the ViPR Controller database is synchronized across all of the ViPR Controller nodes. If the nodes are not synchronized, then a database repair is run to synchronize the database across the nodes at the point in time the check was run.

The Database Consistency Status is displayed in the ViPR Controller UI, Dashboard. The Last Completed Database Check indicates the last time the check was run. The database check is run automatically every 5 days, or after a ViPR Controller node recovery. The frequency of how often the check is run is defined in the ViPR Controller and cannot be changed.

IP addresses for ViPR Controller nodes can be changed through the ViPR Controller UI

The IP addresses for ViPR Controller nodes that are installed on Hyper-V or VMware without vApp can be changed from the ViPR Controller UI Settings > Network Configuration page.

Support for tenant mapping and role assignment based on LDAP groups

In addition to AD groups, tenant mapping, and role assignment can now be configured with LDAP groups. LDAP group support based on Group Object Classes and Group Member Attributes in the Authentication Provider.

To support LDAP groups, Group Object Class and Group Member Attributes have been added to the ViPR Controller Authentication Provider. ViPR Controller uses the Group Object Classes and Group Member Attributes, along with Group Attribute to search group membership in LDAP.

Note Image
When using the CLI, the groupobjectclasses and groupmemberattributes entries must be present in the configuration file but with blank values when using Active Directory.

If upgrading from an earlier version of ViPR Controller existing authentication providers can be modified to enable LDAP group support. When ViPR Controller is configured with VDC’s in the geo-federation all instances must be upgraded to ViPR Controller 2.3 before the LDAP groups can be added.

LDAP groups can be added, mapped, and assigned from the ViPR Controller REST API, CLI, or UI. Refer to the following documents for details:

Support for tenant mapping and role assignment based on local user groups

ViPR Controller user groups can be created based on the AD or LDAP user attributes. Once created the ViPR Controller User Group can be:

In a geo-federated environment, user groups can only be implemented after all instances have been upgraded to ViPR Controller 2.3.

ViPR Controller user groups can be created, mapped, and assigned from the ViPR Controller REST API, CLI, or UI. Refer to the following documents for details:

Changes to Security Administrator and Tenant Administrator privileges

Only the Security Administrator can perform the following functions in ViPR Controller.

The Tenant Administrator can perform the following operations for the tenants assigned to them:

In previous releases ViPR Controller also allowed both the Security Administrator, and the Tenant Administrator to create, modify, and delete existing tenants.

NetApp Cluster-Mode support

Support for NetApp Cluster-Mode has been added to this release of ViPR Controller. Supported features include:

Create, modify, and delete NFS Export of NetApp Cluster-Mode snapshots is not supported in this release of ViPR Controller.

Additional file storage support for EMC Isilon, NetApp 7-Mode, and NetApp Cluster-Mode.

For EMC Isilon, NetApp 7-mode, and NetApp Cluster-mode file storage systems the following Access Control List (ACL) functionality is supported:

Limitation for Data Domain, VNX for File, and VNXe:

Increased functionality for file system shares

Enhancements to file storage system discovery includes:

VCE Vblock™ System support

ViPR Controller support for Vblock systems now includes support for:

ESX or ESXi host discovery

ESX and ESXi hosts can now be added to ViPR Controller individually as hosts. They can also be added with a vCenter, but it is no longer required.

Ingestion of VMAX3 volumes

ViPR Controller can ingest VMAX3 volumes, including SRDF R1 and R2 volumes containing replicas operating in synchronous and asynchronous mode.

Ingestion of snapshots, full copies, and continuous copies

ViPR Controller can ingest snapshots, full copies, and continuous copies that are on VMAX, VMAX3, and VNX volumes. This includes the following functionality:

Ingestion of SRDF/A protected volumes without consistency group (CG) provisioning

ViPR Controller no longer requires that SRDF/A protected volumes provide CG provisioning to be ingested. SRDF/A protected volumes in device groups, composite groups and consistency groups on the VMAX array cannot be ingested.

SRDF enhancements

These enhancements include:

Full copy enhancements: incremental restore and resynchronization

These enhancements include:

VPLEX enhancements

These enhancements include:

RecoverPoint enhancements

These enhancements include:

Ingestion of XtremIO volumes

These enhancements include:

New VMware Services added to the Service Catalog

The following two services have been added to the ViPR Controller Service Catalog, Block Services for VMware:

Using the Export Volume for VMware service, puts some limitations of the use of the following two services:

Enhancement to Service Catalog, VMware services

ViPR Controller now allows you to use the Create Block Volume and VMware Datastore service to create multiple datastores, and volumes in the same order. While in the service order, the user enters the datastore name, volume name, an volume size for each datastore being created.

You can now enable the Storage I/O Control on a VMFS or NFS datastore while using the following services from the Service Catalog:

Compute Stack Integration Support for VMware® vRealize Orchestrator

Updates to ViPR Controller have been made to support integration with vRealize Orchestrator (vRO), which was formerly VMware vCenter Orchestrator (vCO), and a new category of workflows have been added to the plug-in which allow you to perform ViPR Controller operations on multiple ViPR Controller resources, as well as perform multiple ViPR Controller operations in a single workflow.

Back to Top