Apache CloudStack community package repository

Ready-to-use apt, dnf and zypper packages for Apache CloudStack, so you can install the management server and KVM agents with your normal package manager.

Pick a version Set up the repository Upgrading Verifying signatures Nightlies and release candidates Getting help

Pick a version

Look up the version you want on the Apache CloudStack downloads page. It names the current LTS release, which is what most production deployments should run, and the current Regular release, which carries the newest features but is only supported until the next release ships.

You need the branch, not the full version — the two leading digits, such as 4.19 or 4.20. Every command below starts with a CSVERSION line: put your branch there. The repository always serves the newest patch release on that branch, so a maintenance release reaches you through a normal apt upgrade or dnf upgrade without any repository changes.

Not every branch is built for every distribution. If a repository refresh reports that the component or URL does not exist, use the directory listing at the top of this page to see what is actually published for your platform.

Set up the repository

Pick your distribution, set CSVERSION, and paste. Each block is safe to re-run — it overwrites the repository file rather than appending to it.

CSVERSION=          # e.g. 4.19 — see the downloads page
DISTRO=$(. /etc/os-release && echo "$ID")
CODENAME=$(. /etc/os-release && echo "$VERSION_CODENAME")

sudo apt install -y curl ca-certificates
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.cloudstack.org/release.asc \
  -o /etc/apt/keyrings/cloudstack.asc

sudo tee /etc/apt/sources.list.d/cloudstack.sources >/dev/null <<EOF
Types: deb
URIs: https://download.cloudstack.org/${DISTRO}
Suites: ${CODENAME}
Components: ${CSVERSION}
Architectures: amd64 arm64
Signed-By: /etc/apt/keyrings/cloudstack.asc
EOF

sudo apt update

# management server (plus the web UI and usage server)
sudo apt install cloudstack-management cloudstack-ui cloudstack-usage

# KVM hypervisor host
sudo apt install cloudstack-agent

CSVERSION=          # e.g. 4.19 — see the downloads page

sudo rpm --import https://download.cloudstack.org/RPM-GPG-KEY

sudo tee /etc/yum.repos.d/cloudstack.repo >/dev/null <<EOF
[cloudstack]
name=Apache CloudStack (community builds)
baseurl=https://download.cloudstack.org/el/\$releasever/${CSVERSION}
enabled=1
gpgcheck=1
gpgkey=https://download.cloudstack.org/RPM-GPG-KEY
EOF

sudo dnf makecache

# management server (plus the web UI and usage server)
sudo dnf install cloudstack-management cloudstack-ui cloudstack-usage

# KVM hypervisor host
sudo dnf install cloudstack-agent

CSVERSION=          # e.g. 4.19 — see the downloads page
OSMAJOR=$(. /etc/os-release && echo "${VERSION_ID%%.*}")

sudo rpm --import https://download.cloudstack.org/RPM-GPG-KEY
sudo zypper removerepo cloudstack 2>/dev/null
sudo zypper addrepo --refresh --gpgcheck \
  https://download.cloudstack.org/suse/${OSMAJOR}/${CSVERSION} cloudstack
sudo zypper refresh

# management server (plus the web UI and usage server)
sudo zypper install cloudstack-management cloudstack-ui cloudstack-usage

# KVM hypervisor host
sudo zypper install cloudstack-agent

Installing the packages is only part of a working cloud — you still need MySQL, NFS or another secondary storage, and the system VM template. Follow the Quick Installation Guide for the whole sequence.

Upgrading to a newer CloudStack version

Point the repository at the new branch, then upgrade. Read the release notes for your target version first: CloudStack upgrades involve database changes and a specific order of operations across management servers and hosts.

CSVERSION=          # the branch you are moving to

# Debian / Ubuntu — swap the component, then upgrade
sudo sed -i "s/^Components: .*/Components: ${CSVERSION}/" \
  /etc/apt/sources.list.d/cloudstack.sources
sudo apt update && sudo apt upgrade

# RHEL family — swap the branch in the URL, then upgrade
sudo sed -i "s|/[0-9]\+\.[0-9]\+$|/${CSVERSION}|" \
  /etc/yum.repos.d/cloudstack.repo
sudo dnf clean all && sudo dnf upgrade

Upgrade instructions per version are in the upgrade documentation.

Verifying signatures

The Debian and Ubuntu repository metadata and the RPM packages are both signed. The setup commands above enable signature checking; these are the fingerprints they trust.

deb-release.asc is the same key as release.asc under an older name. Do not use apt-key add — it has been removed from current Debian and Ubuntu releases. Use the Signed-By keyring shown above instead.

Nightlies and release candidates

/testing/ holds builds that are not releases:

• Release candidate directories — the exact artefacts put up for a community vote. Useful if you are testing a candidate or verifying a vote.
• nightly/latest/ — daily builds from the development and LTS branches.

Nightlies exist so the community can try changes early. Upgrade paths between them are not maintained, so treat them as fresh installs in a test environment and never as a rolling release.

Getting help

• Documentation — installation, administration and API guides for every release.
• users@ mailing list — the main place to ask questions.
• Community page — Slack, user groups and events.
• GitHub issues — bugs in CloudStack itself. Problems with this repository, such as a missing package or a broken URL, are best raised on the mailing list.

Source code

Source packages are not published here. Official signed source releases are on the Apache CloudStack downloads page, and the git history is at github.com/apache/cloudstack.