Storage volumes volume.uuid files path endpoint overview
Overview
This API is used to read a file, write to a file, retrieve a list of files and directories, and retrieve or modify certain properties of files and directories. The path field is used to specify the path to the directory or file to be acted on. The path field requires using "%2E" to represent "." and "%2F" to represent "/" for the path provided.
File data
Read and write data from/to a named file. To read a file, the Accept request HTTP header must be specified as multipart/form-data, and a value for the length
query property, which represents the number of bytes to be read, must be specified. The API will fail if the length of data being read/written exceeds 1 MB. This API should only be used on normal files or streams associated with files. The results for other file types, such as LUNs is undefined.
The following APIs are used to read or write data to a file:
– GET /api/storage/volumes/{volume.uuid}/files/{path}?byte_offset=0&length=40 -H "Accept: multipart/form-data"
– POST /api/storage/volumes/{volume.uuid}/files/{path} -H "Content-Type: multipart/form-data" --form "file=the data to be written to the new file"
– PATCH /api/storage/volumes/{volume.uuid}/files/{path}?byte_offset=10 -H "Content-Type: multipart/form-data" --form "file=the new data to be written or overwritten to the existing file starting at byte_offset"
Listing directories and files
A list of files and directories and their properties can be retrieved for a specified path.
The following APIs are used to view a list of files and directories:
– GET /api/storage/volumes/{volume.uuid}/files
– GET /api/storage/volumes/{volume.uuid}/files/{path}
– GET /api/storage/volumes/{volume.uuid}/files/{path}?fields=*
File information
The metadata and detailed information about a single directory or file can be retrieved by setting the return_metadata
query property to true
. The information returned includes type, creation_time, modified_time, changed_time, accessed_time, unix_permissions, ownder_id, group_id, size, hard_links_count, inode_number, is_empty, bytes_used, inode_generation, is_vm_aligned, is_junction, is_snapshot, and links.
The following API is used to view the properties of a single file or directory:
– GET /api/storage/volumes/{volume.uuid}/files/{path}?return_metadata=true
QoS
QoS policies and settings enforce Service Level Objectives (SLO) on a file. A pre-created QoS policy can be used by specifying the qos.name
or qos.uuid
properties.
The following APIs are used to assign a QoS policy to a file:
– PATCH /api/storage/volumes/{volume.uuid}/files/{path} -d '{ "qos_policy.name" : "policy" }'
– PATCH /api/storage/volumes/{volume.uuid}/files/{path} -d '{ "qos_policy.uuid" : "b89bc5dd-94a3-11e8-a7a3-0050568edf84" }'
Symlinks
The following APIs are used to create a symlink and read the contents of a symlink:
– POST /api/storage/volumes/{volume.uuid}/files/{path} -d '{ "target" : "directory2/file1" }'
– GET /api/storage/volumes/{volume.uuid}/files/{path}?return_metadata=true&fields=target
Examples
Writing to a new file
# The API: POST /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X POST "https://<mgmt-ip>/api/storage/volumes/54c06ce2-5430-11ea-90f9-005056a73aff/files/aNewFile" -H "Content-Type: multipart/form-data" --form "file=the data to be written to the new file"
Writing to an existing file
# The API: PATCH /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X PATCH "https://<mgmt-ip>/api/storage/volumes/54c06ce2-5430-11ea-90f9-005056a73aff/files/aNewFile?byte_offset=39" -H "Content-Type: multipart/form-data" --form "file=*here is a little more data"
Reading a file
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/54c06ce2-5430-11ea-90f9-005056a73aff/files/aNewFile?byte_offset=0&length=100" -H "Accept: multipart/form-data" # Response for file data: --ec51b3541741ade7 Content-Disposition: form-data; name="bytes_read" Content-Type: text/plain 66 --ec51b3541741ade7 Content-Disposition: form-data; filename="aNewFile" Content-Type: application/octet-stream the data to be written to the new file*here is a little more data --ec51b3541741ade7--
Creating a stream on a file
# The API: POST /api/storage/volumes/{volume.uuid}/files/{path}?overwrite=true # The call: curl -X POST "https://<mgmt-ip>/api/storage/volumes/54c06ce2-5430-11ea-90f9-005056a73aff/files/aNewFile?overwrite=true&byte_offset=-1&stream_name=someStream" -H "Content-Type: multipart/form-data" --form "file=the data to be written to the new file"
Retrieving the list of files in a directory
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/d1%2Fd2%2Fd3" # Response for file records: { "records": [ { "path": "d1/d2/d3", "name": ".", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2F%2E" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2F%2E?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "..", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2F%2E%2E" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2F%2E%2E?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "f1", "type": "file", "_links": { "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2File1?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "d5", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2Fd5" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2Fd5?return_metadata=true" } } } ], "num_records": 4, "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3" } } }
Retrieving a list of files based on file type
You can filter the list of files you retrieve based on multiple file types by including a query parameter in the following format type="file\|symlink"
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/d1%2Fd2%2Fd3?type=file|directory" # Response for file records: { "records": [ { "path": "d1/d2/d3", "name": ".", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2F%2E" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2F%2E?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "..", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2F%2E%2E" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2F%2E%2E?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "f1", "type": "file", "_links": { "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2File1?return_metadata=true" } } }, { "path": "d1/d2/d3", "name": "d5", "type": "directory", "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3%2Fd5" }, "metadata": { "href": "/api/storage/volumes/e8274d79-3bba-11ea-b780-005056a7d72a/files/d1%2Fd2%2Fd3%2Fd5?return_metadata=true" } } } ], "num_records": 4, "_links": { "self": { "href": "/api/storage/volumes/cb6b1b39-8d21-11e9-b926-005056aca658/files/d1%2Fd2%2Fd3" } } }
Retrieving the properties of a directory or a file
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path}?return_metadata=true # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/d1%2Fd2%2Fd3%2Ff1?return_metadata=true" # Response for file properties: { "records": [ { "path": "d1/d2/d3/f1", "name": "", "type": "file", "creation_time": "2019-06-12T21:27:28-04:00", "modified_time": "2019-06-12T21:27:28-04:00", "changed_time": "2019-06-12T21:27:28-04:00", "accessed_time": "2019-06-12T21:27:28-04:00", "unix_permissions": 644, "owner_id": 54738, "group_id": 30, "size": 200, "hard_links_count": 1, "inode_number": 1233, "bytes_used": 4096, "inode_generation": 214488325, "is_vm_aligned": false, "is_junction": false, "is_snapshot": false } ], "num_records": 1, "_links": { "self": { "href": "/api/storage/volumes/da8bb06c-823e-11e9-b790-005056acdcb0/files/d1%2Fd2%2Fd3%2Ff1?return_metadata=true" } } }
Creating a symlink to a relative path
You can use the POST request to create a symlink.
# The API: POST /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X POST "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/symlink1" -H 'accept: application/hal+json' -d '{ "target" : "d1/f1"}' # The response: {}
Retrieving the target of a symlink
You can use the GET request to view the target of a symlink.
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/symlink1?return_metadata=true&fields=target" # The response: { "records": [ { "path": "symlink1", "target": "d1/f1" } ], "num_records": 1, "_links": { "self": { "href": "/api/storage/volumes/54c06ce2-5430-11ea-90f9-005056a73aff/files/symlink1?return_metadata=true&fields=target" } } }
Retrieving all information for a directory
# The API: GET /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X GET "https://<mgmt-ip>/api/storage/volumes/1ef5d1b2-f9d7-11e9-8043-00505682f860/files/d1?return_metadata=true&fields=**" # Response for all fields of the directory: { "records": [ { "svm": { "uuid": "58a996a2-f9d5-11e9-8043-00505682f860", "_links": { "self": { "href": "/api/svm/svms/58a996a2-f9d5-11e9-8043-00505682f860" } } }, "volume": { "uuid": "1ef5d1b2-f9d7-11e9-8043-00505682f860", "_links": { "self": { "href": "/api/storage/volumes/1ef5d1b2-f9d7-11e9-8043-00505682f860" } } }, "path": "d1", "type": "directory", "creation_time": "2019-10-28T23:04:13+00:00", "modified_time": "2019-10-28T23:10:30+00:00", "changed_time": "2019-10-28T23:10:30+00:00", "accessed_time": "2019-10-28T23:10:38+00:00", "unix_permissions": 755, "owner_id": 1002, "group_id": 65533, "size": 4096, "hard_links_count": 5, "inode_number": 96, "is_empty": false, "bytes_used": 4096, "inode_generation": 214514951, "is_vm_aligned": false, "is_junction": false, "is_snapshot": false, "qos_policy": { "name": "pg1", "uuid": "00725264-688f-11ea-8f10-005056a7b8ac" } ], "num_records": 1, "_links": { "self": { "href": "/api/storage/volumes/1ef5d1b2-f9d7-11e9-8043-00505682f860/files/d1?return_metadata=true&fields=**" } } }
Assigning a QoS policy to a file
You can use the PATCH request to assign a QoS policy to a file.
# The API: PATCH /api/storage/volumes/{volume.uuid}/files/{path} # The call: curl -X PATCH "https://<mgmt-ip>/api/storage/volumes/cb6b1b39-8d21-11e9-b926-05056aca658/files/directory1%2Ffile1" -d '{ "qos_policy.name" : "policy"}' # The response: {}