ceph-admin-ops-client v0.1.5

Ceph Object Gateway AdminOps API client

This module contains a Node.js wrapper around the HTTP API of Ceph Object Gateway's Admin Ops API.

Installation

The module can be installed via

npm install ceph-admin-ops-client --save

Basic usage

As a minimum, the accessKey, secretKey, host and port properties need to be set when using this module. Each method returns a promise.

Setup

var AdminOpsAPI = require("ceph-admin-ops-client");

var api = new AdminOpsAPI({
    accessKey: "<<ACCESS_KEY>>",
    secretKey: "<<SECRET_KEY>>",
    host: "192.168.0.100",
    port: 10000
});

Sample method call:

api.getUserInfo({ uid: "myUser" }).then(function(userInfo){
    console.log(JSON.stringify(userInfo));
}).catch(function(error) {
    console.log(JSON.stringify(error));
});

Configuration properties

• accessKey: The access key with which the API shall be used.
• secretKey: The secret key with which the API shall be used.
• host: Either the IP address or the hostname of the Ceph Object Gateway endpoint (default is s3.amazonaws.com).
• port: The port of the Ceph Object Gateway endpoint (default is 80).
• protocol: Either http or https (default is http).
• useSubdomain: If a subdomain shall be used (boolean). Ddefault is false.
• adminBucket: The name of the "admin bucket" (the URI which is configured for the base admin endpoint). Default is admin.
• expiresInMinutes: The time in minutes until the request expires (default is 10).

Methods

The parameters argument for the methods (see below) is an object containing a property map, for example

{
    "uid": "myUser",
    "bucket": "myBucket"
}

getUsage(parameters)

Request bandwidth usage information.

trimUsage(parameters)

Remove usage information. With no dates specified, removes all usage information.

getUserInfo(parameters)

Get user information. If no user is specified returns the list of all users along with suspension information.

createUser(parameters)

Create a new user. By Default, a S3 key pair will be created automatically and returned in the response. If only one of access-key or secret-key is provided, the omitted key will be automatically generated. By default, a generated key is added to the keyring without replacing an existing key pair. If access-key is specified and refers to an existing key owned by the user then it will be modified.

updateUser(parameters)

Modify a user.

deleteUser(parameters)

Remove an existing user.

createSubUser(parameters)

Create a new subuser (primarily useful for clients using the Swift API). Note that either gen-subuser or subuser is required for a valid request. Note that in general for a subuser to be useful, it must be granted permissions by specifying access. As with user creation if subuser is specified without secret, then a secret key will be automatically generated.

updateSubUser(parameters)

Modify an existing subuser

deleteSubUser(parameters)

Remove an existing subuser

createKey(parameters)

Create a new key. If a subuser is specified then by default created keys will be swift type. If only one of access-key or secret-key is provided the committed key will be automatically generated, that is if only secret-key is specified then access-key will be automatically generated. By default, a generated key is added to the keyring without replacing an existing key pair. If access-key is specified and refers to an existing key owned by the user then it will be modified. The response is a container listing all keys of the same type as the key created. Note that when creating a swift key, specifying the option access-key will have no effect. Additionally, only one swift key may be held by each user or subuser.

deleteKey(parameters)

Remove an existing key.

getBucketInfo(parameters)

Get information about a subset of the existing buckets. If uid is specified without bucket then all buckets beloning to the user will be returned. If bucket alone is specified, information for that particular bucket will be retrieved.

deleteBucket(parameters)

Delete an existing bucket.

getBucketIndex(parameters)

Check the index of an existing bucket. NOTE: to check multipart object accounting with check-objects, fix must be set to True.

unlinkBucket(parameters)

Unlink a bucket from a specified user. Primarily useful for changing bucket ownership.

linkBucket(parameters)

Link a bucket to a specified user, unlinking the bucket from any previous user.

deleteObject(parameters)

Remove an existing object. NOTE: Does not require owner to be non-suspended.

getBucketPolicy(parameters)

Read the policy of a bucket.

getObjectPolicy(parameters)

Read the policy of an object.

createUserCapability(parameters)

Add an administrative capability to a specified user.

deleteUserCapability(parameters)

Remove an administrative capability from a specified user.

getUserQuota(parameters)

Read the quota of an user.

updateUserQuota(parameters)

Update the quota of an user.

getBucketQuota(parameters)

Read the quota of a bucket.

updateBucketQuota(parameters)

Update the quota of a bucket.