
UnManaged file systems are file systems, which are present within ViPR storage systems,but have not been ingested by ViPR which moves the unmanaged file systems under ViPR management. File system ingest provides flexibility in bringing unmanaged file systems under ViPR management. An unmanaged file system must be associated with a virtual pool, project, and virtual array before it can be managed by ViPR. List of supported virtual pools for each unmanaged file system is exposed using /vdc/unmanaged/filesystems/bulk. Using an unsupported virtual pool results in an error Size of unmanaged file systems which can be ingested via a single API Call is limited to 4000.
Requires one of the following roles:
All parameters are required unless otherwise stated.
Field | Description | Type | Notes |
<filesystem_ingest> | |||
<vpool> | URI representing the virtual pool supporting the unmanaged file systems | URI | |
<varray> | URI representing the virtual array supporting the unmanaged file systems | URI | |
<project> | URI representing the project | URI | |
<unmanaged_filesystem_list> | List of UnManaged FileSystem URIs. Use GET /vdc/storage-systems/{id}/unmanaged/filesystems for the list of unmanaged FileSystem ids on a Storage System basis. Use GET /vdc/unmanaged/filesystems/bulk for the list of all unManaged FileSystem ids. | URI |
0-* Elements |
</filesystem_ingest> |
Field | Description | Type | Notes |
<filesystems> | |||
<filesystem> |
0-* Elements |
||
<name> | The name of the resource | String | |
<id> | ViPR ID of the related object | URI | |
<link> | A hyperlink to the related object | ||
</filesystem> | |||
</filesystems> |