docs(README): Define the new location of ProxLB at credativ

doc(README): Define new location of the ProxLB project at credativ
Updated README to reflect the new location of the ProxLB project and removed outdated sections.
2026-04-05 20:31:57 +02:00 · 2026-01-15 13:14:42 +01:00 · 2026-01-15 13:13:06 +01:00 · 2026-01-13 10:32:04 +01:00 · 2026-01-13 08:24:50 +01:00 · 2026-01-12 07:15:48 +01:00
34 changed files with 601 additions and 588 deletions
--- a/.changelogs/1.1.11/275_add_overprovisioning_safety_guard.yml
+++ b/.changelogs/1.1.11/275_add_overprovisioning_safety_guard.yml
@@ -0,0 +1,2 @@
+fixed:
+  - Fixed missing overprovisioning safety guard to avoid node overprovisioning (@gyptazy). [#275]
--- a/.changelogs/1.1.11/335_fix_affinity_matrix_prevalidation.yml
+++ b/.changelogs/1.1.11/335_fix_affinity_matrix_prevalidation.yml
@@ -0,0 +1,2 @@
+fixed:
+  - Fixed affinity matrix pre-validation by inverting validations (@Thalagyrt). [#335]
--- a/.changelogs/1.1.11/373_add_node_resource_reservation_support.yml
+++ b/.changelogs/1.1.11/373_add_node_resource_reservation_support.yml
@@ -0,0 +1,2 @@
+added:
+  - Add resource reservation support for PVE nodes (@Chipmonk2). [#373]
--- a/.changelogs/1.1.11/378_change_and_improve_balancing_decisions.yml
+++ b/.changelogs/1.1.11/378_change_and_improve_balancing_decisions.yml
@@ -0,0 +1,3 @@
+changed:
+  - Changed balancing and sorting behaviour (@gyptazy). [#378]
+  - Balancing objects will be ordered by: count of objects in affinity-rules, followed by memory size 
--- a/.changelogs/1.1.11/387_select_balancing_workloads_by_size.yml
+++ b/.changelogs/1.1.11/387_select_balancing_workloads_by_size.yml
@@ -0,0 +1,2 @@
+added:
+  - Add possibility to sort and select balancing workloads by smaller/larger guest objects (@gyptazy). [#387]
--- a/.changelogs/1.1.11/391_add_native_proxmox_ha_rules_support.yml
+++ b/.changelogs/1.1.11/391_add_native_proxmox_ha_rules_support.yml
@@ -0,0 +1,3 @@
+added:
+  - Add support for Proxmox's native HA (affinity/anti-affinity) rules (@gyptazy). [#391]
+  - Add support for Proxmox's native HA (node-affinity) rules for pinning guests to nodes (@gyptazy). [#391]
--- a/.changelogs/1.1.11/395_fix_pool_based_node_pinning.yml
+++ b/.changelogs/1.1.11/395_fix_pool_based_node_pinning.yml
@@ -0,0 +1,2 @@
+fixed:
+  - Fixed pool based node pinning (@gyptazy). [#395]
--- a/.changelogs/1.1.11/402_add_ha_job_validation.yml
+++ b/.changelogs/1.1.11/402_add_ha_job_validation.yml
@@ -0,0 +1,2 @@
+added:
+  - Add HA job validation for migration jobs (@gytazy). [#402]
--- a/.changelogs/1.1.11/406_add_stricness_for_node_pinning_of_pools.yml
+++ b/.changelogs/1.1.11/406_add_stricness_for_node_pinning_of_pools.yml
@@ -0,0 +1,2 @@
+added:
+  - Add support for configuring node-pinning strictness (default: true) within pools (@gyptazy). [#406]
--- a/.changelogs/1.1.11/408_fix_moving_ignored_guests.yml
+++ b/.changelogs/1.1.11/408_fix_moving_ignored_guests.yml
@@ -0,0 +1,2 @@
+fixed:
+  - Fixed that ignored VMs/CTs got moved to another node when being ignored (@gyptazy). [#408]
--- a/.changelogs/1.1.11/414_add_pinning_enforcement.yml
+++ b/.changelogs/1.1.11/414_add_pinning_enforcement.yml
@@ -0,0 +1,2 @@
+added:
+  - Add new option to enforce node/guest pinning even when cluster is balanced from a resource perspective (@gyptazy). [#414]
--- a/.changelogs/1.1.11/release_meta.yml
+++ b/.changelogs/1.1.11/release_meta.yml
@@ -0,0 +1 @@
+date: 2026-01-12
--- a/.changelogs/1.1.12/420_fix_psi_based_balancing_key_error.yml
+++ b/.changelogs/1.1.12/420_fix_psi_based_balancing_key_error.yml
@@ -0,0 +1,2 @@
+fixed:
+  - Fix PSI based balancing which resulted in a Python KeyError (@gyptazy). [#420]
--- a/.changelogs/1.1.12/release_meta.yml
+++ b/.changelogs/1.1.12/release_meta.yml
@@ -0,0 +1 @@
+date: TBD
--- a/.github/workflows/20-pipeline-build-deb-package.yml
+++ b/.github/workflows/20-pipeline-build-deb-package.yml
@@ -40,6 +40,19 @@ jobs:
            # Install dependencies
            apt-get update && \
            apt-get install -y python3 python3-setuptools debhelper dh-python python3-pip python3-stdeb python3-proxmoxer python3-requests python3-urllib3 devscripts python3-all && \
+
+            # Get base version from source code
+            BASE_VERSION=\$(grep __version__ proxlb/utils/version.py | awk '{print \$3}' | tr -d '\"')
+            echo \"Base version: \$BASE_VERSION\"
+
+            # Build full version with timestamp
+            FULL_VERSION=\"\${BASE_VERSION}+$(date +%Y%m%d%H%M)\"
+            echo \"Full version: \$FULL_VERSION\"
+
+            # Update debian/changelog with new version
+            dch --force-bad-version -v \"\$FULL_VERSION\" \
+                \"Automated GitHub Actions build on $(date -u +'%Y-%m-%d %H:%M UTC').\" && \
+
            # Build package using stdeb / setuptools
            # python3 setup.py --command-packages=stdeb.command bdist_deb && \
            # Build native package
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,30 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+## [1.1.11] - 2026-01-12
+
+### Added
+
+- Add support for Proxmoxs native HA (affinity/anti-affinity) rules [beta] (@gyptazy). [#391]
+- Add support for Proxmox native HA (node-affinity) rules for pinning guests to nodes [beta] (@gyptazy). [#391]
+- Add resource reservation support for PVE nodes (@Chipmonk2). [#373]
+- Add possibility to sort and select balancing workloads by smaller/larger guest objects (@gyptazy). [#387]
+- Add HA job validation for migration jobs to fetch child jobs (@gytazy). [#402]
+- Add support for configuring node-pinning strictness (default: true) within pools to allow strict/prefer modes (@gyptazy). [#406]
+- Add new option to enforce node/guest pinning even when cluster is balanced from a resource perspective (@gyptazy). [#414]
+
+### Fixed
+
+- Fix missing overprovisioning safety guard to avoid node overprovisioning (@gyptazy). [#275]
+- Fix affinity matrix pre-validation by inverting validations (@Thalagyrt). [#335]
+- Fix pool based node pinning which expects a list (@gyptazy). [#395]
+- Fix that ignored VMs/CTs got moved to another node when being ignored (@gyptazy). [#408]
+
+### Changed
+
+- Change balancing and sorting behaviour (@gyptazy). [#378]
+- Balancing objects will be ordered by count of objects in affinity-rules, followed by memory size (@gyptazy). [#378]
+
 ## [1.1.10] - 2025-11-25

 ### Added
--- a/README.md
+++ b/README.md
@@ -1,549 +1,7 @@
-# ProxLB - (Re)Balance VM Workloads in Proxmox Clusters
-<img align="left" src="https://cdn.gyptazy.com/img/ProxLB.jpg"/>
-<br>
+# ProxLB Moved

-<p float="center"><img src="https://img.shields.io/github/license/gyptazy/ProxLB"/><img src="https://img.shields.io/github/contributors/gyptazy/ProxLB"/><img src="https://img.shields.io/github/last-commit/gyptazy/ProxLB/main"/><img src="https://img.shields.io/github/issues-raw/gyptazy/ProxLB"/><img src="https://img.shields.io/github/issues-pr/gyptazy/ProxLB"/></p>
+You can find the new location of the `ProxLB` project at:
+[github.com/credativ/ProxLB](https://github.com/credativ/ProxLB)

-## Table of Contents
-1. [Introduction](#introduction)
-2. [Features](#features)
-3. [How does it work?](#how-does-it-work)
-4. [Documentation](#documentation)
-5. [Installation](#installation)
-   1. [Requirements / Dependencies](#requirements--dependencies)
-   2. [Debian Package](#debian-package)
-   4. [Container / Docker](#container--docker)
-   5. [Source](#source)
-6. [Usage / Configuration](#usage--configuration)
-   1. [GUI Integration](#gui-integration)
-   2. [Proxmox HA Integration](#proxmox-ha-integration)
-   3. [Options](#options)
-7. [Affinity & Anti-Affinity Rules](#affinity--anti-affinity-rules)
-   1. [Affinity Rules](#affinity-rules)
-   2. [Anti-Affinity Rules](#anti-affinity-rules)
-   3. [Ignore VMs](#ignore-vms)
-   4. [Pin VMs to Hypervisor Nodes](#pin-vms-to-hypervisor-nodes)
-8. [Maintenance](#maintenance)
-9. [Misc](#misc)
-   1. [Bugs](#bugs)
-   2. [Contributing](#contributing)
-   3. [Support](#support)
-   4. [Enterprise-Support](#enterprise-support)
-10. [Author(s)](#authors)
-
-
-## Introduction
-ProxLB is an advanced load balancing solution specifically designed for Proxmox clusters, addressing the absence of an intelligent and more advanced resource scheduler. As a third-party solution, ProxLB enhances the management and efficiency of Proxmox clusters by intelligently distributing workloads across available nodes. Workloads can be balanced by different times like the guest's memory, CPU or disk usage or their assignment to avoid overprovisioning and ensuring resources.
-
-One of the key advantages of ProxLB is that it is fully open-source and free, making it accessible for anyone to use, modify, and contribute to. This ensures transparency and fosters community-driven improvements. ProxLB supports filtering and ignoring specific nodes and guests through configuration files and API calls, providing administrators with the flexibility to tailor the load balancing behavior to their specific needs.
-
-A standout feature of ProxLB is its maintenance mode. When enabled, all guest workloads are automatically moved to other nodes within the cluster, ensuring that a node can be safely updated, rebooted, or undergo hardware maintenance without disrupting the overall cluster operation. Additionally, ProxLB supports both affinity and anti-affinity rules, allowing operators to group multiple guests to run together on the same node or ensure that certain guests do not run on the same node, depending on the cluster's node count. This feature is crucial for optimizing performance and maintaining high availability.
-
-ProxLB can also return the best next node for guest placement, which can be integrated into CI/CD pipelines using tools like Ansible or Terraform. This capability streamlines the deployment process and ensures efficient resource utilization. Furthermore, ProxLB leverages the Proxmox API, including the entire ACL (Access Control List) system, for secure and efficient operation. Unlike some solutions, it does not require SSH access, enhancing security and simplifying configuration.
-
-Overall, ProxLB significantly enhances resource management by intelligently distributing workloads, reducing downtime through its maintenance mode, and providing improved flexibility with affinity and anti-affinity rules. Its seamless integration with CI/CD tools and reliance on the Proxmox API make it a robust and secure solution for optimizing Proxmox cluster performance.
-
-### Video of Migration
-<img src="https://cdn.gyptazy.com/img/proxlb-rebalancing-demo.gif"/>
-
-## Features
-ProxLB's key features are by enabling automatic rebalancing of VMs and CTs across a Proxmox cluster based on memory, CPU, and local disk usage while identifying optimal nodes for automation. It supports maintenance mode, affinity rules, and seamless Proxmox API integration with ACL support, offering flexible usage as a one-time operation, a daemon, or through the Proxmox Web GUI.
-
-**Features**
-* Rebalance VMs/CTs in the cluster by:
-  * Memory
-  * Disk (only local storage)
-  * CPU
-* Rebalance by different modes:
-  * Used resources
-  * Assigned resources
-  * PSI (Pressure) of resources
-* Get best nodes for further automation
-* Supported Guest Types
-  * VMs
-  * CTs
-* Maintenance Mode
-  * Set node(s) into maintenance
-  * Move all workloads to different nodes
-* Affinity / Anti-Affinity Rules
-* Fully based on Proxmox API
-  * Fully integrated into the Proxmox ACL
-  * No SSH required
-* Usage
-  * One-Time
-  * Daemon
-  * Proxmox Web GUI Integration
-
-## How does it work?
-ProxLB is a load-balancing system designed to optimize the distribution of virtual machines (VMs) and containers (CTs) across a cluster. It works by first gathering resource usage metrics from all nodes in the cluster through the Proxmox API. This includes detailed resource metrics for each VM and CT on every node. ProxLB then evaluates the difference between the maximum and minimum resource usage of the nodes, referred to as "Balanciness." If this difference exceeds a predefined threshold (which is configurable), the system initiates the rebalancing process.
-
-Before starting any migrations, ProxLB validates that rebalancing actions are necessary and beneficial. Depending on the selected balancing mode — such as CPU, memory, or disk — it creates a balancing matrix. This matrix sorts the VMs by their maximum used or assigned resources, identifying the VM with the highest usage. ProxLB then places this VM on the node with the most free resources in the selected balancing type. This process runs recursively until the operator-defined Balanciness is achieved. Balancing can be defined for the used or max. assigned resources of VMs/CTs.
-
-## Documentation
-This `README.md` doesn't contain all information and only highlights the most important facts. Extended information, such like API permissions, creating dedicated user, best-practices in running ProxLB and much more can be found in the [docs/](https://github.com/gyptazy/ProxLB/tree/main/docs) directory. Please consult the documentation before creating issues.
-
-## Installation
-
-### Requirements / Dependencies
-* Proxmox
-    * Proxmox 7.x
-    * Proxmox 8.x
-    * Proxmox 9.x
-* Python3.x
-* proxmoxer
-* requests
-* urllib3
-* pyyaml
-
-The dependencies can simply be installed with `pip` by running the following command:
-```
-pip install -r requirements.txt
-```
-
-*Note: Distribution packages, such like the provided `.deb` package will automatically resolve and install all required dependencies by using already packaged version from the distribution's repository. By using the Docker (container) image or Debian packages, you do not need to take any care of the requirements listed here.*
-
-### Debian Package
-ProxLB is a powerful and flexible load balancer designed to work across various architectures, including `amd64`, `arm64`, `rv64` and many other ones that support Python. It runs independently of the underlying hardware, making it a versatile choice for different environments. This chapter covers the step-by-step process to install ProxLB on Debian-based systems, including Debian clones like Ubuntu.
-
-#### Quick-Start
-You can simply use this snippet to install the repository and to install ProxLB on your system.
-
-```bash
-echo "deb https://repo.gyptazy.com/stable /" > /etc/apt/sources.list.d/proxlb.list
-wget -O /etc/apt/trusted.gpg.d/proxlb.asc https://repo.gyptazy.com/repository.gpg
-apt-get update && apt-get -y install proxlb
-cp /etc/proxlb/proxlb_example.yaml /etc/proxlb/proxlb.yaml
-# Adjust the config to your needs
-vi /etc/proxlb/proxlb.yaml
-systemctl start proxlb
-```
-
-Afterwards, ProxLB is running in the background and balances your cluster by your defined balancing method (default: memory).
-
-#### Details
-ProxLB provides two different repositories:
-* https://repo.gyptazy.com/stable (only stable release)
-* https://repo.gyptazy.com/testing (bleeding edge - not recommended)
-
-The repository is signed and the GPG key can be found at:
-* https://repo.gyptazy.com/repository.gpg
-
-You can also simply import it by running:
-
-```
-# KeyID:  17169F23F9F71A14AD49EDADDB51D3EB01824F4C
-# UID:    gyptazy Solutions Repository <contact@gyptazy.com>
-# SHA256: 52c267e6f4ec799d40cdbdb29fa518533ac7942dab557fa4c217a76f90d6b0f3  repository.gpg
-
-wget -O /etc/apt/trusted.gpg.d/proxlb.asc https://repo.gyptazy.com/repository.gpg
-```
-
-*Note: The defined repositories `repo.gyptazy.com` and `repo.proxlb.de` are the same!*
-
-#### Debian Packages (.deb files)
-If you do not want to use the repository you can also find the debian packages as a .deb file on gyptazy's CDN at:
-* https://cdn.gyptazy.com/debian/proxlb/
-
-Afterwards, you can simply install the package by running:
-```bash
-dpkg -i proxlb_*.deb
-cp /etc/proxlb/proxlb_example.yaml /etc/proxlb/proxlb.yaml
-# Adjust the config to your needs
-vi /etc/proxlb/proxlb.yaml
-systemctl start proxlb
-```
-
-### Container Images / Docker
-Using the ProxLB container images is straight forward and only requires you to mount the config file.
-
-```bash
-# Pull the image
-docker pull cr.gyptazy.com/proxlb/proxlb:latest
-# Download the config
-wget -O proxlb.yaml https://raw.githubusercontent.com/gyptazy/ProxLB/refs/heads/main/config/proxlb_example.yaml
-# Adjust the config to your needs
-vi proxlb.yaml
-# Start the ProxLB container image with the ProxLB config
-docker run -it --rm -v $(pwd)/proxlb.yaml:/etc/proxlb/proxlb.yaml proxlb
-```
-
-*Note: ProxLB container images are officially only available at cr.proxlb.de and cr.gyptazy.com.*
-
-#### Overview of Images
-| Version | Image |
-|------|:------:|
-| latest | cr.gyptazy.com/proxlb/proxlb:latest |
-| v1.1.10 | cr.gyptazy.com/proxlb/proxlb:v1.1.10 |
-| v1.1.9.1 | cr.gyptazy.com/proxlb/proxlb:v1.1.9.1 |
-| v1.1.9 | cr.gyptazy.com/proxlb/proxlb:v1.1.9 |
-| v1.1.8 | cr.gyptazy.com/proxlb/proxlb:v1.1.8 |
-| v1.1.7 | cr.gyptazy.com/proxlb/proxlb:v1.1.7 |
-| v1.1.6.1 | cr.gyptazy.com/proxlb/proxlb:v1.1.6.1 |
-| v1.1.6 | cr.gyptazy.com/proxlb/proxlb:v1.1.6 |
-| v1.1.5 | cr.gyptazy.com/proxlb/proxlb:v1.1.5 |
-| v1.1.4 | cr.gyptazy.com/proxlb/proxlb:v1.1.4 |
-| v1.1.3 | cr.gyptazy.com/proxlb/proxlb:v1.1.3 |
-| v1.1.2 | cr.gyptazy.com/proxlb/proxlb:v1.1.2 |
-| v1.1.1 | cr.gyptazy.com/proxlb/proxlb:v1.1.1 |
-| v1.1.0 | cr.gyptazy.com/proxlb/proxlb:v1.1.0 |
-| v1.0.6 | cr.gyptazy.com/proxlb/proxlb:v1.0.6 |
-| v1.0.5 | cr.gyptazy.com/proxlb/proxlb:v1.0.5 |
-| v1.0.4 | cr.gyptazy.com/proxlb/proxlb:v1.0.4 |
-| v1.0.3 | cr.gyptazy.com/proxlb/proxlb:v1.0.3 |
-| v1.0.2 | cr.gyptazy.com/proxlb/proxlb:v1.0.2 |
-| v1.0.0 | cr.gyptazy.com/proxlb/proxlb:v1.0.0 |
-| v0.9.9 | cr.gyptazy.com/proxlb/proxlb:v0.9.9 |
-
-### Source
-ProxLB can also easily be used from the provided sources - for traditional systems but also as a Docker/Podman container image.
-
-#### Traditional System
-Setting up and running ProxLB from the sources is simple and requires just a few commands. Ensure Python 3 and the Python dependencies are installed on your system, then run ProxLB using the following command:
-```bash
-git clone https://github.com/gyptazy/ProxLB.git
-cd ProxLB
-```
-
-Afterwards simply adjust the config file to your needs:
-```bash
-vi config/proxlb.yaml
-```
-
-Start ProxLB by Python3 on the system:
-```bash
-python3 proxlb/main.py -c config/proxlb.yaml
-```
-
-#### Container Image
-Creating a container image of ProxLB is straightforward using the provided Dockerfile. The Dockerfile simplifies the process by automating the setup and configuration required to get ProxLB running in an Alpine container. Simply follow the steps in the Dockerfile to build the image, ensuring all dependencies and configurations are correctly applied. For those looking for an even quicker setup, a ready-to-use ProxLB container image is also available, eliminating the need for manual building and allowing for immediate deployment.
-
-```bash
-git clone https://github.com/gyptazy/ProxLB.git
-cd ProxLB
-docker build -t proxlb .
-```
-
-Afterwards simply adjust the config file to your needs:
-```bash
-vi config/proxlb.yaml
-```
-
-Finally, start the created container.
-```bash
-docker run -it --rm -v $(pwd)/proxlb.yaml:/etc/proxlb/proxlb.yaml proxlb
-```
-
-## Usage / Configuration
-Running ProxLB is straightforward and versatile, as it only requires `Python3` and the `proxmoxer` library. This means ProxLB can be executed directly on a Proxmox node or on dedicated systems such as Debian, RedHat, or even FreeBSD, provided that the Proxmox API is accessible from the client running ProxLB. ProxLB can also run inside a Container - Docker or LXC - and is simply up to you.
-
-### GUI Integration
-<img align="left" src="https://cdn.gyptazy.com/img/rebalance-ui.jpg"/> ProxLB can also be accessed through the Proxmox Web UI by installing the optional `pve-proxmoxlb-service-ui` package, which depends on the proxlb package. For full Web UI integration, this package must be installed on all nodes within the cluster. Once installed, a new menu item - `Rebalancing`, appears in the cluster level under the HA section. Once installed, it offers two key functionalities:
-* Rebalancing VM workloads
-* Migrate VM workloads away from a defined node (e.g. maintenance preparation)
-
-**Note:** This package is currently discontinued and will be readded at a later time. See also: [#44: How to install pve-proxmoxlb-service-ui package](https://github.com/gyptazy/ProxLB/issues/44).
-
-### Proxmox HA Integration
-Proxmox HA (High Availability) groups are designed to ensure that virtual machines (VMs) remain running within a Proxmox cluster. HA groups define specific rules for where VMs should be started or migrated in case of node failures, ensuring minimal downtime and automatic recovery.
-
-However, when used in conjunction with ProxLB, the built-in load balancer for Proxmox, conflicts can arise. ProxLB operates with its own logic for workload distribution, taking into account affinity and anti-affinity rules. While it effectively balances guest workloads, it may re-shift and redistribute VMs in a way that does not align with HA group constraints, potentially leading to unsuitable placements.
-
-Due to these conflicts, it is currently not recommended to use both HA groups and ProxLB simultaneously. The interaction between the two mechanisms can lead to unexpected behavior, where VMs might not adhere to HA group rules after being moved by ProxLB.
-
-A solution to improve compatibility between HA groups and ProxLB is under evaluation, aiming to ensure that both features can work together without disrupting VM placement strategies.
-
-See also: [#65: Host groups: Honour HA groups](https://github.com/gyptazy/ProxLB/issues/65).
-
-### Options
-The following options can be set in the configuration file `proxlb.yaml`:
-
-| Section | Option | Sub Option | Example | Type | Description |
-|---------|:------:|:----------:|:-------:|:----:|:-----------:|
-| `proxmox_api` |  |  |  |  |  |
-|  | hosts |  | ['virt01.example.com', '10.10.10.10', 'fe01:bad:code::cafe', 'virt01.example.com:443', '[fc00::1]', '[fc00::1]:443', 'fc00::1:8006'] | `List` | List of Proxmox nodes. Can be IPv4, IPv6 or mixed. You can specify custom ports. In case of IPv6 without brackets the port is considered after the last colon |
-|  | user |  | root@pam | `Str` | Username for the API. |
-|  | pass |  | FooBar | `Str` | Password for the API. (Recommended: Use API token authorization!) |
-|  | token_id |  | proxlb | `Str` | Token ID of the user for the API. |
-|  | token_secret |  | 430e308f-1337-1337-beef-1337beefcafe | `Str` | Secret of the token ID for the API. |
-|  | ssl_verification |  | True | `Bool` | Validate SSL certificates (1) or ignore (0). [values: `1` (default), `0`] |
-|  | timeout |  | 10 | `Int` | Timeout for the Proxmox API in sec. |
-|  | retries |  | 1 | `Int` | How often a connection attempt to the defined API host should be performed. |
-|  | wait_time |  | 1 | `Int` | How many seconds should be waited before performing another connection attempt to the API host. |
-| `proxmox_cluster` |  |  |  |  |  |
-|  | maintenance_nodes |  | ['virt66.example.com'] | `List` | A list of Proxmox nodes that are defined to be in a maintenance. (must be the same node names as used within the cluster) |
-|  | ignore_nodes |  | [] | `List` | A list of Proxmox nodes that are defined to be ignored. |
-|  | overprovisioning |  | False | `Bool` | Avoids balancing when nodes would become overprovisioned. |
-| `balancing` |  |  |  |  |  |
-|  | enable |  | True | `Bool` | Enables the guest balancing.|
-|  | enforce_affinity |  | True | `Bool` | Enforcing affinity/anti-affinity rules but balancing might become worse. |
-|  | parallel |  | False | `Bool` | If guests should be moved in parallel or sequentially.|
-|  | parallel_jobs |  | 5 | `Int` | The amount if parallel jobs when migrating guests. (default: `5`)|
-|  | live |  | True | `Bool` | If guests should be moved live or shutdown.|
-|  | with_local_disks |  | True | `Bool` | If balancing of guests should include local disks.|
-|  | with_conntrack_state |  | True | `Bool` | If balancing of guests should including the conntrack state.|
-|  | balance_types |  | ['vm', 'ct'] | `List` | Defined the types of guests that should be honored. [values: `vm`, `ct`]|
-|  | max_job_validation |  | 1800 | `Int` | How long a job validation may take in seconds. (default: 1800) |
-|  | balanciness |  | 10 | `Int` | The maximum delta of resource usage between node with highest and lowest usage. |
-|  | memory_threshold |  | 75 | `Int` | The maximum threshold (in percent) that needs to be hit to perform balancing actions. (Optional) |
-|  | method |  | memory | `Str` | The balancing method that should be used.  [values: `memory` (default), `cpu`, `disk`]|
-|  | mode |  | used | `Str` | The balancing mode that should be used. [values: `used` (default), `assigned`, `psi` (pressure)] |
-|  | psi |  | { nodes: { memory: { pressure_full: 0.20, pressure_some: 0.20, pressure_spikes: 1.00 }}} | `Dict` | A dict of PSI based thresholds for nodes and guests |
-|  | pools |  | pools: { dev: { type: affinity }, de-nbg01-db: { type: anti-affinity }} | `Dict` | A dict of pool names and their type for creating affinity/anti-affinity rules |
-| `service` |  |  |  |  |  |
-|  | daemon |  | True | `Bool` | If daemon mode should be activated. |
-|  | `schedule` |  |  | `Dict` | Schedule config block for rebalancing. |
-|  |  | interval | 12 | `Int` | How often rebalancing should occur in daemon mode.|
-|  |  | format | hours | `Str` | Sets the time format. [values: `hours` (default), `minutes`]|
-|  | `delay` |  |  | `Dict` | Schedule config block for an optional delay until the service starts. |
-|  |  | enable | False | `Bool` | If a delay time should be validated.|
-|  |  | time | 1 | `Int` | Delay time until the service starts after the initial execution.|
-|  |  | format | hours | `Str` | Sets the time format. [values: `hours` (default), `minutes`]|
-|  | log_level |  | INFO | `Str` | Defines the default log level that should be logged. [values: `INFO` (default), `WARNING`, `CRITICAL`, `DEBUG`] |
-
-
-An example of the configuration file looks like:
-```
-proxmox_api:
-  hosts: ['virt01.example.com', '10.10.10.10', 'fe01:bad:code::cafe']
-  user: root@pam
-  pass: crazyPassw0rd!
-  # API Token method
-  # token_id: proxlb
-  # token_secret: 430e308f-1337-1337-beef-1337beefcafe
-  ssl_verification: True
-  timeout: 10
-  # API Connection retries
-  # retries: 1
-  # wait_time: 1
-
-proxmox_cluster:
-  maintenance_nodes: ['virt66.example.com']
-  ignore_nodes: []
-  overprovisioning: True
-
-balancing:
-  enable: True
-  enforce_affinity: False
-  parallel: False
-  live: True
-  with_local_disks: True
-  with_conntrack_state: True
-  balance_types: ['vm', 'ct']
-  max_job_validation: 1800
-  memory_threshold: 75
-  balanciness: 5
-  method: memory
-  mode: used
-# # PSI thresholds only apply when using mode 'psi'
-# # PSI based balancing is currently in beta and req. PVE >= 9
-# psi:
-#   nodes:
-#     memory:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-#     cpu:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-#     disk:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-#   guests:
-#     memory:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-#     cpu:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-#     disk:
-#       pressure_full: 0.20
-#       pressure_some: 0.20
-#       pressure_spikes: 1.00
-  pools:
-    dev:
-      type: affinity
-    de-nbg01-db
-      type: anti-affinity
-      pin:
-        - virt66
-        - virt77
-
-service:
-  daemon: True
-  schedule:
-    interval: 12
-    format: hours
-  delay:
-    enable: False
-    time: 1
-    format: hours
-  log_level: INFO
-```
-
-### Parameters
-The following options and parameters are currently supported:
-
-| Option | Long Option | Description | Default |
-|------|:------:|------:|------:|
-| -c | --config | Path to a config file. | /etc/proxlb/proxlb.yaml (default) |
-| -d | --dry-run | Performs a dry-run without doing any actions. | False |
-| -j | --json | Returns a JSON of the VM movement. | False |
-| -b | --best-node | Returns the best next node for a VM/CT placement (useful for further usage with Terraform/Ansible). | False |
-| -v | --version | Returns the ProxLB version on stdout. | False |
-
-## Affinity & Anti-Affinity Rules
-ProxLB provides an advanced mechanism to define affinity and anti-affinity rules, enabling precise control over virtual machine (VM) placement. These rules help manage resource distribution, improve high availability configurations, and optimize performance within a Proxmox Virtual Environment (PVE) cluster. By leveraging Proxmox’s integrated access management, ProxLB ensures that users can only define and manage rules for guests they have permission to access.
-
-ProxLB implements affinity and anti-affinity rules through a tag-based system within the Proxmox web interface. Each guest (virtual machine or container) can be assigned specific tags, which then dictate its placement behavior. This method maintains a streamlined and secure approach to managing VM relationships while preserving Proxmox’s inherent permission model.
-
-### Affinity Rules
-<img align="left" src="https://cdn.gyptazy.com/img/proxlb-affinity-rules.jpg"/> Affinity rules are used to group certain VMs together, ensuring that they run on the same host whenever possible. This can be beneficial for workloads requiring low-latency communication, such as clustered databases or application servers that frequently exchange data. In general, there're two ways to manage affinity rules:
-
-#### Affinity Rules by Tags
-To define an affinity rule which keeps all guests assigned to this tag together on a node, users assign a tag with the prefix `plb_affinity_$TAG`:
-
-#### Example for Screenshot
-```
-plb_affinity_talos
-```
-As a result, ProxLB will attempt to place all VMs with the `plb_affinity_web` tag on the same host (see also the attached screenshot with the same node).
-
-#### Affinity Rules by Pools
-Antoher approach is by using pools in Proxmox. This way, it can easily also combined with other resources like backup jobs. However, in this approach you need to modify the ProxLB config file to your needs. Within the `balancing` section you can create a dict of pools, including the pool name and the affinity type. Please see the example for further details:
-
-**Example Config**
-```
-balancing:
-  [...]
-  pools:                              # Optional: Define affinity/anti-affinity rules per pool
-    dev:                              # Pool name: dev
-      type: affinity                  # Type: affinity (keeping VMs together)
-      pin:                            # Pin VMs to Nodes
-        - virt77                        # Pinning to 'virt77' which is maybe an older system for dev labs
-```
-
-### Anti-Affinity Rules by Tags
-<img align="left" src="https://cdn.gyptazy.com/img/proxlb-anti-affinity-rules.jpg"/> Conversely, anti-affinity rules ensure that designated VMs do not run on the same physical host. This is particularly useful for high-availability setups, where redundancy is crucial. Ensuring that critical services are distributed across multiple hosts reduces the risk of a single point of failure. In general, there're two ways to manage anti-affinity rules:
-
-To define an anti-affinity rule that ensures to not move systems within this group to the same node, users assign a tag with the prefix:
-
-#### Example for Screenshot
-```
-plb_anti_affinity_ntp
-```
-
-As a result, ProxLB will try to place the VMs with the `plb_anti_affinity_ntp` tag on different hosts (see also the attached screenshot with the different nodes).
-
-#### Anti-Affinity Rules by Pools
-Antoher approach is by using pools in Proxmox. This way, it can easily also combined with other resources like backup jobs. However, in this approach you need to modify the ProxLB config file to your needs. Within the `balancing` section you can create a dict of pools, including the pool name and the affinity type. Please see the example for further details:
-
-**Example Config**
-```
-balancing:
-  [...]
-  pools:                              # Optional: Define affinity/anti-affinity rules per pool
-    de-nbg01-db:                      # Pool name: de-nbg01-db
-      type: anti-affinity                  # Type: anti-affinity (spreading VMs apart)
-```
-
-
-**Note:** While this ensures that ProxLB tries distribute these VMs across different physical hosts within the Proxmox cluster this may not always work. If you have more guests attached to the group than nodes in the cluster, we still need to run them anywhere. If this case occurs, the next one with the most free resources will be selected.
-
-### Ignore VMs
-<img align="left" src="https://cdn.gyptazy.com/img/proxlb-ignore-vm-movement.jpg"/> Guests, such as VMs or CTs, can also be completely ignored. This means, they won't be affected by any migration (even when (anti-)affinity rules are enforced). To ensure a proper resource evaluation, these guests are still collected and evaluated but simply skipped for balancing actions. Another thing is the implementation. While ProxLB might have a very restricted configuration file including the file permissions, this file is only read- and writeable by the Proxmox administrators. However, we might have user and groups who want to define on their own that their systems shouldn't be moved. Therefore, these users can simpy set a specific tag to the guest object - just like the (anti)affinity rules.
-
-To define a guest to be ignored from the balancing, users assign a tag with the prefix `plb_ignore_$TAG`:
-
-#### Example for Screenshot
-```
-plb_ignore_dev
-```
-
-As a result, ProxLB will not migrate this guest with the `plb_ignore_dev` tag to any other node.
-
-**Note:** Ignored guests are really ignored. Even by enforcing affinity rules this guest will be ignored.
-
-### Pin VMs to Specific Hypervisor Nodes
-<img align="left" src="https://cdn.gyptazy.com/img/proxlb-tag-node-pinning.jpg"/> Guests, such as VMs or CTs, can also be pinned to specific (and multiple) nodes in the cluster. This might be usefull when running applications with some special licensing requirements that are only fulfilled on certain nodes. It might also be interesting, when some physical hardware is attached to a node, that is not available in general within the cluster.
-
-#### Pinning VMs to (a) specific Hypervisor Node(s) by Tag
-To pin a guest to a specific cluster node, users assign a tag with the prefix `plb_pin_$nodename` to the desired guest:
-
-#### Example for Screenshot
-```
-plb_pin_node03
-```
-
-As a result, ProxLB will pin the guest `dev-vm01` to the node `virt03`.
-
-
-#### Pinning VMs to (a) specific Hypervisor Node(s) by Pools
-Beside the tag approach, you can also pin a resource group to a specific hypervisor or groups of hypervisors by defining a `pin` key of type list.
-
-**Example Config**
-```
-balancing:
-  [...]
-  pools:                              # Optional: Define affinity/anti-affinity rules per pool
-    dev:                              # Pool name: dev
-      type: affinity                  # Type: affinity (keeping VMs together)
-      pin:                            # Pin VMs to Nodes
-        - virt77                        # Pinning to 'virt77' which is maybe an older system for dev labs
-```
-
-
-You can also repeat this step multiple times for different node names to create a potential group of allowed hosts where a the guest may be served on. In this case, ProxLB takes the node with the lowest used resources according to the defined balancing values from this group.
-
-**Note:** The given node names from the tag are validated. This means, ProxLB validated if the given node name is really part of the cluster. In case of a wrongly defined or unavailable node name it continous to use the regular processes to make sure the guest keeps running.
-
-## Maintenance
-The `maintenance_nodes` option allows operators to designate one or more Proxmox nodes for maintenance mode. When a node is set to maintenance, no new guest workloads will be assigned to it, and all existing workloads will be migrated to other available nodes within the cluster. This process ensures that (anti)-affinity rules and resource availability are respected, preventing disruptions while maintaining optimal performance across the infrastructure.
-
-### Adding / Removing Nodes from Maintenance
-Within the section `proxmox_cluster` you can define the key `maintenance_nodes` as a list object. Simply add/remove one or more nodes with their equal name in the cluster and restart the daemon.
-```
-proxmox_cluster:
-  maintenance_nodes: ['virt66.example.com']
-```
-Afterwards, all guest objects will be moved to other nodes in the cluster by ensuring the best balancing.
-
-## Misc
-### Bugs
-Bugs can be reported via the GitHub issue tracker [here](https://github.com/gyptazy/ProxLB/issues). You may also report bugs via email or deliver PRs to fix them on your own. Therefore, you might also see the contributing chapter.
-
-### Contributing
-Feel free to add further documentation, to adjust already existing one or to contribute with code. Please take care about the style guide and naming conventions. You can find more in our [CONTRIBUTING.md](https://github.com/gyptazy/ProxLB/blob/main/CONTRIBUTING.md) file.
-
-### Support
-If you need assistance or have any questions, we offer support through our dedicated [chat room](https://matrix.to/#/#proxlb:gyptazy.com) in Matrix or [Discord](https://discord.gg/JemGu7WbfQ). Join our community for real-time help, advice, and discussions. The Matrix and Discord room are bridged to ensure that the communication is not splitted - so simply feel free to join which fits most to you!
-
-Connect with us in our dedicated chat room for immediate support and live interaction with other users and developers. You can also visit our [GitHub Community](https://github.com/gyptazy/ProxLB/discussions/) to post your queries, share your experiences, and get support from fellow community members and moderators. You may also just open directly an issue [here](https://github.com/gyptazy/ProxLB/issues) on GitHub.
-
-| Support Channel | Link |
-|------|:------:|
-| Matrix | [#proxlb:gyptazy.com](https://matrix.to/#/#proxlb:gyptazy.com) |
-| Discord | [Discord](https://discord.gg/JemGu7WbfQ) |
-| GitHub Community | [GitHub Community](https://github.com/gyptazy/ProxLB/discussions/)
-| GitHub | [ProxLB GitHub](https://github.com/gyptazy/ProxLB/issues) |
-
-**Note:** Please always keep in mind that this is a one-man show project without any further help. This includes coding, testing, packaging and all the infrastructure around it to keep this project up and running.
-
-### Enterprise-Support
-Running critical infrastructure in an enterprise environment often comes with requirements that go far beyond functionality alone. Enterprises typically expect predictable service levels, defined escalation paths, and guaranteed response times. In many cases, organizations also demand 24x7 support availability to ensure that their systems remain stable and resilient, even under unexpected circumstances.
-
-As the creator and maintainer of ProxLB, I operate as a one-man project. While I am continuously working to improve the software, I cannot provide the type of enterprise-grade support that large organizations may require. To address this need, several companies have stepped in to offer professional services around ProxLB in Proxmox VE clusters.
-
-Below is a list of organizations currently known to provide enterprise-level support for ProxLB. If your business relies on ProxLB in production and you require more than community-based support, these providers may be a good fit for your needs:
-
-| Company| Country | Web |
-|------|:------:|:------:|
-| credativ | DE | [credativ.de](https://www.credativ.de/en/portfolio/support/proxmox-virtualization/) |
-
-*Note: If you provide support for ProxLB, feel free to create PR with your addition.*
-
-### Author(s)
- * Florian Paul Azim Hoberg @gyptazy (https://gyptazy.com)
+## Reasons
+You can find more details about this in [my blog post](https://gyptazy.com/blog/proxlb-project-handover-to-credativ/).
--- a/config/proxlb_example.yaml
+++ b/config/proxlb_example.yaml
@@ -19,6 +19,7 @@ proxmox_cluster:
 balancing:
  enable: True
  enforce_affinity: False
+  enforce_pinning: False
  parallel: False
  # If running parallel job, you can define
  # the amount of prallel jobs (default: 5)
@@ -32,6 +33,12 @@ balancing:
  balanciness: 5                      # Maximum delta of resource usage between highest and lowest usage node
  method: memory                      # 'memory' | 'cpu' | 'disk'
  mode: used                          # 'assigned' | 'used' | 'psi'
+  balance_larger_guests_first: False  # Option to prioritize balancing of larger or smaller guests first
+  node_resource_reserve:              # Optional: Define resource reservations for nodes (in GB)
+    defaults:                         # Default reservation values applying to all nodes (unless explicitly overridden)
+      memory: 4                       # Default: 4 GB memory reserved per node
+    node01:                           # Specific node reservation override for node 'node01'
+      memory: 6                       # Specific: 6 GB memory reserved for node 'node01'
  # # PSI thresholds only apply when using mode 'psi'
  # psi:
  #   nodes:
@@ -68,6 +75,7 @@ balancing:
      pin:                            # Define a pinning og guests to specific node(s)
        - virt66
        - virt77
+      strict: False                   # Disable strict mode of node pinning for this pool

 service:
  daemon: True
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+proxlb (1.1.11) stable; urgency=medium
+
+  * Add support for native Proxmox HA/Affinity rules. (Closes: #391)
+  * Add safety guard to avoid node overprovisioning. (Closes: #275)
+  * Fix affinity rules pre-validation (avoid rebalancing if already ensured). (Closes: #335)
+  * Add resource reservation support for PVE nodes. (Closes: #373)
+  * Change/Adjust balancing and sorting behaviour. (Closes: #378)
+  * Add control over balancing workloads by prefering smaller/larger guest objects. (Closes: #387)
+  * Fix pinning of guest and node relations when using pool based pinning. (Closes: #395)
+  * Add validation of HA jobs by fetching the related child jobs. (Closes: #402)
+  * Add support for configuring node-pinning strictness (mode: strict/prefer). (Closes: #406)
+  * Fix that tag based ignored guests got still moved. (Closes: #408)
+  * Add parameter to enforce guest node relationships when pinned even when the cluster is balanced. (Closes: #414)
+
+ -- Florian Paul Azim Hoberg <gyptazy@gyptazy.com>  Mon, 12 Jan 2026 11:11:04 +0001
+
 proxlb (1.1.10) stable; urgency=medium

  * Prevent redundant rebalancing by validating existing affinity enforcement before taking actions. (Closes: #335)
--- a/docs/02_installation.md
+++ b/docs/02_installation.md
@@ -6,6 +6,7 @@
    - [Quick-Start](#quick-start)
    - [Details](#details)
    - [Debian Packages (.deb files)](#debian-packages-deb-files)
+    - [Repo Mirror and Proxmox Offline Mirror Support](#repo-mirror-and-proxmox-offline-mirror-support)
  - [RedHat Package](#redhat-package)
  - [Container Images / Docker](#container-images--docker)
    - [Overview of Images](#overview-of-images)
@@ -83,6 +84,27 @@ vi /etc/proxlb/proxlb.yaml
 systemctl start proxlb
 ```

+#### Repo Mirror and Proxmox Offline Mirror Support
+ProxLB uses the supported flat mirror style for the Debian repository. Unfortunately, not all offline-mirror applications support it. One of the known ones is the official *proxmox-offline-mirror* which is unable to handle flat repositories (see also: [#385](https://github.com/gyptazy/ProxLB/issues/385)).
+
+Therefore, we currently operate and support both ways to avoid everyone force switching to the new repository. As a result, you can simply use this repository:
+```
+deb https://repo.gyptazy.com/proxlb stable main
+```
+
+**Example Config for proxmox-offline-mirror:**
+
+An example config for the proxmox-offline-mirror would look like:
+```
+mirror: proxlb
+    architectures amd64
+    base-dir /var/lib/proxmox-offline-mirror/mirrors/
+    key-path /etc/apt/trusted.gpg.d/proxlb.asc
+    repository deb https://repo.gyptazy.com/proxlb stable main
+    sync true
+    verify true
+```
+
 ### RedHat Package
 There's currently no official support for RedHat based systems. However, there's a dummy .rpm package for such systems in the pipeline which can be found here:
 * https://github.com/gyptazy/ProxLB/actions/workflows/20-pipeline-build-rpm-package.yml
--- a/helm/proxlb/Chart.yaml
+++ b/helm/proxlb/Chart.yaml
@@ -2,5 +2,5 @@ apiVersion: v2
 name: proxlb
 description: A Helm chart for self-hosted ProxLB
 type: application
-version: "1.1.10"
-appVersion: "v1.1.10"
+version: "1.1.11"
+appVersion: "v1.1.11"
--- a/helm/proxlb/values.yaml
+++ b/helm/proxlb/values.yaml
@@ -1,7 +1,7 @@
 image:
  registry: cr.gyptazy.com
  repository: proxlb/proxlb
-  tag: v1.1.10
+  tag: v1.1.11
  pullPolicy: IfNotPresent
  imagePullSecrets: [ ]

--- a/proxlb/main.py
+++ b/proxlb/main.py
@@ -25,6 +25,7 @@ from models.groups import Groups
 from models.calculations import Calculations
 from models.balancing import Balancing
 from models.pools import Pools
+from models.ha_rules import HaRules
 from utils.helper import Helper


@@ -73,12 +74,14 @@ def main():
        # Get all required objects from the Proxmox cluster
        meta = {"meta": proxlb_config}
        nodes = Nodes.get_nodes(proxmox_api, proxlb_config)
+        meta = Features.validate_any_non_pve9_node(meta, nodes)
        pools = Pools.get_pools(proxmox_api)
-        guests = Guests.get_guests(proxmox_api, pools, nodes, meta, proxlb_config)
+        ha_rules = HaRules.get_ha_rules(proxmox_api, meta)
+        guests = Guests.get_guests(proxmox_api, pools, ha_rules, nodes, meta, proxlb_config)
        groups = Groups.get_groups(guests, nodes)

        # Merge obtained objects from the Proxmox cluster for further usage
-        proxlb_data = {**meta, **nodes, **guests, **pools, **groups}
+        proxlb_data = {**meta, **nodes, **guests, **pools, **ha_rules, **groups}
        Helper.log_node_metrics(proxlb_data)

        # Validate usable features by PVE versions
@@ -87,6 +90,7 @@ def main():
        # Update the initial node resource assignments
        # by the previously created groups.
        Calculations.set_node_assignments(proxlb_data)
+        Helper.log_node_metrics(proxlb_data, init=False)
        Calculations.set_node_hot(proxlb_data)
        Calculations.set_guest_hot(proxlb_data)
        Calculations.get_most_free_node(proxlb_data, cli_args.best_node)
--- a/proxlb/models/balancing.py
+++ b/proxlb/models/balancing.py
@@ -226,8 +226,23 @@ class Balancing:
        logger.debug("Starting: get_rebalancing_job_status.")
        job = proxmox_api.nodes(guest_current_node).tasks(job_id).status().get()

+        # Fetch actual migration job status if this got spawned by a HA job
+        if job["type"] == "hamigrate":
+            logger.debug(f"Balancing: Job ID {job_id} (guest: {guest_name}) is a HA migration job. Fetching underlying migration job...")
+            time.sleep(1)
+            vm_id = int(job["id"])
+            qm_migrate_jobs = proxmox_api.nodes(guest_current_node).tasks.get(typefilter="qmigrate", vmid=vm_id, start=0, source="active", limit=1)
+
+            if len(qm_migrate_jobs) > 0:
+                job = qm_migrate_jobs[0]
+                job_id = job["upid"]
+                logger.debug(f'Overwriting job polling for: ID {job_id} (guest: {guest_name}) by {job}')
+        else:
+            logger.debug(f"Balancing: Job ID {job_id} (guest: {guest_name}) is a standard migration job. Proceeding with status check.")
+
        # Watch job id until it finalizes
-        if job["status"] == "running":
+        # Note: Unsaved jobs are delivered in uppercase from Proxmox API
+        if job.get("status", "").lower() == "running":
            # Do not hammer the API while
            # watching the job status
            time.sleep(10)
--- a/proxlb/models/calculations.py
+++ b/proxlb/models/calculations.py
@@ -369,7 +369,12 @@ class Calculations:
        None
        """
        logger.debug("Starting: relocate_guests.")
-        if proxlb_data["meta"]["balancing"]["balance"] or proxlb_data["meta"]["balancing"].get("enforce_affinity", False):
+
+        # Balance only if it is required by:
+        #  - balanciness
+        #  - Affinity/Anti-Affinity rules
+        # - Pinning rules
+        if proxlb_data["meta"]["balancing"]["balance"] or proxlb_data["meta"]["balancing"].get("enforce_affinity", False) or proxlb_data["meta"]["balancing"].get("enforce_pinning", False):

            if proxlb_data["meta"]["balancing"].get("balance", False):
                logger.debug("Balancing of guests will be performed. Reason: balanciness")
@@ -377,15 +382,56 @@ class Calculations:
            if proxlb_data["meta"]["balancing"].get("enforce_affinity", False):
                logger.debug("Balancing of guests will be performed. Reason: enforce affinity balancing")

-            for group_name in proxlb_data["groups"]["affinity"]:
+            if proxlb_data["meta"]["balancing"].get("enforce_pinning", False):
+                logger.debug("Balancing of guests will be performed. Reason: enforce pinning balancing")

-                # We get initially the node with the most free resources and then
-                # migrate all guests within the group to that node to ensure the
-                # affinity.
-                Calculations.get_most_free_node(proxlb_data)
+            # Sort guests by used memory
+            # Allows processing larger guests first or smaller guests first
+            larger_first = proxlb_data.get("meta", {}).get("balancing", {}).get("balance_larger_guests_first", False)
+
+            if larger_first:
+                logger.debug("Larger guests will be processed first. (Sorting descending by memory used)")
+            else:
+                logger.debug("Smaller guests will be processed first. (Sorting ascending by memory used)")
+
+            # Sort affinity groups by number of guests to avoid creating more migrations than needed
+            # because of affinity-groups and use afterwards memory for defining smaller/larger guests
+            sorted_guest_usage_groups = sorted(
+                proxlb_data["groups"]["affinity"],
+                key=lambda g: (
+                    proxlb_data["groups"]["affinity"][g]["counter"],
+                    -proxlb_data["groups"]["affinity"][g]["memory_used"]
+                    if larger_first
+                    else proxlb_data["groups"]["affinity"][g]["memory_used"],
+                )
+            )
+
+            # Iterate over all affinity groups
+            for group_name in sorted_guest_usage_groups:
+
+                # Validate balanciness again before processing each group
+                Calculations.get_balanciness(proxlb_data)
+                logger.debug(proxlb_data["meta"]["balancing"]["balance"])
+
+                if (not proxlb_data["meta"]["balancing"]["balance"]) and (not proxlb_data["meta"]["balancing"].get("enforce_affinity", False)) and (not proxlb_data["meta"]["balancing"].get("enforce_pinning", False)):
+                    logger.debug("Skipping further guest relocations as balanciness is now ok.")
+                    break

                for guest_name in proxlb_data["groups"]["affinity"][group_name]["guests"]:
+
+                    # Stop moving guests if the source node is no longer the most loaded
+                    source_node = proxlb_data["guests"][guest_name]["node_current"]
+                    method = proxlb_data["meta"]["balancing"].get("method", "memory")
                    mode = proxlb_data["meta"]["balancing"].get("mode", "used")
+                    highest_node = max(proxlb_data["nodes"].values(), key=lambda n: n[f"{method}_used_percent"])
+
+                    if highest_node["name"] != source_node:
+                        logger.debug(f"Stopping relocation for guest {guest_name}: source node {source_node} is no longer the most loaded node.")
+                        break
+
+                    if not Calculations.validate_node_resources(proxlb_data, guest_name):
+                        logger.warning(f"Skipping relocation of guest {guest_name} due to insufficient resources on target node {proxlb_data['meta']['balancing']['balance_next_node']}. This might affect affinity group {group_name}.")
+                        continue

                    if mode == 'psi':
                        logger.debug(f"Evaluating guest relocation based on {mode} mode.")
@@ -483,8 +529,20 @@ class Calculations:
        if len(proxlb_data["guests"][guest_name]["node_relationships"]) > 0:
            logger.debug(f"Guest '{guest_name}' has relationships defined to node(s): {','.join(proxlb_data['guests'][guest_name]['node_relationships'])}. Pinning to node.")

-            # Get the node with the most free resources of the group
+            # Get the list of nodes that are defined as relationship for the guest
            guest_node_relation_list = proxlb_data["guests"][guest_name]["node_relationships"]
+
+            # Validate if strict relationships are defined. If not, we prefer
+            # the most free node in addition to the relationship list.
+            if proxlb_data["guests"][guest_name]["node_relationships_strict"]:
+                logger.debug(f"Guest '{guest_name}' has strict node relationships defined. Only nodes in the relationship list will be considered for pinning.")
+            else:
+                logger.debug(f"Guest '{guest_name}' has non-strict node relationships defined. Prefering nodes in the relationship list for pinning.")
+                Calculations.get_most_free_node(proxlb_data)
+                most_free_node = proxlb_data["meta"]["balancing"]["balance_next_node"]
+                guest_node_relation_list.append(most_free_node)
+
+            # Get the most free node from the relationship list, or the most free node overall
            Calculations.get_most_free_node(proxlb_data, False, guest_node_relation_list)

            # Validate if the specified node name is really part of the cluster
@@ -564,8 +622,14 @@ class Calculations:
        proxlb_data["nodes"][node_current]["disk_used_percent"] = proxlb_data["nodes"][node_current]["disk_used"] / proxlb_data["nodes"][node_current]["disk_total"] * 100

        # Assign guest to the new target node
-        proxlb_data["guests"][guest_name]["node_target"] = node_target
-        logger.debug(f"Set guest {guest_name} from node {node_current} to node {node_target}.")
+        if not proxlb_data["guests"][guest_name]["ignore"]:
+            proxlb_data["guests"][guest_name]["node_target"] = node_target
+            logger.debug(f"Set guest {guest_name} from node {node_current} to node {node_target}.")
+        else:
+            logger.debug(f"Guest {guest_name} is marked as ignored. Skipping target node assignment.")
+
+        Calculations.recalc_node_statistics(proxlb_data, node_target)
+        Calculations.recalc_node_statistics(proxlb_data, node_current)

        logger.debug("Finished: update_node_resources.")

@@ -605,7 +669,7 @@ class Calculations:
            logger.debug(f"Affinity for guest {guest} is {'valid' if balancing_state_affinity else 'NOT valid'}")
            logger.debug(f"Anti-affinity for guest {guest} is {'valid' if balancing_state_anti_affinity else 'NOT valid'}")

-            balancing_ok = not balancing_state_affinity or not balancing_state_anti_affinity
+            balancing_ok = balancing_state_affinity and balancing_state_anti_affinity

        if balancing_ok:
            logger.debug(f"Rebalancing based on affinity/anti-affinity map is not required.")
@@ -707,3 +771,68 @@ class Calculations:
                return False

        return True
+
+    @staticmethod
+    def validate_node_resources(proxlb_data: Dict[str, Any], guest_name: str) -> bool:
+        """
+        Validate that the target node has sufficient resources to host the specified guest.
+
+        This function checks if the target node, determined by the balancing logic,
+        has enough CPU, memory, and disk resources available to accommodate the guest.
+
+        Args:
+            proxlb_data (Dict[str, Any]): A dictionary containing the complete ProxLB state including:
+                - "nodes": Dictionary with node resource information
+                - "guests": Dictionary with guest resource requirements
+                - "meta": Dictionary with balancing information including target node
+            guest_name (str): The name of the guest to validate resources for
+        Returns:
+            bool: True if the target node has sufficient resources, False otherwise
+        """
+        logger.debug("Starting: validate_node_resources.")
+        node_target = proxlb_data["meta"]["balancing"]["balance_next_node"]
+
+        node_memory_free = proxlb_data["nodes"][node_target]["memory_free"]
+        node_cpu_free = proxlb_data["nodes"][node_target]["cpu_free"]
+        node_disk_free = proxlb_data["nodes"][node_target]["disk_free"]
+
+        guest_memory_required = proxlb_data["guests"][guest_name]["memory_used"]
+        guest_cpu_required = proxlb_data["guests"][guest_name]["cpu_used"]
+        guest_disk_required = proxlb_data["guests"][guest_name]["disk_used"]
+
+        if guest_memory_required < node_memory_free:
+            logger.debug(f"Node '{node_target}' has sufficient resources ({node_memory_free / (1024 ** 3):.2f} GB free) for guest '{guest_name}'.")
+            logger.debug("Finished: validate_node_resources.")
+            return True
+        else:
+            logger.debug(f"Node '{node_target}' lacks sufficient resources ({node_memory_free / (1024 ** 3):.2f} GB free) for guest '{guest_name}'.")
+            logger.debug("Finished: validate_node_resources.")
+            return False
+
+    @staticmethod
+    def recalc_node_statistics(proxlb_data: Dict[str, Any], node_name: str) -> None:
+        """
+        Recalculates node statistics including free resources and usage percentages.
+
+        This function updates the computed statistics for a node based on its current
+        resource allocation and usage. It calculates free resources, usage percentages,
+        and assigned percentages for CPU, memory, and disk.
+
+        Args:
+            proxlb_data (Dict[str, Any]): A dictionary containing the complete ProxLB state including:
+            - "nodes": Dictionary with node resource information
+            node_name (str): The name of the node to recalculate statistics for
+
+        Returns:
+            None: Modifies proxlb_data in-place by updating node statistics
+        """
+        n = proxlb_data["nodes"][node_name]
+        n["cpu_free"] = max(0, n["cpu_total"] - n["cpu_used"])
+        n["memory_free"] = max(0, n["memory_total"] - n["memory_used"])
+        n["disk_free"] = max(0, n["disk_total"] - n["disk_used"])
+        n["cpu_used_percent"] = (n["cpu_used"] / n["cpu_total"] * 100) if n["cpu_total"] else 0
+        n["memory_used_percent"] = (n["memory_used"] / n["memory_total"] * 100) if n["memory_total"] else 0
+        n["disk_used_percent"] = (n["disk_used"] / n["disk_total"] * 100) if n["disk_total"] else 0
+        n["cpu_assigned_percent"] = (n["cpu_assigned"] / n["cpu_total"] * 100) if n["cpu_total"] else 0
+        n["memory_assigned_percent"] = (n["memory_assigned"] / n["memory_total"] * 100) if n["memory_total"] else 0
+        n["disk_assigned_percent"] = (n["disk_assigned"] / n["disk_total"] * 100) if n["disk_total"] else 0
--- a/proxlb/models/features.py
+++ b/proxlb/models/features.py
@@ -88,3 +88,37 @@ class Features:
                proxlb_data["meta"]["balancing"]["enable"] = False

        logger.debug("Finished: validate_available_features.")
+
+    @staticmethod
+    def validate_any_non_pve9_node(meta: any, nodes: any) -> dict:
+        """
+        Validate if any node in the cluster is running Proxmox VE < 9.0.0 and update meta accordingly.
+
+        This function inspects the cluster node versions and sets a flag in meta indicating whether
+        any node is running a Proxmox VE version older than 9.0.0.
+
+        Args:
+            meta (dict):    Metadata structure that will be updated with cluster version information.
+            nodes (dict):   Cluster nodes mapping whose values contain 'pve_version' strings.
+
+        Returns:
+            dict:           The updated meta dictionary with 'cluster_non_pve9' flag set to True or False.
+
+        Side effects:
+            - Mutates meta["meta"]["cluster_non_pve9"] based on node versions.
+            - Emits debug log messages.
+
+        Notes:
+            - Version comparison uses semantic version parsing; defaults to "0.0.0" if pve_version is missing.
+        """
+        logger.debug("Starting: validate_any_non_pve9_node.")
+        any_non_pve9_node = any(version.parse(node.get("pve_version", "0.0.0")) < version.parse("9.0.0") for node in nodes.get("nodes", {}).values())
+
+        if any_non_pve9_node:
+            meta["meta"]["cluster_non_pve9"] = True
+            logger.debug("Finished: validate_any_non_pve9_node. Result: True")
+        else:
+            meta["meta"]["cluster_non_pve9"] = False
+            logger.debug("Finished: validate_any_non_pve9_node. Result: False")
+
+        return meta
--- a/proxlb/models/guests.py
+++ b/proxlb/models/guests.py
@@ -11,6 +11,7 @@ __license__ = "GPL-3.0"
 from typing import Dict, Any
 from utils.logger import SystemdLogger
 from models.pools import Pools
+from models.ha_rules import HaRules
 from models.tags import Tags
 import time

@@ -36,7 +37,7 @@ class Guests:
        """

    @staticmethod
-    def get_guests(proxmox_api: any, pools: Dict[str, Any], nodes: Dict[str, Any], meta: Dict[str, Any], proxlb_config: Dict[str, Any]) -> Dict[str, Any]:
+    def get_guests(proxmox_api: any, pools: Dict[str, Any], ha_rules: Dict[str, Any], nodes: Dict[str, Any], meta: Dict[str, Any], proxlb_config: Dict[str, Any]) -> Dict[str, Any]:
        """
        Get metrics of all guests in a Proxmox cluster.

@@ -46,6 +47,8 @@ class Guests:

        Args:
            proxmox_api (any): The Proxmox API client instance.
+            pools (Dict[str, Any]): A dictionary containing information about the pools in the Proxmox cluster.
+            ha_rules (Dict[str, Any]): A dictionary containing information about the HA rules in the
            nodes (Dict[str, Any]): A dictionary containing information about the nodes in the Proxmox cluster.
            meta (Dict[str, Any]): A dictionary containing metadata information.
            proxmox_config (Dict[str, Any]): A dictionary containing the ProxLB configuration.
@@ -95,10 +98,12 @@ class Guests:
                    guests['guests'][guest['name']]['pressure_hot'] = False
                    guests['guests'][guest['name']]['tags'] = Tags.get_tags_from_guests(proxmox_api, node, guest['vmid'], 'vm')
                    guests['guests'][guest['name']]['pools'] = Pools.get_pools_for_guest(guest['name'], pools)
-                    guests['guests'][guest['name']]['affinity_groups'] = Tags.get_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], proxlb_config)
-                    guests['guests'][guest['name']]['anti_affinity_groups'] = Tags.get_anti_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], proxlb_config)
+                    guests['guests'][guest['name']]['ha_rules'] = HaRules.get_ha_rules_for_guest(guest['name'], ha_rules, guest['vmid'])
+                    guests['guests'][guest['name']]['affinity_groups'] = Tags.get_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
+                    guests['guests'][guest['name']]['anti_affinity_groups'] = Tags.get_anti_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
                    guests['guests'][guest['name']]['ignore'] = Tags.get_ignore(guests['guests'][guest['name']]['tags'])
-                    guests['guests'][guest['name']]['node_relationships'] = Tags.get_node_relationships(guests['guests'][guest['name']]['tags'], nodes, guests['guests'][guest['name']]['pools'], proxlb_config)
+                    guests['guests'][guest['name']]['node_relationships'] = Tags.get_node_relationships(guests['guests'][guest['name']]['tags'], nodes, guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
+                    guests['guests'][guest['name']]['node_relationships_strict'] = Pools.get_pool_node_affinity_strictness(proxlb_config, guests['guests'][guest['name']]['pools'])
                    guests['guests'][guest['name']]['type'] = 'vm'

                    logger.debug(f"Resources of Guest {guest['name']} (type VM) added: {guests['guests'][guest['name']]}")
@@ -140,10 +145,12 @@ class Guests:
                    guests['guests'][guest['name']]['pressure_hot'] = False
                    guests['guests'][guest['name']]['tags'] = Tags.get_tags_from_guests(proxmox_api, node, guest['vmid'], 'ct')
                    guests['guests'][guest['name']]['pools'] = Pools.get_pools_for_guest(guest['name'], pools)
-                    guests['guests'][guest['name']]['affinity_groups'] = Tags.get_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], proxlb_config)
-                    guests['guests'][guest['name']]['anti_affinity_groups'] = Tags.get_anti_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], proxlb_config)
+                    guests['guests'][guest['name']]['ha_rules'] = HaRules.get_ha_rules_for_guest(guest['name'], ha_rules, guest['vmid'])
+                    guests['guests'][guest['name']]['affinity_groups'] = Tags.get_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
+                    guests['guests'][guest['name']]['anti_affinity_groups'] = Tags.get_anti_affinity_groups(guests['guests'][guest['name']]['tags'], guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
                    guests['guests'][guest['name']]['ignore'] = Tags.get_ignore(guests['guests'][guest['name']]['tags'])
-                    guests['guests'][guest['name']]['node_relationships'] = Tags.get_node_relationships(guests['guests'][guest['name']]['tags'], nodes, guests['guests'][guest['name']]['pools'], proxlb_config)
+                    guests['guests'][guest['name']]['node_relationships'] = Tags.get_node_relationships(guests['guests'][guest['name']]['tags'], nodes, guests['guests'][guest['name']]['pools'], guests['guests'][guest['name']]['ha_rules'], proxlb_config)
+                    guests['guests'][guest['name']]['node_relationships_strict'] = Pools.get_pool_node_affinity_strictness(proxlb_config, guests['guests'][guest['name']]['pools'])
                    guests['guests'][guest['name']]['type'] = 'ct'

                    logger.debug(f"Resources of Guest {guest['name']} (type CT) added: {guests['guests'][guest['name']]}")
--- a/proxlb/models/ha_rules.py
+++ b/proxlb/models/ha_rules.py
@@ -0,0 +1,126 @@
+"""
+The HaRules class retrieves all HA rules defined on a Proxmox cluster
+including their affinity settings and member resources.
+"""
+
+__author__ = "Florian Paul Azim Hoberg <gyptazy>"
+__copyright__ = "Copyright (C) 2025 Florian Paul Azim Hoberg (@gyptazy)"
+__license__ = "GPL-3.0"
+
+
+from typing import Dict, Any
+from utils.logger import SystemdLogger
+
+logger = SystemdLogger()
+
+
+class HaRules:
+    """
+    The HaRules class retrieves all HA rules defined on a Proxmox cluster
+    including their (anti)a-ffinity settings and member resources and translates
+    them into a ProxLB usable format.
+
+    Methods:
+        __init__:
+            Initializes the HaRules class.
+
+        get_ha_rules(proxmox_api: any) -> Dict[str, Any]:
+            Retrieve HA rule definitions from the Proxmox cluster.
+            Returns a dict with a top-level "ha_rules" mapping each rule id to
+            {"rule": <rule_id>, "type": <affinity_type>, "members": [<resource_ids>...]}.
+            Converts affinity settings to descriptive format (affinity or anti-affinity).
+    """
+    def __init__(self):
+        """
+        Initializes the HA Rules class with the provided ProxLB data.
+        """
+
+    @staticmethod
+    def get_ha_rules(proxmox_api: any, meta: dict) -> Dict[str, Any]:
+        """
+        Retrieve all HA rules from a Proxmox cluster.
+
+        Queries the Proxmox API for HA rule definitions and returns a dictionary
+        containing each rule's id, affinity type, and member resources (VM/CT IDs).
+        This function processes rule affinity settings and converts them to a more
+        descriptive format (affinity or anti-affinity).
+
+        Args:
+            proxmox_api (any):      Proxmox API client instance.
+            meta (dict):            The metadata dictionary containing cluster information.
+
+        Returns:
+            Dict[str, Any]:         Dictionary with a top-level "ha_rules" key mapping rule id
+                                    to {"rule": <rule_id>, "type": <affinity_type>, "members": [<resource_ids>...]}.
+        """
+        logger.debug("Starting: get_ha_rules.")
+        ha_rules = {"ha_rules": {}}
+
+        # If any node is non PVE 9, skip fetching HA rules as they are unsupported
+        if meta["meta"]["cluster_non_pve9"]:
+            logger.debug("Skipping HA rule retrieval as non Proxmox VE 9 systems detected.")
+            return ha_rules
+        else:
+            logger.debug("Cluster running Proxmox VE 9 or newer, proceeding with HA rule retrieval.")
+
+        for rule in proxmox_api.cluster.ha.rules.get():
+
+            # Skip disabled rules (disable key exists AND is truthy)
+            if rule.get("disable", 0):
+                logger.debug(f"Skipping ha-rule: {rule['rule']} of type {rule['type']} affecting guests: {rule['resources']}. Rule is disabled.")
+                continue
+
+            # Create a resource list by splitting on commas and stripping whitespace containing
+            # the VM and CT IDs that are part of this HA rule
+            resources_list_guests = [int(r.split(":")[1]) for r in rule["resources"].split(",") if r.strip()]
+
+            # Convert the affinity field to a more descriptive type
+            if rule.get("affinity", None) == "negative":
+                affinity_type = "anti-affinity"
+            else:
+                affinity_type = "affinity"
+
+            # Create affected nodes list
+            resources_list_nodes = []
+            if rule.get("nodes", None):
+                resources_list_nodes = [n for n in rule["nodes"].split(",") if n]
+
+            # Create the ha_rule element
+            ha_rules['ha_rules'][rule['rule']] = {}
+            ha_rules['ha_rules'][rule['rule']]['rule'] = rule['rule']
+            ha_rules['ha_rules'][rule['rule']]['type'] = affinity_type
+            ha_rules['ha_rules'][rule['rule']]['nodes'] = resources_list_nodes
+            ha_rules['ha_rules'][rule['rule']]['members'] = resources_list_guests
+
+            logger.debug(f"Got ha-rule: {rule['rule']} as type {affinity_type} affecting guests: {rule['resources']}")
+
+        logger.debug("Finished: ha_rules.")
+        return ha_rules
+
+    @staticmethod
+    def get_ha_rules_for_guest(guest_name: str, ha_rules: Dict[str, Any], vm_id: int) -> Dict[str, Any]:
+        """
+        Return the list of HA rules that include the given guest.
+
+        Args:
+            guest_name (str):               Name of the VM or CT to look up.
+            ha_rules (Dict[str, Any]):      HA rules structure as returned by get_ha_rules(),
+                                            expected to contain a top-level "ha_rules" mapping each rule id to
+                                            {"rule": <rule_id>, "type": <affinity_type>, "members": [<resource_ids>...]}.
+            vm_id (int):                    VM or CT ID of the guest.
+
+        Returns:
+            list:                           IDs of HA rules the guest is a member of (empty list if none).
+        """
+        logger.debug("Starting: get_ha_rules_for_guest.")
+        guest_ha_rules = []
+
+        for rule in ha_rules["ha_rules"].values():
+            if vm_id in rule.get("members", []):
+                logger.debug(f"Guest: {guest_name} (VMID: {vm_id}) is member of HA Rule: {rule['rule']}.")
+                guest_ha_rules.append(rule)
+            else:
+                logger.debug(f"Guest: {guest_name} (VMID: {vm_id}) is NOT member of HA Rule: {rule['rule']}.")
+
+        logger.debug("Finished: get_ha_rules_for_guest.")
+        return guest_ha_rules
--- a/proxlb/models/nodes.py
+++ b/proxlb/models/nodes.py
@@ -24,6 +24,7 @@ __license__ = "GPL-3.0"
 import time
 from typing import Dict, Any
 from utils.logger import SystemdLogger
+from utils.helper import Helper

 logger = SystemdLogger()

@@ -77,7 +78,7 @@ class Nodes:
                nodes["nodes"][node["node"]]["cpu_pressure_some_spikes_percent"] = Nodes.get_node_rrd_data(proxmox_api, node["node"], "cpu", "some", spikes=True)
                nodes["nodes"][node["node"]]["cpu_pressure_full_spikes_percent"] = Nodes.get_node_rrd_data(proxmox_api, node["node"], "cpu", "full", spikes=True)
                nodes["nodes"][node["node"]]["cpu_pressure_hot"] = False
-                nodes["nodes"][node["node"]]["memory_total"] = node["maxmem"]
+                nodes["nodes"][node["node"]]["memory_total"] = Nodes.set_node_resource_reservation(node["node"], node["maxmem"], proxlb_config, "memory")
                nodes["nodes"][node["node"]]["memory_assigned"] = 0
                nodes["nodes"][node["node"]]["memory_used"] = node["mem"]
                nodes["nodes"][node["node"]]["memory_free"] = node["maxmem"] - node["mem"]
@@ -253,3 +254,59 @@ class Nodes:
        logger.debug(f"Got version {version['version']} for node {node_name}.")
        logger.debug("Finished: get_node_pve_version.")
        return version["version"]
+
+    @staticmethod
+    def set_node_resource_reservation(node_name, resource_value, proxlb_config, resource_type) -> int:
+        """
+        Check if there is a configured resource reservation for the current node and apply it as needed.
+        Checks for a node specific config first, then if there is any configured default and if neither then nothing is reserved.
+        Reservations are applied by directly modifying the resource value.
+
+        Args:
+            node_name (str):                    The name of the node.
+            resource_value (int):               The total resource value in bytes.
+            proxlb_config (Dict[str, Any]):     A dictionary containing the ProxLB configuration.
+            resource_type (str):                The type of resource ('memory', 'disk', etc.).
+
+        Returns:
+            int:                                The resource value after applying any configured reservations.
+        """
+        logger.debug(f"Starting: apply_resource_reservation")
+
+        balancing_cfg = proxlb_config.get("balancing", {})
+        reserve_cfg = balancing_cfg.get("node_resource_reserve", {})
+        node_resource_reservation = reserve_cfg.get(node_name, {}).get(resource_type, 0)
+        default_resource_reservation = reserve_cfg.get("defaults", {}).get(resource_type, 0)
+
+        # Ensure reservations are numeric values
+        node_resource_reservation = node_resource_reservation if isinstance(node_resource_reservation, (int, float)) else 0
+        default_resource_reservation = default_resource_reservation if isinstance(default_resource_reservation, (int, float)) else 0
+
+        # Apply node specific reservation if set
+        if node_resource_reservation > 0:
+            if resource_value < (node_resource_reservation * 1024 ** 3):
+                logger.critical(f"Configured resource reservation for node {node_name} of type {resource_type} with {node_resource_reservation} GB is higher than available resource value {resource_value / (1024 ** 3):.2f} GB. Not applying...")
+                return resource_value
+            else:
+                logger.debug(f"Applying node specific reservation for {node_name} of type {resource_type} with {node_resource_reservation} GB.")
+                resource_value_new = resource_value - (node_resource_reservation * 1024 ** 3)
+                logger.debug(f'Switched resource value for node {node_name} of type {resource_type} from {resource_value / (1024 ** 3):.2f} GB to {resource_value_new / (1024 ** 3):.2f} GB after applying reservation.')
+                logger.debug(f"Before: {resource_value} | After: {resource_value_new}")
+                return resource_value_new
+
+        # Apply default reservation if set and no node specific reservation has been performed
+        elif default_resource_reservation > 0:
+            if resource_value < (default_resource_reservation * 1024 ** 3):
+                logger.critical(f"Configured default reservation for node {node_name} of type {resource_type} with {default_resource_reservation} GB is higher than available resource value {resource_value / (1024 ** 3):.2f} GB. Not applying...")
+                return resource_value
+            else:
+                logger.debug(f"Applying default reservation for {node_name} of type {resource_type} with {default_resource_reservation} GB.")
+                resource_value_new = resource_value - (default_resource_reservation * 1024 ** 3)
+                logger.debug(f'Switched resource value for node {node_name} of type {resource_type} from {resource_value / (1024 ** 3):.2f} GB to {resource_value_new / (1024 ** 3):.2f} GB after applying reservation.')
+                logger.debug(f"Before: {resource_value} | After: {resource_value_new}")
+                return resource_value_new
+
+        else:
+            logger.debug(f"No default or node specific resource reservation for node {node_name} found. Skipping...")
+            logger.debug(f"Finished: apply_resource_reservation")
+            return resource_value
--- a/proxlb/models/pools.py
+++ b/proxlb/models/pools.py
@@ -115,3 +115,29 @@ class Pools:

        logger.debug("Finished: get_pools_for_guests.")
        return guest_pools
+
+    @staticmethod
+    def get_pool_node_affinity_strictness(proxlb_config: Dict[str, Any], guest_pools: list) -> bool:
+        """
+        Retrieve the node affinity strictness setting for a guest across its pools.
+
+        Queries the ProxLB configuration to determine the node affinity strictness
+        level for the specified guest based on its pool memberships. Returns the
+        strictness setting from the first matching pool configuration.
+
+        Args:
+            proxlb_config (Dict[str, Any]):     ProxLB configuration dictionary.
+            guest_pools (list):                 List of pool names the guest belongs to.
+
+        Returns:
+            bool:                               Node affinity strictness setting (default True if not specified).
+        """
+        logger.debug("Starting: get_pool_node_affinity_strictness.")
+
+        node_strictness = True
+        for pool in guest_pools:
+            pool_settings = proxlb_config.get("balancing", {}).get("pools", {}).get(pool, {})
+            node_strictness = pool_settings.get("strict", True)
+
+        logger.debug("Finished: get_pool_node_affinity_strictness.")
+        return node_strictness
--- a/proxlb/models/tags.py
+++ b/proxlb/models/tags.py
@@ -80,7 +80,7 @@ class Tags:
        return tags

    @staticmethod
-    def get_affinity_groups(tags: List[str], pools: List[str], proxlb_config: Dict[str, Any]) -> List[str]:
+    def get_affinity_groups(tags: List[str], pools: List[str], ha_rules: List[str], proxlb_config: Dict[str, Any]) -> List[str]:
        """
        Get affinity tags for a guest from the Proxmox cluster by the API.

@@ -91,6 +91,7 @@ class Tags:
        Args:
            tags (List): A list holding all defined tags for a given guest.
            pools (List): A list holding all defined pools for a given guest.
+            ha_rules (List): A list holding all defined ha_rules for a given guest.
            proxlb_config (Dict): A dict holding the ProxLB configuration.

        Returns:
@@ -99,14 +100,16 @@ class Tags:
        logger.debug("Starting: get_affinity_groups.")
        affinity_tags = []

+        # Tag based affinity groups
        if len(tags) > 0:
            for tag in tags:
                if tag.startswith("plb_affinity"):
                    logger.debug(f"Adding affinity group for tag {tag}.")
                    affinity_tags.append(tag)
                else:
-                    logger.debug(f"Skipping affinity group for tag {tag}.")
+                    logger.debug(f"Skipping evaluation of tag: {tag} This is not an affinity tag.")

+        # Pool based affinity groups
        if len(pools) > 0:
            for pool in pools:
                if pool in (proxlb_config['balancing'].get('pools') or {}):
@@ -114,13 +117,20 @@ class Tags:
                        logger.debug(f"Adding affinity group for pool {pool}.")
                        affinity_tags.append(pool)
                else:
-                    logger.debug(f"Skipping affinity group for pool {pool}.")
+                    logger.debug(f"Skipping evaluation of pool: {pool} This is not an affinity pool.")
+
+        # HA rule based affinity groups
+        if len(ha_rules) > 0:
+            for ha_rule in ha_rules:
+                if ha_rule.get('type', None) == 'affinity':
+                    logger.debug(f"Adding affinity group for ha-rule {ha_rule}.")
+                    affinity_tags.append(ha_rule['rule'])

        logger.debug("Finished: get_affinity_groups.")
        return affinity_tags

    @staticmethod
-    def get_anti_affinity_groups(tags: List[str], pools: List[str], proxlb_config: Dict[str, Any]) -> List[str]:
+    def get_anti_affinity_groups(tags: List[str], pools: List[str], ha_rules: List[str], proxlb_config: Dict[str, Any]) -> List[str]:
        """
        Get anti-affinity tags for a guest from the Proxmox cluster by the API.

@@ -131,6 +141,7 @@ class Tags:
        Args:
            tags (List): A list holding all defined tags for a given guest.
            pools (List): A list holding all defined pools for a given guest.
+            ha_rules (List): A list holding all defined ha_rules for a given guest.
            proxlb_config (Dict): A dict holding the ProxLB configuration.

        Returns:
@@ -139,14 +150,16 @@ class Tags:
        logger.debug("Starting: get_anti_affinity_groups.")
        anti_affinity_tags = []

+        # Tag based anti-affinity groups
        if len(tags) > 0:
            for tag in tags:
                if tag.startswith("plb_anti_affinity"):
                    logger.debug(f"Adding anti-affinity group for tag {tag}.")
                    anti_affinity_tags.append(tag)
                else:
-                    logger.debug(f"Skipping anti-affinity group for tag {tag}.")
+                    logger.debug(f"Skipping evaluation of tag: {tag} This is not an anti-affinity tag.")

+        # Pool based anti-affinity groups
        if len(pools) > 0:
            for pool in pools:
                if pool in (proxlb_config['balancing'].get('pools') or {}):
@@ -154,7 +167,14 @@ class Tags:
                        logger.debug(f"Adding anti-affinity group for pool {pool}.")
                        anti_affinity_tags.append(pool)
                else:
-                    logger.debug(f"Skipping anti-affinity group for pool {pool}.")
+                    logger.debug(f"Skipping evaluation of pool: {pool} This is not an anti-affinity pool.")
+
+        # HA rule based anti-affinity groups
+        if len(ha_rules) > 0:
+            for ha_rule in ha_rules:
+                if ha_rule.get('type', None) == 'anti-affinity':
+                    logger.debug(f"Adding anti-affinity group for ha-rule {ha_rule}.")
+                    anti_affinity_tags.append(ha_rule['rule'])

        logger.debug("Finished: get_anti_affinity_groups.")
        return anti_affinity_tags
@@ -177,15 +197,20 @@ class Tags:
        ignore_tag = False

        if len(tags) > 0:
+            logger.debug(f"Found {len(tags)} tags to evaluate.")
            for tag in tags:
+                logger.debug(f"Evaluating tag: {tag}.")
                if tag.startswith("plb_ignore"):
+                    logger.debug(f"Found valid ignore tag: {tag}. Marking guest as ignored.")
                    ignore_tag = True
+                else:
+                    logger.debug(f"Tag: {tag} This is not an ignore tag.")

        logger.debug("Finished: get_ignore.")
        return ignore_tag

    @staticmethod
-    def get_node_relationships(tags: List[str], nodes: Dict[str, Any], pools: List[str], proxlb_config: Dict[str, Any]) -> str:
+    def get_node_relationships(tags: List[str], nodes: Dict[str, Any], pools: List[str], ha_rules: List[str], proxlb_config: Dict[str, Any]) -> str:
        """
        Get a node relationship tag for a guest from the Proxmox cluster by the API to pin
        a guest to a node or by defined pools from ProxLB configuration.
@@ -197,6 +222,7 @@ class Tags:
            tags (List): A list holding all defined tags for a given guest.
            nodes (Dict): A dictionary holding all available nodes in the cluster.
            pools (List): A list holding all defined pools for a given guest.
+            ha_rules (List): A list holding all defined ha_rules for a given guest.
            proxlb_config (Dict): A dict holding the ProxLB configuration.

        Returns:
@@ -205,6 +231,7 @@ class Tags:
        logger.debug("Starting: get_node_relationships.")
        node_relationship_tags = []

+        # Tag based node relationship
        if len(tags) > 0:
            logger.debug("Validating node pinning by tags.")
            for tag in tags:
@@ -219,21 +246,38 @@ class Tags:
                    else:
                        logger.warning(f"Tag {node_relationship_tag} is invalid! Defined node does not exist in the cluster. Not applying pinning.")

+        # Pool based node relationship
        if len(pools) > 0:
            logger.debug("Validating node pinning by pools.")
            for pool in pools:
                if pool in (proxlb_config['balancing'].get('pools') or {}):

-                    node = proxlb_config['balancing']['pools'][pool].get('pin', None)
-                    # Validate if the node to pin is present in the cluster
-                    if Helper.validate_node_presence(node, nodes):
-                        logger.debug(f"Pool pinning tag {node} is valid! Defined node exists in the cluster.")
-                        logger.debug(f"Setting node relationship because of pool {pool} to {node}.")
-                        node_relationship_tags.append(node)
-                    else:
-                        logger.warning(f"Pool pinning tag {node} is invalid! Defined node does not exist in the cluster. Not applying pinning.")
+                    pool_nodes = proxlb_config['balancing']['pools'][pool].get('pin', None)
+                    for node in pool_nodes if pool_nodes is not None else []:
+
+                        # Validate if the node to pin is present in the cluster
+                        if Helper.validate_node_presence(node, nodes):
+                            logger.debug(f"Pool pinning tag {node} is valid! Defined node exists in the cluster.")
+                            logger.debug(f"Setting node relationship because of pool {pool} to {node}.")
+                            node_relationship_tags.append(node)
+                        else:
+                            logger.warning(f"Pool pinning tag {node} is invalid! Defined node does not exist in the cluster. Not applying pinning.")
+
                else:
                    logger.debug(f"Skipping pinning for pool {pool}. Pool is not defined in ProxLB configuration.")

+        # HA rule based node relationship
+        if len(ha_rules) > 0:
+            logger.debug("Validating node pinning by ha-rules.")
+            for ha_rule in ha_rules:
+                if len(ha_rule.get("nodes", 0)) > 0:
+                    if ha_rule.get("type", None) == "affinity":
+                        logger.debug(f"ha-rule {ha_rule['rule']} is of type affinity.")
+                        for node in ha_rule["nodes"]:
+                            logger.debug(f"Adding {node} as node relationship because of ha-rule {ha_rule['rule']}.")
+                            node_relationship_tags.append(node)
+                    else:
+                        logger.debug(f"ha-rule {ha_rule['rule']} is of type anti-affinity. Skipping node relationship addition.")
+
        logger.debug("Finished: get_node_relationships.")
        return node_relationship_tags
--- a/proxlb/utils/helper.py
+++ b/proxlb/utils/helper.py
@@ -81,6 +81,7 @@ class Helper:
        """
        logger.debug("Starting: log_node_metrics.")
        nodes_usage_memory = " | ".join([f"{key}: {value['memory_used_percent']:.2f}%" for key, value in proxlb_data["nodes"].items()])
+        nodes_assigned_memory = " | ".join([f"{key}: {value['memory_assigned_percent']:.2f}%" for key, value in proxlb_data["nodes"].items()])
        nodes_usage_cpu = "  | ".join([f"{key}: {value['cpu_used_percent']:.2f}%" for key, value in proxlb_data["nodes"].items()])
        nodes_usage_disk = " | ".join([f"{key}: {value['disk_used_percent']:.2f}%" for key, value in proxlb_data["nodes"].items()])

@@ -90,6 +91,7 @@ class Helper:
            proxlb_data["meta"]["statistics"]["after"] = {"memory": nodes_usage_memory, "cpu": nodes_usage_cpu, "disk": nodes_usage_disk}

        logger.debug(f"Nodes usage memory: {nodes_usage_memory}")
+        logger.debug(f"Nodes usage memory assigned: {nodes_assigned_memory}")
        logger.debug(f"Nodes usage cpu:    {nodes_usage_cpu}")
        logger.debug(f"Nodes usage disk:   {nodes_usage_disk}")
        logger.debug("Finished: log_node_metrics.")
--- a/proxlb/utils/version.py
+++ b/proxlb/utils/version.py
@@ -3,5 +3,5 @@ __app_desc__ = "An advanced resource scheduler and load balancer for Proxmox clu
 __author__ = "Florian Paul Azim Hoberg <gyptazy>"
 __copyright__ = "Copyright (C) 2025 Florian Paul Azim Hoberg (@gyptazy)"
 __license__ = "GPL-3.0"
-__version__ = "1.1.10"
+__version__ = "1.1.11"
 __url__ = "https://github.com/gyptazy/ProxLB"
--- a/setup.py
+++ b/setup.py
@@ -2,7 +2,7 @@ from setuptools import setup

 setup(
    name="proxlb",
-    version="1.1.10",
+    version="1.1.11",
    description="An advanced resource scheduler and load balancer for Proxmox clusters.",
    long_description="An advanced resource scheduler and load balancer for Proxmox clusters that also supports maintenance modes and affinity/anti-affinity rules.",
    author="Florian Paul Azim Hoberg",
Author	SHA1	Message	Date
gyptazy	c39301ca96	docs(README): Define the new location of ProxLB at credativ	2026-01-15 13:14:42 +01:00
gyptazy	b7a6fcec0c	doc(README): Define new location of the ProxLB project at credativ Updated README to reflect the new location of the ProxLB project and removed outdated sections.	2026-01-15 13:13:06 +01:00
gyptazy	9966fbb13f	Merge pull request #421 from gyptazy/fix/420-fix-psi-based-balancing-mode fix(calculations): Fix PSI based balancing which resulted in a Python KeyError	2026-01-13 10:32:04 +01:00
gyptazy	e6ae357838	fix(calculations): Fix PSI based balancing which resulted in a Python KeyError Fixes: #420	2026-01-13 08:24:50 +01:00
gyptazy	65b1bd5fee	Merge pull request #418 from gyptazy/release/1.1.11 release: Create release 1.1.11	2026-01-12 07:15:48 +01:00
gyptazy	72283d8c19	release: Create release 1.1.11 Fixes: #405	2026-01-09 14:22:27 +01:00
gyptazy	4f85feacde	Merge pull request #415 from gyptazy/feature/414-enfoce-pinning feature: Add new option to enforce node/guest pinning even when cluster is balanced from a resource perspective.	2026-01-09 10:09:09 +01:00
Florian Paul Azim Hoberg	34e340c25c	feature: Add new option to enforce node/guest pinning even when cluster is balanced from a resource perspective. Fixes: #414	2026-01-08 16:50:06 +01:00
gyptazy	da193f9d27	Merge pull request #412 from gyptazy/feature/406-strict-nonstrict-node-pinning Add support for configuring node-pinning strictness (default: true) within pools	2026-01-04 12:28:40 +01:00
gyptazy	f11ca263b8	Add support for configuring node-pinning strictness (default: true) within pools Fixes: #406	2025-12-30 08:52:55 +01:00
gyptazy	0af770c9df	Merge pull request #410 from gyptazy/change/378-adjust-balancing-decisions Change balancing and sorting behaviour of guests	2025-12-29 13:12:21 +01:00
gyptazy	a9d11daf40	Change balancing and sorting behaviour of guests - Sort to be balanced guests first by size of affinity group (ASC) - Sort to be balanced guests afterwards by used memory size (ASC/DESC) - Validate if lowest used node is still the lowest one Fixes: #378 Fixes: #390	2025-12-29 12:44:58 +01:00
gyptazy	ab7ee0d687	Merge pull request #409 from gyptazy/fix/tags-ignore Fix that ignored VMs/CTs got moved to another node when being ignored.	2025-12-25 18:29:32 +01:00
gyptazy	e841481fdd	Fix that ignored VMs/CTs got moved to another node when being ignored. Fixes: #408	2025-12-24 16:43:12 +01:00
gyptazy	5b7cc6727f	Merge pull request #407 from hugobugomugo/patch-1 add docker compose to install instructions	2025-12-24 09:18:11 +01:00
gyptazy	15a05d320e	Merge pull request #404 from gyptazy/feature/373-add-resource-reservation-for-nodes Feature/resource reservation (#380)	2025-12-24 09:10:12 +01:00
gyptazy	e0331e83e1	Adjust the integration of node resource reservation - Renamed to set_node_resource_reservation - Immediately apply the values as maxmem for a node - Avoid recalculating percentage values - Simplified code - Adjusted debug logging	2025-12-24 09:06:39 +01:00
hugo	ffd74d47e9	add docker compose to install instructions	2025-12-23 23:37:41 +01:00
gyptazy	89ad425243	Add config exmaples to README for resource reservations on node level Fixes: #373	2025-12-23 15:30:15 +01:00
Chipmonk2	2ce3d73262	Feature/resource reservation (#380 ) Add resource reservation of memory for nodes	2025-12-23 15:08:29 +01:00
gyptazy	b8093454d7	Merge pull request #403 from gyptazy/feature/402-add-ha-job-status-validation-for-migrations feature: Add HA job validation for migration jobs	2025-12-23 15:02:10 +01:00
Florian Paul Azim Hoberg	d7631ef8f5	feature: Add HA job validation for migration jobs Fixes: #402	2025-12-16 20:38:35 +01:00
gyptazy	d546036a9a	Merge pull request #401 from gyptazy/feature/391_improve_native_ha_rules_pve8 fix: HA affinity/anti-affinity rules can only be evaluated on PVE9+ nodes	2025-12-14 09:37:47 +01:00
gyptazy	09b5b83c24	fix: HA affinity/anti-affinity rules can only be evaluated on PVE9+ nodes Fixes: #391	2025-12-14 09:34:21 +01:00
gyptazy	8d61ccfbb1	Merge pull request #399 from gyptazy/fix/395-fix-non-existent-pool-stacktrace fix: Fix crashing on non-existent pools	2025-12-13 20:06:16 +01:00
gyptazy	b39c13e2a5	fix: Fix crashing on non-existent pools Fixes: #395	2025-12-13 20:05:11 +01:00
gyptazy	8e759b778c	Merge pull request #396 from gyptazy/fix/395_fix_pool_based_node_pinning fix: Fixed pool and ha-rules based node pinning of guests.	2025-12-12 08:04:23 +01:00
Florian Paul Azim Hoberg	22406e3628	fix: Fixed pool and ha-rules based node pinning of guests. * Fixed pool based node pinning (@gyptazy). [#395] * Add support for Proxmox's native HA (node-affinity) rules for pinning guests to nodes (@gyptazy). [#391] Fixes: #395 Fixes: #391	2025-12-11 14:43:44 +01:00
gyptazy	e7f5d5142e	Merge pull request #392 from gyptazy/pipeline/dynamic-versioning-packages pipline: Generate snapshot package	2025-12-10 12:51:37 +01:00
Florian Paul Azim Hoberg	48d621a06d	pipline: Generate snapshot package	2025-12-10 12:42:28 +01:00
Florian Paul Azim Hoberg	c133ef1aee	feature: Add support for Proxmox's native HA (affinity/anti-affinity) rules. * Add support of native rules for affinity/anti-affinity types in Proxmox VE * Streamline affinity/anti-affinity rules by Tags, Pools and native Proxmox rules Fixes: #391	2025-12-10 09:11:28 +01:00
gyptazy	9ea04f904d	Merge pull request #388 from gyptazy/feature/387-select-balancing-workloads-by-size feature: Add possibility to sort and select balancing workloads by smaller/larger guest objects	2025-12-08 15:52:25 +01:00
Florian Paul Azim Hoberg	5101202f72	feature: Add possibility to sort and select balancing workloads by smaller/larger guest objects - Allows operators to select if first larger or smaller workloads should be migrated Fixes: #387	2025-12-08 15:44:38 +01:00
gyptazy	929390b288	Merge pull request #386 from gyptazy/docs/385-proxmox-offline-mirror-repo-support docs: Add documentation about offline repor mirror and proxmox-offline-mirror suppot	2025-12-06 16:12:37 +01:00
gyptazy	d4560c3af4	docs: Add documentation about offline repor mirror and proxmox-offline-mirror support * Offline mirror support (air-gapped envs) * Add new full Debian repository Fixes: #385	2025-12-06 12:26:15 +01:00
gyptazy	55c885194e	Merge pull request #382 from gyptazy/fix/275-add-overprovisioning-safety-guard fix(calculations): Add safety guard to avoid overprovisioning of nodes by memory	2025-12-06 11:19:38 +01:00
gyptazy	3d9f0eb85e	fix(calculations): Add safety guard to avoid overprovisioning of nodes by memory. Fixes: #275	2025-12-02 09:59:51 +01:00
gyptazy	490fb55ee1	Merge pull request #376 from Thalagyrt/patch-affinity-rebalance Fix enforce_affinity boolean inversion	2025-11-27 08:41:05 +01:00
James Riley	a70330d4c3	Fix enforce_affinity boolean inversion During runs in which affinity checks determine balancing actions, there was a small error in a boolean calculation that caused ProxLB to always rebalance, as it exited the verification loop with a failure the first time it saw a VM that actually passed affinity checks.	2025-11-26 07:06:28 -07:00