cloudstack/packaging
Abhishek Kumar a1959f2dc2
backup: veeam kvm integration (#12991)
This PR introduces the initial implementation of Veeam integration support for KVM in CloudStack by adding a UHAPI-compatible server and image server components.

Veeam Backup & Replication interacts with virtualization platforms using its Universal Hypervisor API (UHAPI). To enable backup and restore workflows for CloudStack-managed KVM environments, this change introduces a UHAPI server that exposes CloudStack resources through a UHAPI-compatible interface.

In addition to the control plane APIs, an image server component is introduced to handle the data transfer operations required during backup and restore workflows.


The integration consists of two main components:

1. UHAPI Server (Control Plane) named CloudStack Veeam Control Service

A lightweight UHAPI server runs inside the CloudStack management server and exposes endpoints under:

/ovirt-engine
    - /api - For APIs
    - /sso - For authentication
    - /services/pki-resource - For certificates

This server provides inventory discovery APIs required by Veeam and translates CloudStack resources into the structures expected by UHAPI.

The server:

- exposes infrastructure inventory
- handles authentication and session tokens
- maps CloudStack resources to UHAPI-compatible representations


2. Image Server (Data Plane) named CloudStack Image Service

A separate image server component is introduced to handle backup and restore data transfer operations.

This component:

- serves disk image data during backup
- receives image data during restore operations
- exposes endpoints used by Veeam worker components
- integrates with CloudStack storage to read and write VM disk data

The separation between both these components server ensures that:

- metadata APIs and control operations remain lightweight
- bulk image transfer operations are handled independently

Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Co-authored-by: Abhisar Sinha <63767682+abh1sar@users.noreply.github.com>
Co-authored-by: abh1sar <abhisar.sinha@gmail.com>
Co-authored-by: Wei Zhou <weizhou@apache.org>
2026-06-08 08:47:00 +02:00
..
debian Enable UEFI on KVM hosts (by default), and configure with some default settings (#11740) 2025-11-07 14:54:02 +01:00
el8 backup: veeam kvm integration (#12991) 2026-06-08 08:47:00 +02:00
suse15 Update suse15 packaging spec, use qemu-ovmf-x86_64 package instead of edk2-ovmf for agent (#13133) 2026-05-11 20:15:16 +05:30
systemd Merge release branch 4.20 to 4.22 2026-05-22 08:31:35 -03:00
README.md pre-commit auto add license for all Markdown files (#11870) 2025-10-24 16:04:22 +05:30
build-deb.sh packaging: new timestamp format and add output dir option (#4471) 2021-02-19 14:26:13 +05:30
centos8 packaging: support both mysql and mariadb on EL8/EL9 (#9941) 2025-01-30 16:08:39 +01:00
el9 Build: drop EL7 support, support JRE17 for packages and sonar check (#8609) 2024-08-27 16:09:10 +05:30
el10 Add support EL10 (#11546) 2025-09-25 15:37:45 +05:30
package.sh Build: drop EL7 support, support JRE17 for packages and sonar check (#8609) 2024-08-27 16:09:10 +05:30

README.md

CloudStack RPM and DEB packaging

This directory contains all the required scripts and tools needed to build RPM and DEB packages for Apache CloudStack.

These scripts are also used by the CloudStack team to build packages for the official release of CloudStack.

Requirements

The RPM and DEB packages have dependencies on versions of specific libraries. Due to these dependencies the following distributions and their versions are supported by the packages.

  • CentOS / RHEL: 8 and 9
  • Ubuntu: 20.04, 22.04, 24.04
  • Debian 12 (Bookworm, untested!)

Building

Using the scripts in the packaging directory the RPM and DEB packages can be build.

DEB

If you simply want to build packages go to the root directory of your CloudStack source code and run:

dpkg-buildpackage

This will build packages for the current distribution version you are running. If you run this on a Ubuntu 16.04 system the packages will be tailored for Ubuntu 16.04 and will not install on Ubuntu 14.04.

Building cross-distribution

If you want to build packages for a different distribution run the build-deb.sh script. This will build packages with the current distribution as a suffix to the package names. E.g. cloudstack-agent_4.9.0~xenial_all.deb

Using a Docker image you can build packages for a distribution you are not running.

The following commands assume that the CloudStack source is present in /tmp/cloudstack on the system you are running these commands on.

docker run -ti -v /tmp:/src ubuntu:16.04 /bin/bash -c "apt-get update && apt-get install -y dpkg-dev python debhelper openjdk-8-jdk genisoimage python-mysql.connector maven lsb-release devscripts && /src/cloudstack/packaging/build-deb.sh"

docker run -ti -v /tmp:/src ubuntu:14.04 /bin/bash -c "apt-get update && apt-get install -y dpkg-dev python debhelper openjdk-7-jdk genisoimage python-mysql.connector maven lsb-release devscripts && /src/cloudstack/packaging/build-deb.sh"

docker run -ti -v /tmp:/src ubuntu:22.04 /bin/bash -c "apt-get update && apt-get install -y software-properties-common &&apt-add-repository universe --yes && apt-get update && apt-get install -y dpkg-dev debhelper lsb-release devscripts openjdk-11-jdk libws-commons-util-java genisoimage libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven python3 python3-mysql.connector python3-setuptools python-setuptools python3-openssl python3-dev libffi-dev build-essential libssl-dev libffi-dev fakeroot python-is-python3 && curl -sL https://deb.nodesource.com/setup_14.x | bash - && apt-get install -y nodejs && /src/cloudstack/packaging/build-deb.sh"

The commands above will generate Ubuntu 14.04, 16.04, and 22.04 packages which you will find in /tmp on your system after the build succeeds.

RPM

The package.sh script can be used to build RPM packages for CloudStack. In the packaging script you can run the following command:

./package.sh --pack oss --distribution el8