Get storage details
Returns the details of the selected storage.
Example cURL requests
Get Storage Details
curl -H "X-Auth-Token: $TOKEN" -X GET https:/$OP_PANEL_HOST/api/v3/onepanel/provider/storages/$STORAGE_ID
{
"type": "s3",
"storagePathType": "flat",
"signatureVersion": 4,
"scheme": "http",
"readonly": false,
"qosParameters":{
"storageId": "05b6c0a9b72e475c9d5061b0b7e16947chbcdc",
"providerId": "03c7e42a793912307b01b1bbb72a3a6bch4c1c"
},
"name": "My S3 Storage",
"maximumCanonicalObjectSize": 67108864,
"lumaFeed": "auto",
"importedStorage": false,
"id": "05b6c0a9b72e475c9d5061b0b7e16947chbcdc",
"hostname": "https://iam.exampele.com:443/",
"fileMode": "0664",
"dirMode": "0775",
"bucketName": "bucket1.iam.examplee.com",
"blockSize": 10485760,
"accessKey": ""
}
Path parameters
| Parameter | Type & Description |
|---|---|
| id required | string The Id of a storage resource, which details should be returned. |
Request Examples
onepanel-rest-cli -u onepanel:$PASSPHRASE getStorageDetails id=$STORAGE_ID --host https://$OP_PANEL_HOST:9443
Responses
The details of a selected storage.
The type of storage.
type = "posix"
Any POSIX compatible storage, typically attached over high-throughput local network, such as NFS.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
The type of storage.
type = "nulldevice"
POSIX compatible storage which emulates behavior of /dev/null on
local filesystem. Allows running various performance tests, which are
not impacted by actual storage latency.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
The type of storage.
type = "nfs"
NFS storage.
Type of the storage. Must be given explicitly and must match the actual type of subject storage - this redundancy is needed due to limitations of OpenAPI polymorphism.
The Id of storage.
The name of storage.
Result of storage verification (reading and writing a file). Returned only on PATCH requests for read-write storages.
Storage operation timeout in milliseconds.
Type of feed for LUMA DB. Feed is a source of user/group mappings used to populate the LUMA DB. For more info please read: https://onedata.org/#/home/documentation/doc/administering_onedata/luma.html
URL of external feed for LUMA DB. Relevant only if lumaFeed equals external.
API key checked by external service used as feed for LUMA DB. Relevant only if lumaFeed equals external.
Map with key-value pairs used for describing storage QoS parameters.
Defines whether storage contains existing data to be imported.
Defines whether storage supports long-term dataset archiving.
Defines whether the storage is readonly. If enabled, Oneprovider will block any operation that writes, modifies or deletes data on the storage. Such storage can only be used to import data into the space. Mandatory to ensure proper behaviour if the backend storage is actually configured as readonly. This option is available only for imported storages.
Unauthorized request.
Forbidden request.
Storage does not exist.
Internal server error.
error object (ErrorDetails) Object describing an error.
Object describing an error.
String identifying the error type. Does not change between error instances.
Human readable error description. May contain information specific to given error instance.
Details about the error instance. The object schema is specific to each error type.
Example
{
"error": {
"id": "badValueString",
"details": {
"key": "name"
},
"description": "Bad value: provided \"name\" must be a string."
}
}Services needed to fulfill this request are not running.