Combining Ceph’s distributed block storage capabilities with JuiceFS metadata separation and MinIO’s S3-compatible API creates a robust hybrid storage environment. This design allows object-level access over a high-performance file system layer backed by resilient RADOS clusters.

Pre-Deployment Requirements

Before configuration begins, verify the following environment status:

• Operational Ceph cluster with accessible RADOS pools.
• Installed JuiceFS client tools on target hosts.
• Available MinIO binary compatible with the OS.
• Necessary network rules permitting inter-service communication.
• ceph-common package installed for pool management.

Configuring the Backend Storage

Provitioning RADOS Resources

Initialize the storage pool designated for the filesystem data tier. Adjust replication counts based on safety requirements.

ceph osd pool create jfs-data-volume 256 256

Initializing JuiceFS Parameters

Rather than hardcoding secrets in configuration files, define credentials via environment variables to enhance security posture during initialization. This approach modifies the deployment workflow compared to static YAML approaches.

export JFS_SYSTEM_NAME="production-meta"
export META_CONN="redis://internal-db:6379/meta_db"
export STOR_TYPE="ceph"
export BUCKET_REF="jfs-data-volume"
export MONITOR_ADDR="192.168.10.5:6789"
export CEPH_CONF="/etc/ceph/ceph.conf"
export ACCESS_CRED="storage_user_01"
export SECRET_VAL="xYz123SecureKey!"

Execute the format command passing these parameters explicitly.

juicefs format "$JFS_SYSTEM_NAME" \\
  --storage "$STOR_TYPE" \\
  --bucket "$BUCKET_REF" \\
  --metadata "$META_CONN" \\
  --access-key "$ACCESS_CRED" \\
  --secret-key "$SECRET_VAL" \\
  --monitors "$MONITOR_ADDR" \\
  --conf "$CEPH_CONF"

Launching the Object Interface

Filesystem Mounting

Create the target directory for the object service and bind the JuiceFS instance to it. Ensure the mount point exists prior to execution.

mkdir -p /app/storage-layer
juicefs mount "$JFS_SYSTEM_NAME" /app/storage-layer

Activating MinIO Services

Start the MinIO daemon pointing to the mounted directory. Utilize the modernized root credentials environment variables for session management.

export MINIO_ROOT_USER="admin_access"
export MINIO_ROOT_PASSWORD="ComplexPassword#99"
minio server /app/storage-layer

Upon successful startup, the service exposes standard S3 endpoints on port 9000. Data ingested via MinIO clients is transparently stored within the JuiceFS metadata and Ceph backend infrastructure, providing unified access patterns.