Filesystems/{filesystemName}/filesets/{filesetName}/directory/{path}: POST

Creates a directory inside a fileset.

Availability

Available on all IBM Storage Scale editions.

Description

The POST filesystems/{filesystemName}/filesets/{filesetName}/directory/{path} request creates directory inside a fileset.

Request URL

https://management API host:port/scalemgmt/v2/filesystems/filesystemName/filesets/filesetName/directory/path
where:
filesystems/filesystemName
Specifies the name of the file system to which the fileset belong. Required.
filesets/filesetName
Specifies the name of the fileset to which the directory belongs. Required.
directory/path
Specifies the directory to be created. Required.

Request headers

Accept: application/json

Request parameters

The following parameters can be used in the request URL to customize the request:
Table 1. List of request parameters
Parameter name Description and applicable keywords Required/optional
filesystemName The file system name. Required.
filesetName   Required.
path The directory path relative to the fileset path. Required.
body Body of the request that contains the required parameters to be passed on to the IBM Storage Scale system to perform the requested operation. Required.

Request data

{
"user": "User name",
"uid": "User ID",
"group": "Group name",
"gid": "Group ID"
"permission": Permissions
"recursive":  false}
    }
"user": "User name"
The name of the owning user.
"uid": "User ID"
The ID of the owning user.
"group": "Group name"
The name of the owning user group.
"gid": "Group ID"
The ID of the owning user group.
"permission": Access permissions
The number of permissions that are set by using the CLI command chmod. If nothing is specified, then no action is allowed. The default value is 771.
"recursive": true | false
Specifies whether the directory is created recursively within the entire fileset or within the specific fileset directory that is defined in the endpoint path. The recursive parameter is always displayed as false for this request.

Response data

{
   "status": {
      "code":ReturnCode",
      "message":"ReturnMessage"
   },
   "jobs": [
      {
         "result":"", 
           { 
             "commands":"String",
             "progress":"String,
             "exitCode":"Exit code",
             "stderr":"Error",
             "stdout":"String",
           },
         "request":" ",
           {
             "type":"{GET | POST | PUT | DELETE}",
             "url":"URL",
             "data":""",
           }
         "jobId":"ID",
         "submitted":"Time",
         "completed":Time",
         "status":"Job status",
         }
   ],
  }
For more information about the fields in the following data structures, see the links at the end of this topic.
"jobs":
An array of elements that describe jobs. Each element describes one job.
"status":
Return status.
"message": "ReturnMessage",
The return message.
"code": ReturnCode
The return code.
"result"
"commands":"String'
Array of commands that are run in this job.
"progress":"String'
Progress information for the request.
"exitCode":"Exit code"
Exit code of command. Zero is success, nonzero denotes failure.
"stderr":"Error"
CLI messages from stderr.
"stdout":"String"
CLI messages from stdout.
"request"
"type":"{GET | POST | PUT | DELETE}"
HTTP request type.
"url":"URL"
The URL through which the job is submitted.
"data":" "
Optional.
"jobId":"ID",
The unique ID of the job.
"submitted":"Time"
The time at which the job was submitted.
"completed":Time"
The time at which the job was completed.
"status":"RUNNING | COMPLETED | FAILED"
Status of the job.

Examples

The following example shows how to create a directory inside the fileset fs1.

Request data: 
curl -k -u admin:admin001 -X POST --header 'content-type:application/json' --header 'accept:application/json' 
-d '{ 
   "user": "testuser55", 
   "uid": 1234, 
   "group": "mygroup", 
   "gid": 4711,
   "permissions": 700,
   "recursive": false 
}' 'https://198.51.100.1:443/scalemgmt/v2/filesystems/gpfs0/filesets/fs1/directory/mydir'
Response data:
Note: In the JSON data that is returned, the return code indicates whether the command is successful. The response code 200 indicates that the command successfully retrieved the information. Error code 400 represents an invalid request and 500 represents internal server error. 
{
  "jobs" : [ {
    "jobId" : 1000000000005,
    "status" : "RUNNING",
    "submitted" : "2017-03-14 15:59:34,180",
    "completed" : "N/A",
    "request" : {
      "data" : {
         "user": "testuser55", 
         "uid": 1234, 
         "group": "mygroup", 
         "gid": 4711,
         "permissions": 700,
         "recursive": false 
      },
      "type" : "POST",
      "url" : "/scalemgmt/v2/filesystems/gpfs0/filesets/fs1/directory/mydir"
    },
    "result" : { }
  } ],
  "status" : {
    "code" : 202,
    "message" : "The request was accepted for processing"
  }
}