EMC ViPR REST API

Search (SHIFT+S)

API Reference


New in this release

Add Storage System Type

POST /vdc/storage-system-types

short term solution. This will be discontinued and mechanism will be provided to add new storage type during driver deployment.


Required Roles

Requires one of the following roles:

  • SYSTEM_ADMIN
  • RESTRICTED_SYSTEM_ADMIN

Request Payload

All parameters are required unless otherwise stated.

Field Description Type Notes
<storagesystem_type_add>
</storagesystem_type_add>

Response Body

StorageSystemTypeRestRep object.

Field Description Type Notes
<storagesystem_type>
<storage_type_id> Storage System Type ID internal URI generated by system for unique identification String
<storage_type_name> Storage System Type name, example VMAX String
<meta_type> Storage System Type type, example file, block and object String
<is__smi_provider> Is this Storage System Type is managed using SMI Provider. If true CoprHD should connect through Provider only Boolean
<storage_type_disp_name> Display name for storage system type, example EMC VMAX String
<is_default_ssl> Storage system type support SSL connection by default. If true provide SSL port Boolean
<is_default_mdm> Is the storage system type support Meta Data Manager as default. This is applicable only for ScaleIO arrays Boolean
<is_only_mdm> Is the storage system type support only Meta Data Manager. This is applicable only for ScaleIO arrays Boolean
<is_element_mgr> Whether the Storage System Type is managed by Element Manager. Applicable for ScaleIO Boolean
<is_secret_key> Whether the Storage System Type has a secret key. Boolean
<ssl_port> SSL port number, if SSL is supported and enabled String
<non_ssl_port> Storage System Type port number. String
<driver_class_name> Storage System Type driver class name. This class is defined in South Bound SDK of CoprHD that device driver developer should implement. String
<name> The name assigned to this resource in ViPR. The resource name is set by a user and can be changed at any time. It is not a unique identifier. String
<id> An identifier that is generated by ViPR when the resource is created. The resource ID is guaranteed to be unique and immutable across all virtual data centers for all time. URI
<link> A hyperlink to the details for this resource
<creation_time> A timestamp that shows when this resource was created in ViPR DateTime
<tags> Keywords and labels that can be added by a user to a resource to make it easy to find when doing a search.
<tag> String 0-* Elements
</tags>
<inactive> Whether or not the resource is inactive. When a user removes a resource, the resource is put in this state before it is removed from the ViPR database. Boolean
<global> Boolean
<remote> Boolean
<vdc>    
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</vdc>      
<internal> Whether or not the resource is an internal resource. Boolean
</storagesystem_type>