Skip to content
QuantCDN

Defining a New Persistent Storage Volume

Creating additional persistent storage volumes allows you to organize your application’s data storage according to your specific requirements. New volumes can be added to any environment beyond the inherited production defaults.

Creating a New Volume

Access Volume Creation

  1. Navigate to your environment’s details page
  2. Click on the Volumes tab
  3. Scroll to the “Define New Logical Volume” section
  4. Use the volume creation form to specify your new storage requirements

The form provides a streamlined interface for defining logical volumes that will be available for mounting into your containers.

Volume Configuration Fields

Volume Name (Required) Specify a unique identifier for your volume within the environment. The name should be descriptive and follow standard naming conventions:

  • Use lowercase letters, numbers, and hyphens
  • Examples: user-uploads, app-cache, log-storage, shared-assets
  • Must be unique within the environment
  • Cannot conflict with existing volume names
  • Used when configuring container mount points

Description (Optional) Provide a clear explanation of the volume’s purpose and intended usage. Good descriptions help team members understand the volume’s role:

  • “Persistent storage for user-uploaded files”
  • “Application cache data for improved performance”
  • “Shared configuration files across containers”
  • “Development environment test data”

Automatic Path Assignment Quant Cloud automatically assigns the underlying storage directory path for your volume. The platform creates a unique path structure based on:

  • Organization context
  • Application name
  • Environment name
  • Volume name

This automatic path management ensures no conflicts occur while providing organized storage structure. The root directory will be automatically set to /{volume-name} as indicated in the interface.

Creating the Volume

Submit Volume Definition After configuring the volume name and description, click “Define Volume” to create the new logical volume. The platform will:

  1. Validate the volume name for uniqueness and format
  2. Create the logical volume definition in the environment
  3. Prepare the underlying storage structure
  4. Make the volume available for container mounting

After Volume Creation

Volume Availability Once created, the new volume immediately appears in the “Defined Logical Volumes” list for the environment. The volume is now ready for use and can be mounted into any container within the same environment.

Next Steps for Usage To actually use the volume in your application:

  1. Configure Container Mount Points: Navigate to your environment’s “Edit Config” page
  2. Select Containers: Expand the containers that need access to this storage
  3. Add Mount Points: In the “Mount Points” section, select your new volume from the dropdown
  4. Specify Container Path: Define where the volume should be mounted inside the container
  5. Set Access Mode: Choose read-write or read-only access as appropriate

Volume Inheritance Volumes created in the production environment will automatically be inherited by new environments created after this volume definition. Existing environments will not automatically receive new volume definitions.

Common Volume Patterns

Application-Specific Storage

  • app-uploads for user-generated content
  • app-logs for persistent application logging
  • app-cache for performance optimization storage

Service-Specific Storage

  • redis-data for Redis persistence
  • elasticsearch-data for search index storage
  • nginx-cache for web server caching

Environment-Specific Storage

  • staging-test-data for staging environment testing
  • dev-scratch for development environment temporary storage
  • backup-storage for environment-specific backup data

Properly organized volume definitions provide the foundation for reliable, scalable persistent storage across your application’s lifecycle.