Consumer ownership
During live migration:
- Instance UUID owns destination allocations.
- Migration UUID owns source allocations.
These are allocation sets: each consumer can hold resources across multiple providers.
Consumer ownership
During live migration:
These are allocation sets: each consumer can hold resources across multiple providers.
| [[local|localrc]] | |
| # Minimal Contents | |
| # ---------------- | |
| # While ``stack.sh`` is happy to run without ``localrc``, devlife is better when | |
| # there are a few minimal variables set: | |
| # If the ``*_PASSWORD`` variables are not set here you will be prompted to enter | |
| # values for them by ``stack.sh``and they will be added to ``local.conf``. |
| #cloud-config | |
| disable_root: false | |
| ssh_pwauth: true | |
| users: | |
| - default | |
| - name: stack | |
| groups: [sudo] | |
| shell: /bin/bash |
This is a quick concept and workflow mapping for thinking about KubeVirt from an OpenStack Nova perspective.
| OpenStack / Nova | KubeVirt / OpenShift Virtualization | Notes |
|---|---|---|
| Nova server / instance | VirtualMachine + VirtualMachineInstance |
VirtualMachine is desired state; VirtualMachineInstance is the running guest. |
| Running libvirt domain | VirtualMachineInstance |
The live domain generated by KubeVirt. |
This document summarizes the changes between commit 38b5e63cf3d56df4568a9640e40ea3283ada7b95 (previous iteration) and the current HEAD (10487db642cf5580d20016dde25ab1423b0c1ad7). The spec underwent significant expansion with 491 insertions and 168 deletions, adding substantial detail on future work, implementation details, and use cases.
The placement service in OpenStack is an inventory management system.
Placement models the available resources in an OpenStack cloud as a set of resource providers in a tree structure. Each resource provider has inventories of consumable resource classes such as CPUs, memory, disks, and capabilities known as traits.
# Watcher 2026.1 Gazpacho PTG Report
## Executive Summary
The OpenStack Watcher project held its virtual Project Teams Gathering (PTG)
from October 27-31, 2025, to plan the 2026.1 Gazpacho development cycle. The
event brought together key contributors including sean-k-mooney, dviroel,
rlandy, chandan, jgilaber, amoralej, and efoley to address critical technical
debt, modernization efforts, and strategic improvements. The PTG resulted in| *Watcher 2026.1 Gazpacho virtual PTG | |
| *DO NOT USE TRANSLATION TOOLS IN THIS ETHERPAD!!!! (ノ ゜Д゜)ノ ┻━┻ | |
| *不要在这个ETHERPAD中使用翻译工具! | |
| To translate this etherpad, please follow these easy instructions: | |
| 1. Look in the above toolbar and click the '</>' ("Share this pad") button | |
| 2. Click the "Read only" checkbox at the top of the dialog box | |
| 3. Copy the URL that appears in the "Link" box | |
| 4. Open that URL in a new browser tab or window | |
| 5. Use your translation tools of choice in the new window | |
| Thank you! |
Note: This document is a working implementation guide and will not be committed
to the repository. All permanent documentation will be in reStructuredText format
under doc/source/contributor/.
This document provides a concrete, phased implementation plan for code quality improvements. The plan is structured around deliverable outcomes rather than incremental tooling, with each phase being self-contained, self-testing, and self-documenting.
This document outlines a concrete, incremental plan to improve code quality across the repository with a focus on:
*) imports with a single allowed exceptiongetattr, hasattr,
setattr) including common Django patterns