# CIQ Documentation > Official product documentation for CIQ (Ctrl IQ, Inc.), the founding > commercial sponsor of Rocky Linux. CIQ builds enterprise infrastructure > software for AI, HPC, and regulated environments — RLC Pro (Rocky Linux > from CIQ), Fuzzball, Warewulf Pro, Ascender Pro, CIQ Bridge, and more. > This site (https://docs.ciq.com/) is published by CIQ (https://ciq.com/). Sibling CIQ properties: - [CIQ Website](https://ciq.com/): Company and product overviews, solutions, pricing, and services. - [CIQ Knowledge Base](https://kb.ciq.com/): Troubleshooting guides and product knowledge articles. - [CIQ Trust & Security Center](https://trust.ciq.com/): Compliance certifications and security posture. ## Ascender Enterprise automation platform for IT infrastructure and application deployment - [Backup](https://docs.ciq.com/ascender/admin-guides/backup): Back up an Ascender deployment. - [Restore](https://docs.ciq.com/ascender/admin-guides/restore): Restore an Ascender deployment from a previous backup. - [Ascender](https://docs.ciq.com/ascender): Enterprise automation platform for managing infrastructure, applications, and services at scale. - [Installation Overview](https://docs.ciq.com/ascender/installation): This section covers installing Ascender Automation Platform using the ascender-install tool across supported Kubernetes platforms. - [Installing Ascender](https://docs.ciq.com/ascender/installation/install): Install Ascender Automation Platform using the ascender-install tool. - [Installing Ascender on AKS](https://docs.ciq.com/ascender/installation/install-aks): Deploy Ascender Automation Platform on Azure Kubernetes Service. - [Installing Ascender on EKS](https://docs.ciq.com/ascender/installation/install-eks): Deploy Ascender Automation Platform on Amazon Elastic Kubernetes Service. - [Installing Ascender on GKE](https://docs.ciq.com/ascender/installation/install-gke): Deploy Ascender Automation Platform on Google Kubernetes Engine. - [Installing Ascender on Kubernetes](https://docs.ciq.com/ascender/installation/install-kubernetes): Install Ascender Automation Platform on an existing Kubernetes cluster. - [Installing Ascender on RKE2](https://docs.ciq.com/ascender/installation/install-rke2): Install Ascender Automation Platform on a single-node or highly available RKE2 cluster. - [Installing Ascender on RKE2 (Air-Gapped)](https://docs.ciq.com/ascender/installation/install-rke2-offline): Install Ascender on a fully air-gapped RKE2 cluster with no internet access. ## Ascender Pro Enterprise automation platform for IT infrastructure and application deployment - [Admin Guides](https://docs.ciq.com/ascender-pro/admin-guides): Administration guides for Ascender Pro. - [Admin Section](https://docs.ciq.com/ascender-pro/admin-guides/admin): Guide to the Admin section of Ascender Ledger Pro, covering Users, Teams, Servers, and Settings management. - [Configuration of Ascender](https://docs.ciq.com/ascender-pro/admin-guides/config): Guide for configuring Ascender to send logs to Ascender Ledger Pro. - [SAML Authentication](https://docs.ciq.com/ascender-pro/admin-guides/saml): Configure SAML 2.0 single sign-on for Ascender Ledger Pro against any standards-compliant identity provider. - [FAQs](https://docs.ciq.com/ascender-pro/faqs): Frequently asked questions about Ascender Pro. - [Ascender Pro](https://docs.ciq.com/ascender-pro): Enterprise platform for gathering, analyzing, and monitoring data across your infrastructure. - [Installing Ascender Pro](https://docs.ciq.com/ascender-pro/installation): Install Ascender Pro alongside Ascender for analytics, reporting, and log aggregation. - [Release Notes](https://docs.ciq.com/ascender-pro/release-notes): Release notes for Ascender Pro. - [Ascender Pro v1.0.0 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.0): Release notes for Ascender Pro v1.0.0 - [Ascender Pro v1.0.1 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.1): Release notes for Ascender Pro v1.0.1 - [Ascender Pro v1.0.2 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.2): Release notes for Ascender Pro v1.0.2 - [Ascender Pro v1.0.3 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.3): Release notes for Ascender Pro v1.0.3 - [Ascender Pro v1.0.4 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.4): Release notes for Ascender Pro v1.0.4 - [Ascender Pro v1.0.5 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.5): Release notes for Ascender Pro v1.0.5 - [Ascender Pro v1.0.6 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.6): Release notes for Ascender Pro v1.0.6 - [Ascender Pro v1.0.7 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.7): Release notes for Ascender Pro v1.0.7 - [Ascender Pro v1.0.8 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.8): Release notes for Ascender Pro v1.0.8 - [Ascender Pro v1.0.9 Release Notes](https://docs.ciq.com/ascender-pro/release-notes/v1.0.9): Release notes for Ascender Pro v1.0.9 - [User Guides](https://docs.ciq.com/ascender-pro/user-guides): User guides for Ascender Pro. - [Alerts Section](https://docs.ciq.com/ascender-pro/user-guides/alerts): Guide to configuring and managing alerts in Ascender Ledger Pro using providers and filters. - [Changes Section](https://docs.ciq.com/ascender-pro/user-guides/changes): Guide to the Changes section in Ascender Ledger Pro, which tracks automation-driven host changes from Ascender and AWX derivatives. - [Dashboard Section](https://docs.ciq.com/ascender-pro/user-guides/dashboard): Overview of the Ascender Ledger Pro dashboard, which provides real-time infrastructure statistics and customizable graphs. - [Errata Section](https://docs.ciq.com/ascender-pro/user-guides/errata): Guide to the Errata section in Ascender Ledger Pro, which tracks CVE exposure across Enterprise Linux hosts. - [Facts Section](https://docs.ciq.com/ascender-pro/user-guides/facts): Guide to the Facts section in Ascender Ledger Pro, which collects and displays Ansible fact data from hosts. - [Hosts Section](https://docs.ciq.com/ascender-pro/user-guides/hosts): Guide to the Hosts section in Ascender Ledger Pro, covering host inventory, packages, services, and errata per host. - [Packages Section](https://docs.ciq.com/ascender-pro/user-guides/packages): Guide to the Packages section in Ascender Ledger Pro, covering current package status and package log tracking across hosts. - [Reports Section](https://docs.ciq.com/ascender-pro/user-guides/reports): Guide to creating, editing, scheduling, and managing reports in Ascender Ledger Pro. - [Services Section](https://docs.ciq.com/ascender-pro/user-guides/services): Guide to the Services section in Ascender Ledger Pro, covering current service status and service log tracking across hosts. ## CIQ Bridge Extended-life security patching and package maintenance for CentOS 7.9 after end of life - [FAQ](https://docs.ciq.com/ciq-bridge/faqs): Common questions about CIQ Bridge remediation scope, architecture, and migration off CentOS 7. - [Getting Started](https://docs.ciq.com/ciq-bridge/getting-started): Entitle CIQ Bridge, install the Depot Client, and enable the Bridge repository on CentOS 7.9. - [CIQ Bridge](https://docs.ciq.com/ciq-bridge): Ongoing CVE remediation for CentOS 7.9 after end of life. - [Security and Errata](https://docs.ciq.com/ciq-bridge/security): How CIQ publishes signed CVE remediation, advisories, and errata feeds for CentOS 7.9 under CIQ Bridge. ## CIQ Portal Central hub for accessing CIQ software, managing organizations, and discovering products. - [FAQs](https://docs.ciq.com/ciq-portal/faqs): Frequently asked questions about the CIQ Portal - [Getting Started](https://docs.ciq.com/ciq-portal/getting-started): Guide to navigating and using the CIQ Portal to access CIQ software, services, and content - [Glossary](https://docs.ciq.com/ciq-portal/glossary): Glossary of terms used in CIQ Portal and related services - [CIQ Portal](https://docs.ciq.com/ciq-portal): Overview of CIQ Portal - your central hub for accessing CIQ software, managing organizations, and discovering products - [Troubleshooting](https://docs.ciq.com/ciq-portal/troubleshooting): Common issues and solutions for CIQ Portal - [User Guides](https://docs.ciq.com/ciq-portal/user-guides): Detailed guides for managing your CIQ Portal account, organization, and content access - [Accessing CIQ Content](https://docs.ciq.com/ciq-portal/user-guides/accessing-content): Methods for accessing CIQ software including direct downloads, Depot Client, HTTP downloads, rsync, reposync, Satellite, and container images - [Account Management](https://docs.ciq.com/ciq-portal/user-guides/account-management): Managing your CIQ Portal user account, profile settings, security, and privacy options - [Organization Management](https://docs.ciq.com/ciq-portal/user-guides/organization-management): Managing CIQ Portal organizations including members, invites, licenses, access tokens, event logs, and settings ## CIQ Depot Enterprise package repository and software distribution platform - [Depot Client](https://docs.ciq.com/depot/depot-client): Install and use the CIQ Depot Client CLI to manage repositories and access CIQ software - [Command Reference](https://docs.ciq.com/depot/depot-client/command-reference): Complete reference for all CIQ Depot Client CLI commands - [depot disable](https://docs.ciq.com/depot/depot-client/command-reference/disable): Remove the DNF configuration for a given product - [depot enable](https://docs.ciq.com/depot/depot-client/command-reference/enable): Enable one or more products by their IDs. Use --repo to enable specific repositories within a single product. - [depot help](https://docs.ciq.com/depot/depot-client/command-reference/help): Display help for depot commands. - [depot list](https://docs.ciq.com/depot/depot-client/command-reference/list): List available products or repositories. - [depot login](https://docs.ciq.com/depot/depot-client/command-reference/login): Authenticate with the depot server. - [depot upload](https://docs.ciq.com/depot/depot-client/command-reference/upload): Upload file to a repo - [Get Started](https://docs.ciq.com/depot/depot-client/get-started): Get started with the CIQ Depot Client - installation, setup, and basic usage - [Working with Container Images](https://docs.ciq.com/depot/depot-client/get-started/containers): Access CIQ container images using Docker and Podman - [Installing the Depot Client](https://docs.ciq.com/depot/depot-client/get-started/installation): How to install the CIQ Depot Client on your system - [Depot Client Maintenance](https://docs.ciq.com/depot/depot-client/get-started/maintenance): Keeping your Depot Client and CIQ repositories up to date - [Setting Up Your Host](https://docs.ciq.com/depot/depot-client/get-started/setting-up-host): Configure CIQ repositories on your system using the Depot Client - [How-To Guides](https://docs.ciq.com/depot/how-to-guides): Guides for mirroring repositories and integrating CIQ Depot with your infrastructure - [Installing Ansible Collections from Depot](https://docs.ciq.com/depot/how-to-guides/how-to-ansible-galaxy): How to install entitled Ansible collections from CIQ Depot using ansible-galaxy - [Mirroring Repositories with Reposync](https://docs.ciq.com/depot/how-to-guides/how-to-reposync): How to mirror CIQ repositories using DNF reposync - [Mirroring Repositories with Rsync](https://docs.ciq.com/depot/how-to-guides/how-to-rsync): How to create and maintain local mirrors of CIQ repositories using rsync - [Integrating CIQ Repositories with Red Hat Satellite](https://docs.ciq.com/depot/how-to-guides/how-to-satellite): Configure CIQ repositories in Red Hat Satellite for centralized content management - [CIQ Depot](https://docs.ciq.com/depot): CIQ's content delivery platform for software distribution ## CIQ Enterprise Linux Manager CIQ Enterprise Linux Manager - mirror repositories, curate versioned content views, and provision RPM-based Linux hosts over the network - [Admin guides](https://docs.ciq.com/elm/admin-guides): Managing CIQ ELM - sources, content views, hosts and groups, provisioning, authentication, permissions, integrations, and the REST API. - [API](https://docs.ciq.com/elm/admin-guides/api): Automate CIQ ELM with the browsable REST API at /api/v1/, authenticated with a session or HTTP Basic auth. - [Authentication](https://docs.ciq.com/elm/admin-guides/authentication): Sign in to CIQ ELM with local accounts, LDAP, or SAML 2.0, with automatic team placement from directory groups. - [Content views](https://docs.ciq.com/elm/admin-guides/content-views): Compose curated, versioned repositories with pin and exclude rules, custom RPM uploads, dependency checks, snapshots, and rollback. - [Hosts and groups](https://docs.ciq.com/elm/admin-guides/hosts-and-groups): Register machines with the CIQ ELM agent, inspect package state, organize nested groups, and assign content views and kickstarts. - [Integrations](https://docs.ciq.com/elm/admin-guides/integrations): Connect CIQ ELM to CIQ Depot, Ascender automation, and Ascender Ledger. - [MCP server](https://docs.ciq.com/elm/admin-guides/mcp): Enable CIQ ELM's optional read-only Model Context Protocol server for permission-scoped access by AI assistants. - [Provisioning](https://docs.ciq.com/elm/admin-guides/provisioning): Install Enterprise Linux over the network with iPXE, DHCP, TFTP, templated kickstarts, and the credentials vault. - [Settings and signing](https://docs.ciq.com/elm/admin-guides/settings-and-signing): Configure CIQ ELM's canonical URL, trusted proxies, retention, source cleanup, provisioning timeout, and OpenPGP repository metadata signing. - [Sources](https://docs.ciq.com/elm/admin-guides/sources): Mirror upstream package repositories into CIQ ELM from remote HTTP(S) URLs, rsync mirrors, uploaded ISOs, or the CIQ Depot catalog. - [Users, teams, and permissions](https://docs.ciq.com/elm/admin-guides/users-teams-permissions): Granular RBAC in CIQ ELM - users, teams, feature permissions, and the audit log. - [FAQs](https://docs.ciq.com/elm/faqs): Common questions about CIQ Enterprise Linux Manager, including supported distributions, security, access, air-gapped operation, and storage. - [Getting started](https://docs.ciq.com/elm/getting-started): First login, the dashboard, and the end-to-end workflow from mirroring a repository to serving packages to hosts. - [CIQ Enterprise Linux Manager](https://docs.ciq.com/elm): CIQ Enterprise Linux Manager - mirror repositories, curate versioned content views, and provision RPM-based Linux hosts over the network. - [Installation](https://docs.ciq.com/elm/installation): Install the CIQ ELM server RPM, configure CIQ Depot image access, and run the Podman deployment with systemd. - [Air-gapped considerations](https://docs.ciq.com/elm/installation/air-gapped): Running CIQ ELM in isolated environments - offline content ingestion through ISO upload and rsync, and what to expect without internet access. - [Release notes](https://docs.ciq.com/elm/release-notes): Release notes for all CIQ Enterprise Linux Manager (ELM) versions. - [CIQ Enterprise Linux Manager 0.1.0 (Aug 2026)](https://docs.ciq.com/elm/release-notes/rn-0.1.0): Initial release with sources, content views, provisioning, the agent, RBAC, integrations, and automation APIs. ## Fuzzball High Performance Computing (HPC) 2.0 - Orchestrate job-based workflows with ease across on-premises and cloud environments - [About These Guides](https://docs.ciq.com/fuzzball/about): If you're looking to understand, use, or administer Fuzzball, these guides are designed specifically for you, regardless of your level of HPC expertise. - [Advanced Features](https://docs.ciq.com/fuzzball/advanced-features): Fuzzball enables more advanced workflow features than simply starting, stopping, and checking logs. The following sections detail some of the more complex… - [Interacting with Other Users' Workflows](https://docs.ciq.com/fuzzball/advanced-features/add-owners): You can check the status of workflows started by other members of your group. To enable other group members to perform actions on your workflows, you can add… - [In-Workflow API Access](https://docs.ciq.com/fuzzball/advanced-features/in-workflow-api-access): Every job and service container in a workflow automatically receives a workflow-scoped API token, so processes running inside a workflow can call the Fuzzball… - [Job Hostnames](https://docs.ciq.com/fuzzball/advanced-features/job-hostnames): Important: Because jobs and services share the same DNS namespace within a workflow, their names must be globally unique. You cannot have a service and a job… - [Using OpenCode with a Fuzzball-Hosted Model](https://docs.ciq.com/fuzzball/advanced-features/opencode-access): OpenCode is a coding agent that talks to any OpenAI-compatible API. A model served on Fuzzball publishes that kind of API, so OpenCode can use a cluster GPU… - [Service Autoscaling](https://docs.ciq.com/fuzzball/advanced-features/service-autoscaling): Service autoscaling is an early-access feature. The syntax described here may evolve in future releases. - [Serving an AI Model](https://docs.ciq.com/fuzzball/advanced-features/serving-a-model): Fuzzball serves large language models from the workflow catalog. One command starts a model on a cluster GPU and gives you a base URL that speaks the OpenAI… - [Getting an Interactive Shell and Executing Commands](https://docs.ciq.com/fuzzball/advanced-features/shell-exec): It's easy to obtain a shell or execute a command in a container supporting a running job within your workflow. - [Connecting to Workflow Services](https://docs.ciq.com/fuzzball/advanced-features/workflow-connect): The fuzzball workflow connect command provides a convenient way to interact with a service running in a workflow. Depending on the service definition, it can… - [Workflow Endpoints](https://docs.ciq.com/fuzzball/advanced-features/workflow-endpoints): When a workflow service exposes network endpoints (configured via the network section in your workflow definition), the fuzzball workflow endpoints command… - [GPUs and Fabrics](https://docs.ciq.com/fuzzball/advanced-hardware): Fuzzball allows you to run workflows on GPUs with relative ease. Once you have a container with GPU accelerated code, you can build a workflow that utilizes… - [Using GPUs with Fuzzball](https://docs.ciq.com/fuzzball/advanced-hardware/gpus): Fuzzball intelligently passes GPU resources from the host through to the containers that support your jobs. Once an administrator has properly added and… - [Using High-Speed Fabrics with Fuzzball](https://docs.ciq.com/fuzzball/advanced-hardware/high-speed-interconnects): Fuzzball supports the use of traditional HPC high-speed interconnects like InfiniBand and Omni-Path, as well as more cloud oriented high-speed fabrics like… - [Appendices](https://docs.ciq.com/fuzzball/appendices): The appendices provide background information useful for understanding the main guides. - [Certificate Renewal and Monitoring](https://docs.ciq.com/fuzzball/appendices/certificate-lifecycle): Fuzzball deployments rely on several internal TLS certificates. On Kubernetes deployments these certificates are issued by cert-manager and renewed… - [Installing the CLI](https://docs.ciq.com/fuzzball/appendices/cli-installation): To interact with Fuzzball through the CLI, you must first install the CLI. - [Deploying with External cert-manager](https://docs.ciq.com/fuzzball/appendices/external-cert-manager): By default, the Fuzzball operator installs and manages its own cert-manager instance. If your cluster already has cert-manager (and optionally trust-manager)… - [FuzzballOrchestrate CRD Reference](https://docs.ciq.com/fuzzball/appendices/fuzzball-crd-reference): The FuzzballOrchestrate Custom Resource Definition (CRD) is the primary way to deploy and configure a Fuzzball cluster on Kubernetes. This CRD provides… - [Glossary](https://docs.ciq.com/fuzzball/appendices/glossary): The Fuzzball guides include many new terms that are specific to Fuzzball, as well as some familiar terms that are used in specific ways. This glossary is… - [Installing a basic RKE2 Kubernetes Cluster](https://docs.ciq.com/fuzzball/appendices/k8s-cluster): This section will guide you through the procedure for setting up a basic RKE2 cluster suitable for running Fuzzball. This procedure is intended for use with a… - [Initial Configuration](https://docs.ciq.com/fuzzball/appendices/k8s-cluster/config): Several steps must be carried out to prepare the server for K8s deployment. - [Environment Variables Used in Deployment](https://docs.ciq.com/fuzzball/appendices/k8s-cluster/envvars): This guide is designed to be completed primarily through copy-and-paste instructions. But some values cannot be anticipated and are therefore included as… - [Installing RKE2 on the Server Node](https://docs.ciq.com/fuzzball/appendices/k8s-cluster/install-rke2): After the initial configuration has been completed, you are ready to install RKE2. - [Remaining Dependencies](https://docs.ciq.com/fuzzball/appendices/k8s-cluster/remaining-deps): Fuzzball requires a few more components to be present and operational before using the operator for installation. - [Known Issues](https://docs.ciq.com/fuzzball/appendices/known-issues): Fuzzball is a quickly developing project. This page documents some known issues with the current version of Fuzzball. If you spot a bug or an issue, you can… - [Kubernetes Secret References](https://docs.ciq.com/fuzzball/appendices/kubernetes-secret-references): Fuzzball CRD fields that accept credentials — passwords, API keys, TLS certificates, and image pull secrets — support references to Kubernetes Secrets as an… - [Setting up a hosted zone with Route53](https://docs.ciq.com/fuzzball/appendices/route53): Fuzzball needs a domain to host services like keycloak, the Fuzzball API server, and the UI. On AWS, Fuzzball needs a "hosted zone" in Route53 for a domain.… - [CoreWeave Static Node Pool Provisioning](https://docs.ciq.com/fuzzball/appendices/static-provisioning): Support for CoreWeave within Fuzzball is in preview status and is currently subject to more rapid change to address customer requirements than other features… - [Access the Fuzzball Web UI through SSH](https://docs.ciq.com/fuzzball/appendices/web-ui-tunnel): This section will walk you through accessing the Fuzzball web UI running in a on-premises cluster using SSH tunneling. You'll use a SOCKS proxy to establish… - [Background](https://docs.ciq.com/fuzzball/appendices/web-ui-tunnel/background): Your Kubernetes deployment hosts the Fuzzball web UI. By default, the web UI isn't directly exposed to the outside world. In a bare-metal environment like the… - [Configure Browser for SOCKS Proxy](https://docs.ciq.com/fuzzball/appendices/web-ui-tunnel/browser-config): With the SOCKS proxy up and running, all that's left to do is to configure your web browser to use it. The specific steps to do this vary depending on your… - [Establish the SSH Tunnel](https://docs.ciq.com/fuzzball/appendices/web-ui-tunnel/create-tunnel): On your local workstation, open a terminal and establish an SSH connection with SOCKS proxy enabled: - [Accessing the Web Interface and Authentication](https://docs.ciq.com/fuzzball/appendices/web-ui-tunnel/visit-site): If you've followed the previous steps to establish an SSH tunnel and configure your browser to use the SOCKS proxy, you can now access the Fuzzball web UI… - [Fuzzfile Syntax Guide](https://docs.ciq.com/fuzzball/appendices/workflow-syntax): Workflows are the fundamental unit of work in Fuzzball, orchestrating container execution, data movement, and resource allocation across compute clusters.… - [Provisioner Administration](https://docs.ciq.com/fuzzball/central-config): The Fuzzball provisioner is responsible for allocating compute resources to run users' jobs. To perform this action, it must be configured to know what kinds… - [Provisioner Configuration Overview](https://docs.ciq.com/fuzzball/central-config/central-config): The provisioner configuration file is a YAML document that defines the following: - [Provisioner Configuration Reference](https://docs.ciq.com/fuzzball/central-config/configuration-reference): This document provides an exhaustive reference for all configuration parameters available in the Fuzzball central configuration system. The central… - [Cloud Deployment Guides](https://docs.ciq.com/fuzzball/cloud-admin-guide): These guides are intended for administrators who wish to install, configure, and maintain Fuzzball in a cloud environment. You can use Fuzzball in your AWS… - [Tracking AWS Cloud Spend](https://docs.ciq.com/fuzzball/cloud-admin-guide/billing): Using Fuzzball in the cloud incurs costs in several ways. - [Per-Workflow Charges](https://docs.ciq.com/fuzzball/cloud-admin-guide/billing/per-workflow-charges): Fuzzball tracks resource usage for each workflow it runs and exposes the results through the CLI. Use this view to attribute compute, storage, and egress… - [Cross-Cloud DNS Configuration](https://docs.ciq.com/fuzzball/cloud-admin-guide/cross-cloud-dns): When Fuzzball deploys a cluster, it requests TLS certificates from Let's Encrypt and validates them with DNS-01 challenges. By default the challenge records… - [Deployment](https://docs.ciq.com/fuzzball/cloud-admin-guide/deployment): After fulfilling the prerequisites listed in the requirements doc, you are ready to perform a deployment in your cloud environment. - [Connecting External Static Compute Nodes](https://docs.ciq.com/fuzzball/cloud-admin-guide/external-static-nodes): A cloud Fuzzball Orchestrate deployment normally provisions its own compute nodes on demand from the corresponding cloud provider. In addition it is possible… - [Requirements](https://docs.ciq.com/fuzzball/cloud-admin-guide/requirements): You will need a few things before you begin deploying your new Fuzzball cluster in the cloud. - [Validating Deployments](https://docs.ciq.com/fuzzball/cloud-admin-guide/validating-deployments): Fuzzball ships tiered readiness checks that validate a deployed, running cluster and print a sectioned report. Checks are grouped into the deployment… - [Local Deployment Guides](https://docs.ciq.com/fuzzball/cluster-admin-guide): These guides are intended for administrators who wish to deploy Fuzzball in an on-premises cluster. - [Install Fuzzball on an AMD Ryzen AI Max (Strix Halo)](https://docs.ciq.com/fuzzball/cluster-admin-guide/amd-halo): This guide covers the AMD Ryzen AI Max ("Strix Halo") specifics for bringing up a single-host Fuzzball cluster with GPU passthrough. It builds on the… - [Deployment](https://docs.ciq.com/fuzzball/cluster-admin-guide/cag-dct-deployment): After fulfilling the requirements, you are ready to deploy Fuzzball. Use the Kubernetes Operator tab for a multi-node, production-style deployment across… - [Docker Compose Stack](https://docs.ciq.com/fuzzball/cluster-admin-guide/cag-dct-docker-compose): The fuzzball cluster docker-compose deploy command brings up a single-host Fuzzball stack — nginx (TLS termination and subdomain routing), PostgreSQL,… - [Requirements](https://docs.ciq.com/fuzzball/cluster-admin-guide/cag-dct-requirements): Requirements differ depending on how you deploy Fuzzball. Use the Kubernetes Operator tab for a multi-node, production-style deployment, or the Docker Compose… - [Impersonating Users for Troubleshooting](https://docs.ciq.com/fuzzball/cluster-admin-guide/cag-impersonating-users): Cluster administrators can temporarily assume the identity of any user in any organization to troubleshoot issues, reproduce bugs, or verify permissions. When… - [Install Fuzzball on an NVIDIA DGX Spark](https://docs.ciq.com/fuzzball/cluster-admin-guide/dgx-spark): This guide covers the NVIDIA DGX Spark specifics for bringing up a single-host Fuzzball cluster with GPU passthrough. It builds on the platform-agnostic… - [Creating Fuzzfiles](https://docs.ciq.com/fuzzball/creating-fuzzfiles): Fuzzball runs workflows that are composed of one or more jobs. Each job in a workflow runs some specified command(s), executes within an environment… - [Adding Dependent Jobs and Volumes](https://docs.ciq.com/fuzzball/creating-fuzzfiles/adding-jobs): Let's expand on the previous example by creating a second job that will run after the first job. In our example, the second job should take the fortune… - [Building Images in a Workflow](https://docs.ciq.com/fuzzball/creating-fuzzfiles/building-images): Sometimes no public container has quite what your job needs. Rather than building an image on your workstation and pushing it to a registry first, you can… - [Notes on Containers](https://docs.ciq.com/fuzzball/creating-fuzzfiles/container-urls): All jobs in a given Fuzzball workflow run within containers. You can find containers for your jobs in public registries like Docker Hub, Amazon Elastic… - [Using Encrypted SIF Images](https://docs.ciq.com/fuzzball/creating-fuzzfiles/encrypted-sif-images): Fuzzball supports running jobs with encrypted SIF (Singularity Image Format) images. This feature enables you to protect sensitive container images by… - [Host Networking for Multinode Services](https://docs.ciq.com/fuzzball/creating-fuzzfiles/host-networking-multinode): Multinode services always run with host networking: every rank runs directly on its node's network stack instead of in an isolated network namespace. Fuzzball… - [Complicated Job DAGs, Ingress, and Egress](https://docs.ciq.com/fuzzball/creating-fuzzfiles/multi-job-ingress-and-egress): We can continue to build upon this Fuzzfile to create a workflow with a more complicated Directed Acyclic Graph (DAG) of jobs and dependencies. We'll also… - [A First Basic Workflow](https://docs.ciq.com/fuzzball/creating-fuzzfiles/simple-workflow): Let's create a job that uses a lolcow image from Docker Hub to run the fortune command and produce a random fortune/quote/joke. We'll start by showing the… - [Before We Begin](https://docs.ciq.com/fuzzball/creating-fuzzfiles/starting-note): This guide will show you how to build a Fuzzball workflow in multiple steps using the workflow editor. At the conclusion of every step we will show the… - [Debugging](https://docs.ciq.com/fuzzball/debugging): This section provides documentation for debugging and troubleshooting Fuzzball clusters. These tools are designed for administrators to diagnose issues,… - [Entities](https://docs.ciq.com/fuzzball/entities): Fuzzball supports the use of organizations, groups, and users. These entities enable a Fuzzball admin to control access to a Fuzzball deployment. The entities… - [Accounts](https://docs.ciq.com/fuzzball/entities/ent-accounts): Groups enable organizations to control a user's access to resources definitions, secrets, and storage volumes. They also enable a group of users to share… - [Entities Illustration](https://docs.ciq.com/fuzzball/entities/ent-illustration): The following page will walk through an example which ties the concepts of Fuzzball organizations, users, and groups together. Consider the example below: - [Organizations](https://docs.ciq.com/fuzzball/entities/ent-organizations): An organization within Fuzzball houses sets of users and groups. When adding a user to an organization, the user can be added as an organization owner or an… - [Roles and Permissions](https://docs.ciq.com/fuzzball/entities/ent-permissions): The table below illustrates the permissions of roles which can manipulate organizations and their membership. - [Users](https://docs.ciq.com/fuzzball/entities/ent-users): A Fuzzball user is created under an organization by the organization owner. The user can be added as an organization owner or an organization member. - [Fuzzball Entity Management](https://docs.ciq.com/fuzzball/entity-admin): Fuzzball uses the following entities to control access to deployments, resources, and workflows: - [Group Management](https://docs.ciq.com/fuzzball/entity-admin/account-admin): Once users have been added into your Fuzzball deployment under an organization as described in the Adding Users to Organizations section, you can begin… - [Adding Users to Groups](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-adding-users): In order to add users to a group, you will need organization owner or group owner permissions. Users can be added to a group using either the web UI or the… - [Managing a Group Compute Policy](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-compute-policy): Each group has its own compute policy that further restricts which instance types the group's members can run workflows on. A group's policy is bounded above… - [Creating Groups](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-creation): In order to create Fuzzball groups, your user will need organization owner permissions. Groups can be created using either the web UI or the CLI. Follow the… - [Deleting Groups](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-deletion): In order to delete groups, you will need organization owner permissions. Groups can be deleted using either the web UI or the CLI. Follow the instructions in… - [Listing Group Members](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-listing-members): You can list the members of a Fuzzball group using the CLI fuzzball group member list command. Group members and their owner status can also be viewed through… - [Removing Users from Groups](https://docs.ciq.com/fuzzball/entity-admin/account-admin/acc-removing-users): In order to remove users from a group, you will need organization owner or group owner permissions. Users can be removed from a group using either the web UI… - [Organization Management](https://docs.ciq.com/fuzzball/entity-admin/org-admin): After Fuzzball has been deployed on your system, you will first need to create an organization before you are able to add Fuzzball users. - [Managing the Organization Compute Policy](https://docs.ciq.com/fuzzball/entity-admin/org-admin/oa-compute-policy): An organization's compute policy is the set of compute instance types that users in the organization are permitted to run workflows on. Every instance type… - [Creating Organizations](https://docs.ciq.com/fuzzball/entity-admin/org-admin/oa-creation): Cluster administrators can create an organization with the Fuzzball CLI subcommand organization create. There is no web UI equivalent. - [Deleting Organizations](https://docs.ciq.com/fuzzball/entity-admin/org-admin/oa-deletion): Cluster administrators can delete an organization with the Fuzzball CLI subcommand organization delete. There is no web UI equivalent. - [Listing Organizations](https://docs.ciq.com/fuzzball/entity-admin/org-admin/oa-listing): Cluster administrators can list every organization in the cluster with the Fuzzball CLI subcommand organization list. Use it to find the organization IDs… - [Listing Organization Members](https://docs.ciq.com/fuzzball/entity-admin/org-admin/oa-listing-members): You can list the members of a Fuzzball organization using the CLI fuzzball org member list command. Organization members and their owner status can also be… - [User Management](https://docs.ciq.com/fuzzball/entity-admin/user-admin): Once your organization has been created, you can begin to add users to, or remove them from your organization. This section will show examples for both using… - [Adding Users to Organizations](https://docs.ciq.com/fuzzball/entity-admin/user-admin/ua-adding-users): New users are created by adding them to an organization using either the web UI or the CLI. Follow the instructions for your preferred method below. - [Managing Passwords](https://docs.ciq.com/fuzzball/entity-admin/user-admin/ua-managing-passwords): Fuzzball provides two password management workflows: users can change their own password through a self-service flow, and organization owners can reset a… - [Removing Users from Organizations](https://docs.ciq.com/fuzzball/entity-admin/user-admin/ua-removing-users): An organization owner can remove members and other owners of the organization using the web UI or the CLI. - [Federate Admin Guides](https://docs.ciq.com/fuzzball/federate-admin-guide): These guides are intended for administrators who wish to install, configure, and maintain Fuzzball Federate. Federate gives you the ability to combine… - [Accessing and Configuring Federate](https://docs.ciq.com/fuzzball/federate-admin-guide/access): Once your Federate cluster has been deployed. You can gather the appropriate information by running a convenience script provided by CIQ. For these steps to… - [Deployment](https://docs.ciq.com/fuzzball/federate-admin-guide/deployment): After fulfilling the prerequisites from the requirements doc, you are ready to deploy Federate in an existing K8s cluster that already supports Fuzzball. - [Requirements](https://docs.ciq.com/fuzzball/federate-admin-guide/requirements): You need a few things before you begin deploying your new Federate instance. - [Scheduling Priority and Preemption in Federate](https://docs.ciq.com/fuzzball/federate-admin-guide/scheduling): Federate deployments use the same scheduling priority and preemption features as standalone Fuzzball clusters, with one key difference: the scheduling… - [Fuzzball Guides](https://docs.ciq.com/fuzzball): Welcome to the Fuzzball guides! These pages will teach you everything that you need to create and run workflows in Fuzzball! - [Initial Configuration](https://docs.ciq.com/fuzzball/initial-configuration): After installing Fuzzball, you need to log in to your newly created cluster as an administrator and complete four configuration steps so you (and potentially… - [Initial Entity Management](https://docs.ciq.com/fuzzball/initial-configuration/entity-management): If you expect other people to use your Fuzzball cluster, you can create new users and manage them by (optionally) setting up new organizations and groups.… - [Initial Login](https://docs.ciq.com/fuzzball/initial-configuration/initial-login): To configure your Fuzzball cluster for use, you must first log in. This section will guide you through the process of creating a Fuzzball context and an admin… - [Next Steps](https://docs.ciq.com/fuzzball/initial-configuration/nextsteps): Congratulations! This concludes the initial basic configuration of your Fuzzball cluster! - [Basic Provisioner Configuration](https://docs.ciq.com/fuzzball/initial-configuration/provisioner-config): You can set a provisioner configuration to add one or more compute nodes running Substrate to your cluster. The configuration process varies depending on your… - [Storage Configuration](https://docs.ciq.com/fuzzball/initial-configuration/storage-config): Fuzzball V4 uses storage provisioners to manage storage. A provisioner combines a built-in storage driver with access policies in a single configuration —… - [MCP Server for LLM Agents](https://docs.ciq.com/fuzzball/mcp-server): The Fuzzball CLI can run a Model Context Protocol (MCP) server that exposes cluster operations as tools an LLM agent can call. This lets an assistant such as… - [Querying Compute Nodes](https://docs.ciq.com/fuzzball/nodes): Fuzzball provides visibility into the compute nodes in your Fuzzball cluster. Nodes are physical or virtual machines that execute your workflow's jobs. Each… - [Listing Nodes](https://docs.ciq.com/fuzzball/nodes/listing-nodes): List all compute nodes in your Fuzzball cluster - [Getting Node Details](https://docs.ciq.com/fuzzball/nodes/node-details): Get detailed information on a specific compute node in your Fuzzball cluster. - [Object Cache](https://docs.ciq.com/fuzzball/object-cache): The Fuzzball Object Cache is a built-in store for sharing files, data, and container images across workflows and clusters. Objects are addressed with fb://… - [Overview](https://docs.ciq.com/fuzzball/overview): HPC clusters really haven't changed much since the mid 1990's when the first Beowulf cluster was built at NASA. This means that HPC users rely on outdated,… - [Parallel / Distributed Jobs](https://docs.ciq.com/fuzzball/parallel-and-distributed): The terms parallel and distributed can mean different things depending on the person and context. In these guides, parallel jobs mean collections of tasks… - [Distributed Workflows with Generic Multinode](https://docs.ciq.com/fuzzball/parallel-and-distributed/generic): Fuzzball supports a generic multinode implementation that allows you to run custom commands or scripts across multiple nodes without being tied to a specific… - [Distributed Workflows with MPI](https://docs.ciq.com/fuzzball/parallel-and-distributed/mpi): Fuzzball supports distributed jobs that use MPI. - [Parallel Workflows with Job Arrays](https://docs.ciq.com/fuzzball/parallel-and-distributed/parallel): Fuzzball supports parallel workloads through task arrays. - [Distributed Workflows with PGAS](https://docs.ciq.com/fuzzball/parallel-and-distributed/pgas): Partitioned global address space (PGAS) networks are an alternative to MPI that use a multinode shared memory space to support parallelism. GASNet is an… - [Fuzzball in 15 Minutes](https://docs.ciq.com/fuzzball/quick-start): Fuzzball orchestrates job-based workflows that run in Linux containers. This hands-on tutorial is designed to get you up and running with Fuzzball in 15… - [Getting Your First Workflow](https://docs.ciq.com/fuzzball/quick-start/uqs-initial-workflow): Your Fuzzball cluster hosts a list of prebuilt Fuzzfile templates in the Workflow Catalog. These templates create the YAML files that define workflows, and… - [Interacting with Your Running Workflow](https://docs.ciq.com/fuzzball/quick-start/uqs-interacting-with-workflows): You can check the status of a workflow and retrieve its logs, both while it runs and after it finishes. See Checking Workflow Status and Retrieving Job Logs… - [Retrieving Job Logs](https://docs.ciq.com/fuzzball/quick-start/uqs-interacting-with-workflows/uqs-retrieve-logs): You can retrieve logs from jobs within a workflow. These can be retrieved after the job has completed, or streamed in real time as the job runs. - [Checking Workflow Status](https://docs.ciq.com/fuzzball/quick-start/uqs-interacting-with-workflows/uqs-workflow-status): Workflows, jobs, and other stages (such as pulling containers and setting up volumes) each report a status. The ones you will see most often are: - [Logging In and Selecting Your Group](https://docs.ciq.com/fuzzball/quick-start/uqs-logging-in): After deciding whether to use the web UI or the CLI to interact with Fuzzball and confirming that you meet all prerequisites, you can log in. Follow the… - [Next Steps](https://docs.ciq.com/fuzzball/quick-start/uqs-next-steps): This concludes your tour of the Fuzzball basics. Most workflows will additionally require the use of Volumes for data ingress/egress and Secrets for accessing… - [Prerequisites](https://docs.ciq.com/fuzzball/quick-start/uqs-prerequisites): There are a few prerequisites to check off before you begin. Make sure you have the following: - [Starting and Stopping Your New Workflow](https://docs.ciq.com/fuzzball/quick-start/uqs-starting-and-stopping-workflows): Now that you have a Fuzzfile loaded into the web UI or saved on your file system for use with the CLI, you are ready to run your first workflow. - [Release Notes](https://docs.ciq.com/fuzzball/release-notes): Release notes for each Fuzzball 4.x release, newest first. Each page covers the changes since the release it was cut against, so when upgrading across more… - [Fuzzball v4.0.0 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.0.0): Fuzzball v4.0.0 is a major release. It rearchitects storage around a simpler two-tier provisioner-and-volume model, promotes the external API to v4 as a… - [Fuzzball v4.0.1 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.0.1): Fuzzball v4.0.1 stabilizes the v4.0.0 release with fixes across federation, storage, cloud deployments, and the CLI. It also enhances the object cache with… - [Fuzzball v4.0.2 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.0.2): Fuzzball v4.0.2 is a patch release carrying a single fix: an internal NATS JetStream cluster name conflict that could stall a rolling upgrade away from… - [Fuzzball v4.1.0 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.1.0): Fuzzball v4.1.0 is a minor release built around scheduling. Queued work is now ranked by a cluster-configurable priority expression, higher-priority work can… - [Fuzzball v4.1.1 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.1.1): Fuzzball v4.1.1 is a patch release that hardens the scheduling and service work introduced in v4.1.0. Services now publish their declared ports on randomly… - [Fuzzball v4.1.2 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.1.2): Fuzzball v4.1.2 is a patch release that corrects the service host-port behavior introduced in v4.1.1, unblocks multi-GB object-cache transfers such as large… - [Fuzzball v4.2.0 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.2.0): Fuzzball v4.2.0 is a large minor release built around cluster reliability and multi-tenancy. Compute nodes now report hardware health, earn a reliability… - [Fuzzball v4.2.1 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.2.1): Fuzzball v4.2.1 is a patch release that makes the AWS v4.1.0 -> v4.2.0 in-place upgrade reliable. The upgrade previously wedged in about one in ten attempts… - [Fuzzball v4.2.2 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.2.2): Fuzzball v4.2.2 is a patch release that fixes an AWS deployment failure affecting stack updates -- including in-place upgrades -- for deployments with large… - [Fuzzball v4.2.3 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.2.3): Fuzzball v4.2.3 is a patch release that makes volume ownership correct on LDAP-federated deployments and makes the in-workflow API token usable on clusters… - [Fuzzball v4.3.0 release notes](https://docs.ciq.com/fuzzball/release-notes/v4.3.0): Fuzzball v4.3.0 is a feature release. - [Scheduler Administration](https://docs.ciq.com/fuzzball/scheduler-admin): The Fuzzball scheduler is responsible for placing and managing jobs on compute nodes in your cluster. As a cluster administrator, you can monitor and manage… - [Node Management](https://docs.ciq.com/fuzzball/scheduler-admin/node-management): Cluster administrators can control the scheduling behavior of compute nodes in the Fuzzball cluster. You can mark nodes as unschedulable (cordoned) or… - [Node Cordoning and Uncordoning](https://docs.ciq.com/fuzzball/scheduler-admin/node-management/node-cordoning): Node cordoning is the process of marking compute nodes as unschedulable, preventing new workflows from being placed on them. This is commonly used during… - [Node Health Monitoring](https://docs.ciq.com/fuzzball/scheduler-admin/node-management/node-health): Fuzzball compute nodes report their own health to the control plane. Each node sends a periodic heartbeat carrying hardware health signals, which lets the… - [Node Get and List](https://docs.ciq.com/fuzzball/scheduler-admin/node-management/node-listing): The Fuzzball scheduler provides commands to list all compute nodes and retrieve detailed information about specific nodes. These commands are essential for… - [Removing Node Registrations](https://docs.ciq.com/fuzzball/scheduler-admin/node-management/node-removal): A compute node appears in Fuzzball because its agent registers with the control plane and reports what hardware it has. That registration is what makes the… - [Queue and Scheduling Observability](https://docs.ciq.com/fuzzball/scheduler-admin/queue-observability): Fuzzball exposes the scheduler queue so you can see what is waiting, what is running, and — for any allocation that is not yet running — why. Three commands… - [Workflow Priority](https://docs.ciq.com/fuzzball/scheduler-admin/workflow-priority): Fuzzball orders queued work by an effective priority the scheduler recomputes every tick. Workflows with a higher effective priority are placed first, and a… - [Deleting and Retaining Workflows](https://docs.ciq.com/fuzzball/scheduler-admin/workflow-retention): A workflow record outlives the work it describes. Once a workflow finishes, its row and everything recorded alongside it -- stages, events, job metrics,… - [Client SDK](https://docs.ciq.com/fuzzball/sdk): Fuzzball enables you to generate a Fuzzball client Software Development Kit (SDK) for multiple languages from the API using Swagger! This makes it easy to… - [Authentication](https://docs.ciq.com/fuzzball/sdk/sdk-auth): The Fuzzball client SDK is designed to interact with the Fuzzball API client after a valid Fuzzball API token has been obtained. To obtain this token, you can… - [Coding Examples](https://docs.ciq.com/fuzzball/sdk/sdk-coding-examples): The following sections walk through the process of executing various Fuzzball operations using the Python SDK. Usage in other programming languages will… - [Initializing the Fuzzball Workflow Service API](https://docs.ciq.com/fuzzball/sdk/sdk-coding-examples/sdk-code-init-api): This demo requires the Fuzzball CLI to be set up in your environment. For more information please see the documentation on installing the Fuzzball CLI. - [Listing Workflows](https://docs.ciq.com/fuzzball/sdk/sdk-coding-examples/sdk-code-listwfs): After initialization, Python can leverage the Fuzzball API by referencing the variable apiinstance. The code snippet below requests a list of Fuzzball… - [Getting the Status of Workflows](https://docs.ciq.com/fuzzball/sdk/sdk-coding-examples/sdk-code-statuswfs): After initialization, Python can leverage the Fuzzball API by referencing the variable apiinstance. The code snippet below uses the Fuzzball API to get the… - [Submitting Workflows](https://docs.ciq.com/fuzzball/sdk/sdk-coding-examples/sdk-code-submittingwfs): After initialization, Python can leverage the Fuzzball API by referencing the variable apiinstance. The code snippet below uses the Fuzzball workflow service… - [SDK Generation using Swagger Codegen](https://docs.ciq.com/fuzzball/sdk/sdk-generation): First, we'll generate the Fuzzball client SDK for Python using Swagger Codegen in an Apptainer container. - [SDK Installation](https://docs.ciq.com/fuzzball/sdk/sdk-installation): After the Python client SDK has been generated in the directory /python-fuzzball, it can be installed into your Python environment using the command below. - [SDK Prerequisites](https://docs.ciq.com/fuzzball/sdk/sdk-prerequisites): Before proceeding with the SDK generation and installation process, please ensure you have the following prerequisites configured in your environment: - [Secrets](https://docs.ciq.com/fuzzball/secrets): Fuzzball supports the storage of sensitive information within a context as a “secret”. Secrets can be things like credentials for privately-hosted container… - [Adding Secrets](https://docs.ciq.com/fuzzball/secrets/sec-adding): Credentials can be added as group or user scoped secrets. These credentials can be used to access resources such as containers in a private OCI registry or… - [Using Secrets in Workflows](https://docs.ciq.com/fuzzball/secrets/sec-in-workflows): After your secrets have been created, you can reference them when building your workflows in the Fuzzball web UI or within a Fuzzfile to access containers in… - [Secret Scope](https://docs.ciq.com/fuzzball/secrets/sec-scope): Fuzzball enables users to create secrets at the group or user level of scope. Group scoped secrets are usable by all members of the given Fuzzball group. User… - [Secret specification YAML files](https://docs.ciq.com/fuzzball/secrets/sec-specs): If you plan on creating secrets with the web UI, you can skip ahead to the section on adding secrets and select the web UI tab. - [HuggingFace](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-hf): The following syntax is appropriate for a secret that authenticates to the HuggingFace Hub. - [HTTP(S)](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-http): The following syntax is appropriate for secrets associated with http(s) URLs. - [Container Registry](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-image): Secrets associated with OCI container registries can be specified in a YAML file with the following syntax. - [S3](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-s3): The following syntax is appropriate for adding a secret associated with an S3 bucket. - [SIF Image Decryption](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-sif-decryption): Secrets for decrypting encrypted SIF (Singularity Image Format) images can be specified in a YAML file with the following syntax. - [Arbitrary Value](https://docs.ciq.com/fuzzball/secrets/sec-specs/sec-spec-value): The following syntax is good for adding any arbitrary value as a secret for use in your workflows. - [Types of Secrets](https://docs.ciq.com/fuzzball/secrets/sec-types): Secrets are stored by Fuzzball as data structures (technically Go maps). Different types of secrets have different fields which may be required or optional.… - [Updating Existing Secrets](https://docs.ciq.com/fuzzball/secrets/sec-updating): If you need to change one of your secrets you can (and should) simply update it so that you can continue to use your existing Fuzzfiles without updating them. - [Slurm and PBS Integration](https://docs.ciq.com/fuzzball/slurm-pbs-integration): Fuzzball integration with the Slurm and PBS batch scheduling systems enables you to leverage existing HPC clusters as compute resources for running Fuzzball… - [Orchestrate Configuration](https://docs.ciq.com/fuzzball/slurm-pbs-integration/orchestrator-config): The Orchestrate configuration defines how Fuzzball connects to your Slurm or PBS cluster. This configuration is specified in the FuzzballOrchestrate Custom… - [Provisioner Configuration](https://docs.ciq.com/fuzzball/slurm-pbs-integration/provisioner-config): Node provisioners specify the node resources available through Slurm or PBS and how workflows should request them. They are created through Fuzzball's… - [Requirements](https://docs.ciq.com/fuzzball/slurm-pbs-integration/requirements): Before setting up the Slurm or PBS integration for Fuzzball, you should ensure you have met these requirements. - [Troubleshooting](https://docs.ciq.com/fuzzball/slurm-pbs-integration/troubleshooting): This guide covers common issues you may encounter when using Fuzzball with Slurm or PBS integration and provides detailed troubleshooting steps and solutions. - [Workflow Submission](https://docs.ciq.com/fuzzball/slurm-pbs-integration/workflow-submission): Once you have configured Fuzzball to use either Slurm or PBS as a node provisioner backend and created node provisioners, you can submit workflows to run on… - [Updating Fuzzball](https://docs.ciq.com/fuzzball/updating): You can (and should!) update your Fuzzball cluster when new versions are released. The update process differs somewhat depending on the environment. - [Volume Configuration and Management](https://docs.ciq.com/fuzzball/volume-admin): Fuzzball manages storage through two components: - [Storage Provisioners](https://docs.ciq.com/fuzzball/volume-admin/provisioners): Fuzzball V4 uses storage provisioners to manage how volumes are created, accessed, and stored on your cluster. A provisioner is a single entity that combines… - [Access Policies](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-access-policies): Storage provisioners control which members of an organization can access, create, or use ephemeral volumes. Each provisioner defines three independent… - [Annotations and Selection](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-annotations-and-selection): When a workflow uses an ephemeral volume without naming a specific provisioner, Fuzzball automatically selects a provisioner based on annotations and group… - [Provisioner Definitions](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-definitions): A provisioner definition is a YAML file that describes how a storage provisioner operates: which driver to use, how to connect to the storage backend, and… - [Driver Types](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-driver-types): Fuzzball V4 includes seven built-in storage drivers. Each driver handles a different type of storage backend. All drivers are built into the Fuzzball platform… - [Provisioner Management](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-management): Storage provisioners are managed with the fuzzball volume provisioner command. Organization owners can manage provisioners for their organization. - [Tenant Isolation](https://docs.ciq.com/fuzzball/volume-admin/provisioners/provisioner-tenant-isolation): In a deployment that serves more than one organization, storage has to keep those organizations apart. This page describes how Fuzzball does that, and what an… - [Storage Classes](https://docs.ciq.com/fuzzball/volume-admin/storage-classes): Deprecated (V3 Only) — Storage Classes were removed in Fuzzball V4. This page documents the V3 system and is retained as reference only. These instructions… - [Storage Class Definitions](https://docs.ciq.com/fuzzball/volume-admin/storage-classes/sc-storageclassdefs): Deprecated (V3 Only) — Storage Classes were removed in Fuzzball V4. This page documents the V3 system and is retained as reference only. These instructions… - [Storage Class Management](https://docs.ciq.com/fuzzball/volume-admin/storage-classes/sc-storageclassmgmt): Deprecated (V3 Only) — Storage Classes were removed in Fuzzball V4. This page documents the V3 system and is retained as reference only. These instructions… - [Storage Drivers](https://docs.ciq.com/fuzzball/volume-admin/storage-drivers): V3 Only — In Fuzzball V4, storage drivers are built into the platform and do not require external CSI-based driver containers. This page documents the V3… - [Storage Drivers Definitions](https://docs.ciq.com/fuzzball/volume-admin/storage-drivers/sd-storagedriverdefs): V3 Only — In Fuzzball V4, storage drivers are built into the platform and do not require external CSI-based driver containers. This page documents the V3… - [Storage Driver Management](https://docs.ciq.com/fuzzball/volume-admin/storage-drivers/sd-storagedrivermgmt): V3 Only — In Fuzzball V4, storage drivers are built into the platform and do not require external CSI-based driver containers. This page documents the V3… - [Storage Volumes](https://docs.ciq.com/fuzzball/volume-admin/storage-volumes): Storage volumes are directories or resources on a storage backend that are mounted into workflow containers. Each volume belongs to a storage provisioner… - [Storage Volume Definitions](https://docs.ciq.com/fuzzball/volume-admin/storage-volumes/sav-defs): Persistent volumes must be created before they are referenced in a workflow. You can create them using the CLI, web UI, or API. Below is the CLI method — you… - [Storage Volume Management](https://docs.ciq.com/fuzzball/volume-admin/storage-volumes/sav-storagevolumemgmt): This section covers explicit management of storage volumes. The section on storage volumes and workflows covers automatic creation of storage volumes by… - [Storage Volumes and Workflows](https://docs.ciq.com/fuzzball/volume-admin/storage-volumes/sav-workflows): Storage volumes are used in workflows through the volumes: section using the V4 provisioner-based syntax. Persistent volumes must be created explicitly (via… - [V4 Storage Breaking Changes](https://docs.ciq.com/fuzzball/volume-admin/v4-breaking-changes): This page summarizes the storage-related breaking changes between Fuzzball V3 and V4. For step-by-step upgrade instructions, see the V3 to V4 Storage… - [V3 to V4 Storage Migration](https://docs.ciq.com/fuzzball/volume-admin/vac-v3-to-v4-migration): When upgrading from Fuzzball V3 to V4, the storage system is automatically migrated from the V3 three-tier model (Storage Driver, Storage Class, Storage… - [Using Volumes](https://docs.ciq.com/fuzzball/volumes): HPC jobs typically require data. Volumes allow your jobs to access external data, allow multiple jobs within the same workflow to share data, and provide a… - [Examples](https://docs.ciq.com/fuzzball/volumes/vols-examples): The following examples illustrate the use of ephemeral and persistent volumes. There are examples of volume creation, data ingress, mounting, and egress using… - [Example 2. Data Ingress and Egress using an Ephemeral Volume](https://docs.ciq.com/fuzzball/volumes/vols-examples/vols-ex-ingress-egress-ephemeral): This builds upon the previous example. Instead of using data ingress to pull a single raw file from the GitHub repo, we will download the entire repo (as a… - [Example 1. Data Ingress using an Ephemeral Volume](https://docs.ciq.com/fuzzball/volumes/vols-examples/vols-ex-ingress-ephemeral): This example demonstrates how volume creation, data ingress, and mounts work. We will create an ephemeral volume (called ephvol1), accomplish data ingress… - [Example 3. Reading and Writing Data on a Persistent Volume](https://docs.ciq.com/fuzzball/volumes/vols-examples/vols-ex-persistent): Persistent Volumes can obviate the need for data ingress and egress. A persistent volume may already have the data needed to execute a workflow when it is… - [Closing Notes and Next Steps](https://docs.ciq.com/fuzzball/volumes/vols-notes): Each workflow can create/use an arbitrary number of volumes and carry out any amount of data ingress and egress. However, it is a good practice to minimize… - [Volume Operations](https://docs.ciq.com/fuzzball/volumes/vols-operations): Suppose you have raw data in an AWS S3 bucket. You create a workflow with several jobs that process and analyze the data in multiple steps. You need to… - [Creation](https://docs.ciq.com/fuzzball/volumes/vols-operations/vols-ops-creation): Volume creation happens on demand for ephemeral volumes. In contrast Persistent volumes need to be created explicitly via the CLI, web UI, or API prior to… - [Egress](https://docs.ciq.com/fuzzball/volumes/vols-operations/vols-ops-egress): Egress is the last stage of workflow execution, during which any desired data is exported to an outside destination. This could be output, processed data,… - [Ingress](https://docs.ciq.com/fuzzball/volumes/vols-operations/vols-ops-ingress): Ingress is one of the first stages of workflow execution, where any data needed for your workflow is imported to your volume from an outside source. This… - [Mounts](https://docs.ciq.com/fuzzball/volumes/vols-operations/vols-ops-mounts): Fuzzball locates or creates the volumes referenced in your workflow specification YAML as one of the first stages in your workflow. It then mounts the… - [Workflow Catalog](https://docs.ciq.com/fuzzball/workflow-catalog): The Fuzzball workflow catalog makes it easy for you to create Fuzzfiles and launch workflows based on pre-existing templates! Workflow templates contain… - [Catalog Repositories](https://docs.ciq.com/fuzzball/workflow-catalog/catalog-repositories): Catalog repositories allow you to import a set of application templates from external Git repositories into the Fuzzball workflow catalog. This enables you to… - [Admin Commands](https://docs.ciq.com/fuzzball/workflow-catalog/catalog-repositories/admin-commands): This page documents the administrator commands for managing catalog repositories. These commands provide additional capabilities beyond the standard user… - [User Commands](https://docs.ciq.com/fuzzball/workflow-catalog/catalog-repositories/user-commands): This page documents the user-facing commands for managing catalog repositories. These commands allow regular users to import, manage, and synchronize their… - [Copying and Editing Existing Templates](https://docs.ciq.com/fuzzball/workflow-catalog/copying): You can create your own templates in the workflow catalog. The simplest way to do this is to copy an existing template and edit it. - [Creating New Templates](https://docs.ciq.com/fuzzball/workflow-catalog/creating): You can create your own templates in the workflow catalog that you or your colleagues can use to render fuzzfiles and run workflows. - [Fuzzfiles From Existing Templates](https://docs.ciq.com/fuzzball/workflow-catalog/existing-templates): The Workflow Catalog is prepopulated with a set of official CIQ templates based on common applications and workflows. If you use a shared group, you may also… - [Workflow Examples](https://docs.ciq.com/fuzzball/workflow-examples): This section provides a range of workflow examples, from general to specific, including: - [Basic Examples](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples): This section provides a set of basic Fuzzfile examples that demonstrate Fuzzball workflow concepts and features. These examples include: - [Jupyter Notebook](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples/jupyter-notebook): Jupyter Server is a well-known standard web application for creating and sharing computational documents. It offers a simple, streamlined, document-centric… - [Accessing the Jupyter Server UI](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples/jupyter-notebook/nb-access-ui): To access the Jupyter Server, select the jupyter service in the workflow you started earlier and click the CONNECT button that appears below the workflow… - [Starting a Jupyter Notebook](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples/jupyter-notebook/nb-start): The instructions below will walk you through the process of launching a Jupyter Server workflow using the Fuzzball workflow catalog. The workflow catalog will… - [Stopping a Jupyter Notebook](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples/jupyter-notebook/nb-stop): When you are done using your Jupyter Notebook, you can stop the Jupyter Notebook by stopping the workflow through Fuzzball web UI or CLI. - [Printer](https://docs.ciq.com/fuzzball/workflow-examples/basic-examples/printer): The instructions below will walk you through the process of launching a simple printer workflow using the Fuzzball workflow catalog. The workflow catalog will… - [Fuzzfile Examples](https://docs.ciq.com/fuzzball/workflow-examples/fuzzfiles) - [Open Source Examples](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples): The following section provides example Fuzzball workflows using open source software tailored for specific applications such as: - [BLAST](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/blast): The Basic Local Alignment Search Tool (BLAST) uses a local alignment algorithm to compare protein or nucleotide queries to sequence databases and identify… - [Executing a BLAST Workflow Template](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/blast/blast-run): The instructions on this page will show you how to execute a BLAST query workflow using the workflow catalog with the Fuzzball web UI and CLI. - [Saving BLAST Results to AWS S3](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/blast/blast-save-results-S3): The pre-installed BLAST workflow template obtains query sequences with efetch from NCBI or curl from any https URL and saves results to a configurable path… - [Viewing BLAST Results](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/blast/blast-view-results): The run of the stock BLAST workflow template saves results to a persistent volume. You can access and post-process these results from other Fuzzball workflows… - [LAMMPS](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/lammps): LAMMPS is a popular molecular dynamics suite created by Sandia National Laboratories. LAMMPS simulates interactions between atoms and molecules, and is an… - [Executing a LAMMPS Workflow](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/lammps/lammps-run): This workflow template has a number of parameters including the following: - [Saving LAMMPS Results](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/lammps/lammps-save): This example LAMMPS CPU workflow uses StageoutScript to save results to a persistent volume. If you wanted to, for example, modify the workflow template to… - [Viewing LAMMPS Results](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/lammps/lammps-view): The run of the stock LAMMPS workflow template saves results to a persistent volume. You can access and post-process these results from other Fuzzball… - [OpenFOAM](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/openfoam): OpenFOAM is the free, open source Computational Fluid Dynamics (CFD) software developed primarily by OpenCFD Ltd since 2004. It has a large user base at… - [Executing an OpenFOAM Motorbike Simulation](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/openfoam/of-run): The instructions on this page will show you how to execute the OpenFOAM motorbike tutorial from the workflow catalog template with the Fuzzball web UI and… - [Viewing OpenFOAM Results](https://docs.ciq.com/fuzzball/workflow-examples/open-source-examples/openfoam/of-view): In the previous section, we showed how to save results to a persistent volume, and/or to S3. In the following sections we will discuss how to access and… Other documented versions: - [Fuzzball 4.2](https://docs.ciq.com/fuzzball/4.2): Documentation for version 4.2. - [Fuzzball 4.1](https://docs.ciq.com/fuzzball/4.1): Documentation for version 4.1. - [Fuzzball 4.0](https://docs.ciq.com/fuzzball/4.0): Documentation for version 4.0. - [Fuzzball 3.4](https://docs.ciq.com/fuzzball/3.4): Documentation for version 3.4. - [Fuzzball 3.3](https://docs.ciq.com/fuzzball/3.3): Documentation for version 3.3. - [Fuzzball 3.2](https://docs.ciq.com/fuzzball/3.2): Documentation for version 3.2. ## migrate2rlc Migrate Enterprise Linux or Amazon Linux 2 to Rocky Linux from CIQ - [Bash Script Guides](https://docs.ciq.com/migrate2rlc/bash-script): Distribution-specific migration guides using the migrate2rlc bash script - [Amazon Linux 2 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-al2-rlc): Migrate Amazon Linux 2 to Rocky Linux from CIQ using the migrate2rlc bash script - [AlmaLinux 8 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-alma8-rlc): Migrate AlmaLinux 8 to Rocky Linux from CIQ using the migrate2rlc bash script - [AlmaLinux 9 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-alma9-rlc): Migrate AlmaLinux 9 to Rocky Linux from CIQ using the migrate2rlc bash script - [CentOS Stream 8 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-cs8-rlc): Migrate CentOS Stream 8 to Rocky Linux from CIQ using the migrate2rlc bash script - [CentOS Stream 9 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-cs9-rlc): Migrate CentOS Stream 9 to Rocky Linux from CIQ using the migrate2rlc bash script - [Oracle Linux 8 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-ol8-rlc): Migrate Oracle Linux 8 to Rocky Linux from CIQ using the migrate2rlc bash script - [Oracle Linux 9 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-ol9-rlc): Migrate Oracle Linux 9 to Rocky Linux from CIQ using the migrate2rlc bash script - [RHEL 8 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-rhel8-rlc): Migrate Red Hat Enterprise Linux 8 to Rocky Linux from CIQ using the migrate2rlc bash script - [RHEL 9 to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-rhel9-rlc): Migrate Red Hat Enterprise Linux 9 to Rocky Linux from CIQ using the migrate2rlc bash script - [Rocky Linux 8 (Community) to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-rocky8-rlc): Migrate community Rocky Linux 8 to Rocky Linux from CIQ using the migrate2rlc bash script - [Rocky Linux 9 (Community) to Rocky Linux from CIQ](https://docs.ciq.com/migrate2rlc/bash-script/migrate2rlc-rocky9-rlc): Migrate community Rocky Linux 9 to Rocky Linux from CIQ using the migrate2rlc bash script - [Ansible/Ascender Playbook Guides](https://docs.ciq.com/migrate2rlc/playbook): Migration guides using Ansible playbooks with CIQ Ascender or standalone Ansible - [Standalone Ansible Playbook](https://docs.ciq.com/migrate2rlc/playbook/migrate2rlc-ansible-standalone): Run the migrate2rlc Ansible playbook directly without CIQ Ascender - [Amazon Linux 2 Migration via Ascender](https://docs.ciq.com/migrate2rlc/playbook/migrate2rlc-ascender-al2): Deploy the migrate2rlc Ansible playbook through CIQ Ascender for Amazon Linux 2 systems - [EL 8 Migration via Ascender](https://docs.ciq.com/migrate2rlc/playbook/migrate2rlc-ascender-el8): Deploy the migrate2rlc Ansible playbook through CIQ Ascender for Enterprise Linux 8 systems - [EL 9 Migration via Ascender](https://docs.ciq.com/migrate2rlc/playbook/migrate2rlc-ascender-el9): Deploy the migrate2rlc Ansible playbook through CIQ Ascender for Enterprise Linux 9 systems ## RLC Pro Production-ready enterprise Linux with commercial support and extended lifecycle - [FAQs](https://docs.ciq.com/rlc/faqs): Common questions about Rocky Linux from CIQ (RLC Pro and RLC+) - [FIPS 140-3 Compliance](https://docs.ciq.com/rlc/fips): FIPS 140-3 certification status, CIQ's compliance delivery model, terminology, and FAQ for RLC Pro - [FIPS Algorithm Validation (ACVP)](https://docs.ciq.com/rlc/fips/algorithm-validation): Per-module ACVP algorithm validation certificate numbers, from each module’s NIST Security Policy. - [FIPS Certification Status](https://docs.ciq.com/rlc/fips/certification-status): CMVP-validated and in-process cryptographic modules by RLC Pro version, plus validated entropy sources. - [Enabling FIPS](https://docs.ciq.com/rlc/fips/enabling): Enable FIPS mode on RLC Pro and install the validated FIPS packages (Compliant or Certified). - [FIPS Reference](https://docs.ciq.com/rlc/fips/reference): Module enhancements, open-source transparency, certification partner, ATO support, terminology, and FAQ. - [Getting Started with RLC](https://docs.ciq.com/rlc/getting-started): How to access and deploy Rocky Linux from CIQ through Portal and Depot CLI - [RLC Pro](https://docs.ciq.com/rlc): Enterprise Rocky Linux from CIQ with LTS, FIPS, GPU support, and commercial guarantees. - [Installation](https://docs.ciq.com/rlc/installation): Overview of RLC deployment methods, available images, and system requirements - [Bootc Images](https://docs.ciq.com/rlc/installation/bootc-images): Deploy immutable, transactional Rocky Linux from CIQ systems using OCI container technology - [GenericCloud (QCOW2) Deployment](https://docs.ciq.com/rlc/installation/kvm-qcow2): Deploying Rocky Linux from CIQ using GenericCloud QCOW2 virtual machine images - [Version Pinning & Long Term Support](https://docs.ciq.com/rlc/lts): LTS versions and version pinning for RLC Pro customers - [Migration Guide](https://docs.ciq.com/rlc/migration): Migrating to Rocky Linux from CIQ from Rocky Linux, RHEL, or legacy RLC - [Repository Architecture](https://docs.ciq.com/rlc/repositories): Understanding Rocky Linux from CIQ repository structure for RLC Pro and RLC+ Other documented versions: - [RLC Pro 8](https://docs.ciq.com/rlc/8): Documentation for version 8. ## RLC Pro AI AI-optimized Rocky Linux with the CIQ Linux Kernel and a pre-validated NVIDIA and PyTorch stack - [Admin Guides](https://docs.ciq.com/rlc-ai/admin-guides): Repository architecture and system management guides for RLC Pro AI administrators. - [Repository Architecture](https://docs.ciq.com/rlc-ai/admin-guides/repositories): Understanding the RLC Pro AI repository structure and where each part of the AI stack comes from. - [SELinux on RLC Pro AI](https://docs.ciq.com/rlc-ai/admin-guides/selinux): How SELinux is configured on RLC Pro AI and how to work with it for AI workloads and containers. - [Container Deployment](https://docs.ciq.com/rlc-ai/container-deployment): Running RLC Pro AI as OCI container images with Podman, Docker, and Apptainer. - [Apptainer](https://docs.ciq.com/rlc-ai/container-deployment/apptainer): Pulling the RLC Pro AI container image as a SIF file with Apptainer for HPC and shared environments. - [Docker](https://docs.ciq.com/rlc-ai/container-deployment/docker): Pulling and running the RLC Pro AI container image with Docker. - [Podman](https://docs.ciq.com/rlc-ai/container-deployment/podman): Pulling and running the RLC Pro AI container image with Podman. - [Getting Started with RLC Pro AI](https://docs.ciq.com/rlc-ai/getting-started): How to obtain RLC Pro AI images from the CIQ Portal and choose a deployment method. - [RLC Pro AI](https://docs.ciq.com/rlc-ai): Enterprise Linux engineered for AI workloads, pairing the CIQ Linux Kernel with a pre-validated NVIDIA and PyTorch stack that works at first boot. - [Installation](https://docs.ciq.com/rlc-ai/installation): Hardware requirements, installation methods, and post-installation steps for RLC Pro AI. - [QEMU/QCOW2 Installation Guide](https://docs.ciq.com/rlc-ai/installation/kvm-qemu-qcow2): Step-by-step guide for deploying RLC Pro AI on a KVM hypervisor using QCOW2 cloud images. - [Post-Installation Guide | Enrolling and Updating RLC Pro AI](https://docs.ciq.com/rlc-ai/installation/post-install-update): Step-by-step instructions for enrolling, enabling entitlements, and updating your RLC Pro AI system after installation. - [Hardware Requirements Matrix](https://docs.ciq.com/rlc-ai/installation/requirements): A guide to the minimum and recommended hardware requirements for RLC Pro AI. - [Release Notes](https://docs.ciq.com/rlc-ai/release-notes): Release notes for RLC Pro AI. - [RLC Pro AI 9.7-20260428 Release Notes](https://docs.ciq.com/rlc-ai/release-notes/rn-9.7-20260428): Release notes for RLC Pro AI - [Troubleshooting](https://docs.ciq.com/rlc-ai/troubleshooting): Common RLC Pro AI issues and how to diagnose them. - [User Guides](https://docs.ciq.com/rlc-ai/user-guides): Guides for working with the AI software stack on RLC Pro AI. - [AI Frameworks](https://docs.ciq.com/rlc-ai/user-guides/ai-frameworks): The pre-installed PyTorch stack on RLC Pro AI, how to verify it, and how to install additional frameworks. - [Running Ollama](https://docs.ciq.com/rlc-ai/user-guides/ollama): Installing and using Ollama for local LLM inference on RLC Pro AI. ## RLC Pro Hardened Security-hardened Rocky Linux with compliance frameworks and enhanced security features - [Admin Guides](https://docs.ciq.com/rlc-h/admin-guides): Guides for managing and configuring security features on RLC Pro Hardened. - [Control Tool Guide for RLC Pro Hardened](https://docs.ciq.com/rlc-h/admin-guides/control-tool-guide): Guide for using the control tool to manage security facilities on RLC Pro Hardened - [Linux Kernel Runtime Guard (LKRG) Guide for RLC Pro Hardened](https://docs.ciq.com/rlc-h/admin-guides/lkrg-guide): Comprehensive guide for configuring and managing LKRG on RLC Pro Hardened - [Lockdown Playbooks Guide](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide): Apply DISA STIG, CIS Benchmark, CUI/OSPP, and RLC Pro Hardened baselines to Rocky Linux 9 systems with the CIQ Lockdown Wrapper. - [Configuration](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/configuration): Profiles, environments, variable structure, and customization for the CIQ Lockdown Wrapper. - [Idempotency](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/idempotency): The lockdown playbooks are idempotent - safe to re-run, with zero changes reported on already-hardened systems. - [Compliance Scores](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/limitations): How to interpret OpenSCAP and GOSS compliance scores after running the lockdown playbooks. - [Quick Start](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/quickstart): Install the CIQ Lockdown Wrapper and harden a Rocky Linux 9 system in 5 steps. - [Troubleshooting](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/troubleshooting): Common issues when running the CIQ Lockdown Wrapper playbooks, and their solutions. - [Variable Reference](https://docs.ciq.com/rlc-h/admin-guides/lockdown-guide/variable-reference): Full reference of named configuration variables for the CIQ Lockdown Wrapper, by hardening profile. - [Hardened Malloc Guide for RLC Pro Hardened](https://docs.ciq.com/rlc-h/admin-guides/malloc-guide): Comprehensive guide for using hardened_malloc memory allocator on RLC Pro Hardened - [Cloud Deployment](https://docs.ciq.com/rlc-h/cloud-deployment): Deploy RLC Pro Hardened on AWS, Azure, and Google Cloud Platform. - [RLC Pro Hardened on AWS](https://docs.ciq.com/rlc-h/cloud-deployment/aws-deploy): Deploy RLC Pro Hardened on Amazon Web Services - [RLC Pro Hardened on Azure](https://docs.ciq.com/rlc-h/cloud-deployment/azure-deploy): Deploy RLC Pro Hardened on Microsoft Azure - [RLC Pro Hardened on Google Cloud Platform](https://docs.ciq.com/rlc-h/cloud-deployment/gcp-deploy): Deploy RLC Pro Hardened on Google Cloud Platform - [FAQs](https://docs.ciq.com/rlc-h/faqs): Common questions about RLC Pro Hardened - [Getting Started with RLC Pro Hardened](https://docs.ciq.com/rlc-h/getting-started): Complete guide to getting started with RLC Pro Hardened - [RLC Pro Hardened](https://docs.ciq.com/rlc-h): Security-hardened Rocky Linux with compliance frameworks and enhanced security features for enterprise environments. - [Installation](https://docs.ciq.com/rlc-h/installation): Hardware requirements, installation methods, and post-installation steps for RLC Pro Hardened. - [Baremetal ISO Installation Guide](https://docs.ciq.com/rlc-h/installation/baremetal-iso): Comprehensive guide for installing and configuring RLC Pro Hardened on bare metal hardware using ISO installation media. - [QEMU/QCOW2 Installation Guide](https://docs.ciq.com/rlc-h/installation/kvm-qemu-qcow2): Comprehensive guide for deploying and managing RLC Pro Hardened using QEMU/QCOW2 - [Post-Installation Guide | Updating RLC Pro Hardened](https://docs.ciq.com/rlc-h/installation/post-install-update): Step-by-step instructions for enrolling, enabling entitlements, and updating your RLC Pro Hardened system after installation. - [Hardware Requirements Matrix](https://docs.ciq.com/rlc-h/installation/requirements): A guide to the minimum and recommended hardware requirements. - [Release Notes](https://docs.ciq.com/rlc-h/release-notes): Release notes for RLC Pro Hardened. - [RLC Pro Hardened 9.6-20251028 Release Notes](https://docs.ciq.com/rlc-h/release-notes/rn-9.6-20251028): Release notes for RLC Pro Hardened - [RLC Pro Hardened 9.7-20260131 Release Notes](https://docs.ciq.com/rlc-h/release-notes/rn-9.7-20260131): Release notes for RLC Pro Hardened - [Security and Compliance](https://docs.ciq.com/rlc-h/security): FIPS 140-3 certification, security profiles, compliance delivery, and verification for RLC Pro Hardened. - [FIPS](https://docs.ciq.com/rlc-h/security/fips): RLC Pro Hardened inherits the FIPS 140-3 validated cryptographic modules from RLC Pro. The full compliance model, certification status, terminology, and FAQ… - [Enabling FIPS Mode on RLC Pro Hardened](https://docs.ciq.com/rlc-h/security/fips/enablement): This guide describes how to enable FIPS (Federal Information Processing Standards) mode on RLC Pro Hardened. FIPS mode configures the system to use only FIPS… - [Switching FIPS Modes (Compliant and Certified)](https://docs.ciq.com/rlc-h/security/fips/mode-switching): How RLC Pro Hardened delivers FIPS via the rlc-fips and rlc-fips-certified meta packages, and how to switch between compliant and certified modes. - [Hardened Package Enforcement (rlc-h)](https://docs.ciq.com/rlc-h/security/meta-package-enforcement): How the rlc-h meta package enforces the security-hardened builds of glibc and openssh on RLC Pro Hardened. - [Profiles](https://docs.ciq.com/rlc-h/security/profiles): How RLC Pro Hardened delivers DISA STIG, CIS, and other compliance frameworks as OpenSCAP profiles, and which profiles are production-ready. - [CIS Benchmarks Profile](https://docs.ciq.com/rlc-h/security/profiles/cis-benchmarks): Apply and verify the CIS Level 2 (Server) benchmark on RLC Pro Hardened using the bundled OpenSCAP profile. - [DISA STIG Profile](https://docs.ciq.com/rlc-h/security/profiles/disa-stig): Scan, remediate, and verify RLC Pro Hardened against the DISA STIG using the bundled OpenSCAP profile. - [Verification Scripts](https://docs.ciq.com/rlc-h/security/scripts): This section provides scripts to help administrators verify the security and compliance status of their RLC Pro Hardened deployments. - [Troubleshooting](https://docs.ciq.com/rlc-h/troubleshooting): Common issues and solutions for RLC Pro Hardened ## CIQ SIG/Cloud Next CIQ SIG/Cloud Next - [CIQ SIG/Cloud Next](https://docs.ciq.com/scn): Install instructions for enabling CIQ SIG/Cloud Next repositories on RLC - [SIG/Cloud-Next Release Notes](https://docs.ciq.com/scn/release-notes): Release notes and updates for CIQ SIG/Cloud-Next - [aarch64 (ARM) 64k Page Size Kernel Support — December 2025](https://docs.ciq.com/scn/release-notes/arm-64k-kernel): 64k page size kernel support for ARM architecture in SIG/Cloud-Next - [DOCA OFED Upgrade Advisory — Rocky Linux 9.7 — December 2025](https://docs.ciq.com/scn/release-notes/doca-ofed-upgrade-advisory): Important upgrade advisory for DOCA OFED on Rocky Linux 9.7 - [SIG/Cloud-Next Kernel Dist-Tag Update — October-November 2025](https://docs.ciq.com/scn/release-notes/kernel-dist-tag-update): Kernel dist-tag consolidation for SIG/Cloud-Next across Rocky Linux 8, 9, and 10 ## Warewulf Pro Enterprise cluster management and provisioning solution with commercial support - [Admin guides](https://docs.ciq.com/warewulf-pro/admin-guides): Managing the components Warewulf Pro adds - web interface, Pro overlays, Pro node images, and bundled Apptainer. - [Apptainer](https://docs.ciq.com/warewulf-pro/admin-guides/apptainer): CIQ-packaged Apptainer for HPC containerization, distributed with Warewulf Pro. - [Pro node images](https://docs.ciq.com/warewulf-pro/admin-guides/pro-node-images): Pre-built compute node images for OpenHPC, Slurm, OpenPBS, and Fuzzball Substrate. Multi-arch. - [Pro overlays](https://docs.ciq.com/warewulf-pro/admin-guides/pro-overlays): Configuration overlays included with Warewulf Pro - apptainer, chrony, slurm, openpbs, fuzzball-substrate. - [Web interface](https://docs.ciq.com/warewulf-pro/admin-guides/web-interface): The Warewulf Pro web interface - Cockpit-based UI for cluster management. - [Installation](https://docs.ciq.com/warewulf-pro/admin-guides/web-interface/installation): Install and configure the Warewulf Pro web interface (Cockpit module and REST API). - [Using the web interface](https://docs.ciq.com/warewulf-pro/admin-guides/web-interface/usage): A tour of the Warewulf Pro web interface - managing nodes, profiles, images, overlays, and tags from Cockpit. - [FAQs](https://docs.ciq.com/warewulf-pro/faqs): Common questions about Warewulf Pro. - [Getting started with Warewulf Pro](https://docs.ciq.com/warewulf-pro/getting-started): Enable the Warewulf Pro repository through CIQ Depot and install the core components. - [Warewulf Pro](https://docs.ciq.com/warewulf-pro): Enterprise cluster provisioning with a web interface, turn-key node images, configuration overlays, bundled Apptainer, and CIQ support. - [Installation](https://docs.ciq.com/warewulf-pro/installation): Install Warewulf Pro from CIQ Depot, with options for connected and air-gapped environments. - [Air-gapped install](https://docs.ciq.com/warewulf-pro/installation/air-gapped): Mirror the Warewulf Pro repository locally for environments without internet access. - [Standard install via Depot](https://docs.ciq.com/warewulf-pro/installation/depot-install): Install Warewulf Pro on a server with internet access to CIQ Depot. - [Release notes](https://docs.ciq.com/warewulf-pro/release-notes): Release notes for all Warewulf Pro versions. - [Warewulf Pro 1.0.0 (Aug 2025)](https://docs.ciq.com/warewulf-pro/release-notes/rn-1.0.0): First Warewulf Pro release. warewulf-dracut, OpenPBS overlay, repo refactor. - [Warewulf Pro 1.1.0 (Sep 2025)](https://docs.ciq.com/warewulf-pro/release-notes/rn-1.1.0): Release notes introduced, separate web-interface repository, RLC images split into a dedicated product. - [Warewulf Pro 1.1.1 (Dec 2025)](https://docs.ciq.com/warewulf-pro/release-notes/rn-1.1.1): aarch64 server packages, Apptainer v1.4.5, packaging fixes. - [Warewulf Pro 1.2.0 (Jan 2026)](https://docs.ciq.com/warewulf-pro/release-notes/rn-1.2.0): Multi-arch node images, Warewulf v4.6.5, Apptainer build, Cockpit improvements. ## Optional - [CIQ Website](https://ciq.com/): Product overviews, solutions, pricing, and company information. - [CIQ Knowledge Base](https://kb.ciq.com/): Technical troubleshooting and product knowledge articles. - [CIQ Customer Portal](https://portal.ciq.com/): Customer login for software access and support. - [CIQ on GitHub](https://github.com/ctrliq): CIQ open-source repositories.