S

    Volian Linux Documentation

    Overview

    Welcome to Volian Linux, a secure and minimal Linux distribution designed for enterprise environments. Volian Linux is built with a focus on immutability, automation, and centralized management, making it ideal for large-scale deployments.

    This distribution is Debian-derived, leveraging the stability and vast package ecosystem of Debian while introducing an innovative pool-based file system that ensures integrity and rapid deployment.

    All of our code is available for review and contribution at https://gitlab.com/volian/.

    Key Features

    Immutable & Secure

    • Pool-Based File System: System files are stored as hashed objects, ensuring integrity and preventing unauthorized modifications.
    • Automatic Verification: Every boot verifies system files against a central management server.
    • Optional Local Storage: Systems can be fully ephemeral or retain local state as needed.

    Enterprise-Grade Architecture

    • Centralized Management Server: Nodes are configured dynamically at runtime, reducing installation complexity.
    • Fast & Automated Deployment: Systems can be provisioned in minutes by partitioning and syncing from the pool.
    • MDM Capabilities: The master server can handle mobile device management (MDM) functions for workstations.

    Security & Compliance

    • SELinux & Firewalld Enabled: Strong security defaults for enterprise environments.
    • CIS Compliance: Key security settings, such as noexec for /tmp, protect against malware like perfctl.
    • Cryptographic Integrity Checks: Ensures that all nodes remain in a known-good state.

    Debian-Based & Flexible

    • Debian Stability: Built on a solid Debian foundation with access to extensive package repositories.
    • Minimal & Efficient: The base system is lightweight, allowing enterprises to build only what they need.
    • Optional GUI: Users can configure their system to include KDE and Firefox.

    System Architecture

    Master Server

    The Volian Master Server manages all nodes and enforces system integrity. It is responsible for:

    • Storing system files in a hashed pool for fast retrieval.
    • Generating ISO images for easy, automated installation.
    • Assigning and enforcing system configurations.
    • Handling logs, monitoring, and MDM functions for workstations.

    Node Boot Process

    Each node follows a structured boot process:

    1. Boot & Partitioning: Nodes boot from an ISO and prepare their partitions.
    2. Configuration Fetch: The node retrieves its assigned configuration from the master server.
    3. File Sync: System files are copied from the central pool or retrieved dynamically at runtime.
    4. Integrity Verification: At each boot, the system checks all files and restores any inconsistencies.

    Storage Options

    • Fully Ephemeral: Systems fetch all files at boot and retain nothing locally. Ideal for disposable infrastructure.
    • Hybrid Cache Mode: Frequently used files are cached locally while the system remains centrally managed.
    • Persistent Mode: Local storage can be configured to retain /home, logs, or other partitions.

    Installation

    Setting Up the Master Server

    1. Install Volian Linux on a designated management machine.
    2. Configure the hashed file pool and system policies.
    3. Generate and distribute ISO images for deployment.
    4. Assign nodes to configurations via the management interface.

    Installing a Node

    1. Boot from a Volian ISO (network-enabled or standalone).
    2. Partition storage and initialize the system.
    3. The system contacts the master server and syncs its configuration.
    4. Files are retrieved from the central pool or local cache.
    5. The node boots into a verified state.

    Updates & Maintenance

    Update Mechanism

    Nodes automatically check the master server for updates using two strategies:

    • Pull-Based: Nodes fetch updates at boot and apply them automatically.
    • Push-Based: The master server can trigger updates and enforce compliance.

    Rollback & Recovery

    • If corruption or unauthorized changes are detected, files are restored from the central pool.
    • If a system rollback is needed, nodes can be re-imaged in minutes.

    Security Model

    • Immutable by Default: Core system files are locked to prevent drift.
    • Managed from Inception: Every node is registered with the master server.
    • Centralized Authentication: Keys and access policies are centrally controlled.

    Target Audience

    Volian Linux is designed for:

    • Enterprises & Data Centers: Centralized management for hundreds or thousands of machines.
    • Stateless Workstations: Perfect for environments where machines need to be reset frequently.
    • CI/CD & DevOps: Ensures consistent environments for automated workflows.
    • Security-Conscious Deployments: Protects against tampering with strong integrity checks.

    Getting Started

    Once installed, users can customize their system with Nala for package management and configure optional components using the system’s config files.

    For additional help, visit our documentation page.

    Community & Support

    Volian Linux is open source and community-driven. Want to contribute? Check out our GitLab repository.

    Need help? Visit our support page for troubleshooting and discussions.

    Roadmap

    Planned improvements include:

    • Cloud integration for hybrid deployments.
    • Expanded MDM functions for workstation management.
    • Enhanced rollback and disaster recovery options.
    • Additional architecture support beyond x86 and ARM.

    License

    Volian Linux is open source and free to use. See our license page for more details.

    Final Thoughts

    Volian Linux represents the next step in enterprise OS design—fast, secure, and centrally managed. Whether used for ephemeral cloud deployments or persistent enterprise infrastructure, Volian provides the flexibility and control needed to keep systems secure and efficient.

    On this page

    Powered by Doctave