Docs > Object Subsystem (ObjectNode)

Object Subsystem (ObjectNode)

How To Provide Object Storage Service with Object Subsystem (ObjectNode)

Start a ObjectNode process by execute the server binary of ChubaoFS you built with -c argument and specify configuration file.

nohup cfs-server -c objectnode.json &


Object Node using JSON format configuration file.


Key Type Description Mandatory
role string Role of process and must be set to objectnode Yes
listen string
Listen and accept ip address and port of this server.
Format: IP:PORT or :PORT
Default: :80
region string
Region of this gateway. Used by S3-like interface signature validation.
Default: cfs_default
domains string slice
Domain of S3-like interface which makes wildcard domain support
Format: DOMAIN
logDir string Log directory Yes
logLevel string
Level operation for logging.
Default: error
masterAddr string slice
Format: HOST:PORT.
HOST: Hostname, domain or IP address of master (resource manager).
PORT: port number which listened by this master
exporterPort string Port for monitor system No
prof string Pprof port Yes


     "role": "objectnode",
     "listen": ":80",
     "region": "cfs_default",
     "domains": [
     "logDir": "/opt/cfs/objectnode/logs",
     "logLevel": "debug",
     "masterAddr": [
     "exporterPort": 9512,
     "prof": "7013"

Fetch Authentication Keys

Authentication keys owned by volume and stored with volume view (volume topology) by Resource Manager (Master). User can fetch it by using administration API, see Get Volume Information at Volume

Using Object Storage Interface

Object Subsystem (ObjectNode) provides S3-compatible object storage interface, so that you can operate files by using native Amazon S3 SDKs.

For detail about list of supported APIs, see Supported S3-compatible APIs at Object Subsystem (ObjectNode)

For detail about list of supported SDKs, see Supported SDKs at Object Subsystem (ObjectNode)