Onedata API Reference

REST API references for Onezone, Oneprovider, and Onepanel.

Version:

Onezone REST API Oneprovider REST API Onepanel REST API

Version:

Support space

POST /provider/spaces

Supports an existing space.

Example cURL requests

Support space

curl -H "X-Auth-Token: $TOKEN" -X POST https://$OP_PANEL_HOST/api/v3/onepanel/provider/spaces \
-H "Content-Type: application/json" -d '{
    "token": "MDAU02QHLaaJ00go",
    "size": 10000000,
    "storageId": "18a42a43b1b2d9e9a1f82"
}'

{
    "id": "16403a6c45105010dc7103e31874cb3echac41"
}

Request body

application/json

Specification of the space support request including support size and token.

Property Type & Description

token

string

The token for space creation or support.

size

integer

The storage space size in bytes that provider is willing to assign to the space.

storageId

string

The Id of the storage resource where the space data should be stored.

storageImport

object (StorageImport)

Configuration of the storage import within the space.

mode

string

Mode of the storage import within the space.

In case of auto mode, the storage will be automatically scanned and data will be imported from storage into the assigned Onedata space without need for copying the data.

Configuration of the auto storage import can be passed in the autoStorageImportConfig parameter. It is possible to enable periodical scans for automatic detection of changes on the storage (refer to the option continuousScan in the config).

In case of manual mode, the files must be registered manually by the space users with REST API. Registration of directories is not supported. For more info please read: https://onedata.org/#/home/api/stable/oneprovider?anchor=tag/File-registration

Enum:

automanual

autoStorageImportConfig

object (AutoStorageImportConfig)

Configuration of auto storage import mechanism. The auto import is based on scans - gradual traversing of the file system and registration of files and directories.

maxDepth integer Maximum depth of filesystem tree that will be traversed during the scan.
syncAcl boolean Flag that enables synchronization of NFSv4 ACLs.
continuousScan boolean With this option enabled the storage will be scanned periodically and direct changes on the storage will be reflected in the assigned Onedata space (upon the consecutive scan).
scanInterval integer Period between subsequent scans in seconds (counted from end of one scan till beginning of the following). This parameter is relevant only for continuous scans.
detectModifications boolean Flag determining that modifications of files on the synchronized storage will be detected. If disabled, the storage will be treated as immutable (only creations and deletions of files on storage will be detected). This parameter is relevant only for continuous scans.
detectDeletions boolean Flag determining that deletions of files from the synchronized storage will be detected. This parameter is relevant only for continuous scans.

accountingEnabled

boolean

Indicates if accounting is enabled. The accounting mechanism utilizes directory statistics to keep track of quota usage within a space for the corresponding supporting provider.

dirStatsServiceEnabled

boolean

Indicates if the directory statistics service is enabled. The service gathers statistics concerning logical and physical directory size, file count and update times. It cannot be disabled if accounting is enabled.

Request Examples

application/json

{
  "token": "ASDJNASD87687ASDMNBMNASD87786asd",
  "size": 1024000,
  "storageId": "x7It3cpgNgLZ8RwOrOoW"
}

Responses

application/json

201

Created space support relation.

Property	Type & Description
id string Resource Id.

Example

application/json

{
  "id": "26cbc2b20f92416eb9f3cba65e50c1d2"
}

400

Invalid request.

Property

Type & Description

error

object (ErrorDetails)

Object describing an error.

id required string String identifying the error type. Does not change between error instances.
description required string Human readable error description. May contain information specific to given error instance.
details object Details about the error instance. The object schema is specific to each error type.

Example

application/json

{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}

401

Unauthorized request.

403

Forbidden request.

500

Internal server error.

Property

Type & Description

error

object (ErrorDetails)

Object describing an error.

id required string String identifying the error type. Does not change between error instances.
description required string Human readable error description. May contain information specific to given error instance.
details object Details about the error instance. The object schema is specific to each error type.

Example

application/json

{
  "error": {
    "id": "badValueString",
    "details": {
      "key": "name"
    },
    "description": "Bad value: provided \"name\" must be a string."
  }
}

503

Services needed to fulfill this request are not running.