PowerVC is an OpenStack based cloud provider with some significant
differences. Since we can use the OpenStack provider for most of the
work, we will create a thin provider which will only handle the
differences.
Instead of just starting the UI container and leaving conmon to manage
it (e.g. by restarting on failure), continue to manage it with systemd
as we do for all other podman containers.
Replace manually-maintained GraphViz DOT files with an auto-generation
system that parses systemd unit files and generates diagrams showing
service dependencies and workflow structure.
Key features:
- Parses systemd units from data/data/agent/systemd/units
- Extracts Before/After dependencies for edges
- Infers cluster membership from PartOf/BindsTo relationships
- Filters services by workflow based on discriminator files
- Shows file creation during workflows (node-zero creates node0, etc)
- Auto-detects disconnected services and marks with thin borders
- Auto-computes workflow differences (add-nodes vs install)
- Maintains consistent layout with invisible edge chains
Only a small number of exceptions are hardcoded:
- load-config-iso@ triggered by udev (unconfigured_ignition only)
- 99-agent-copy-files.sh excluded from interactive (agent-extract-tui provides tui)
- agent-interactive-console services disabled in unconfigured-ignition
Assisted-by: Claude Code
Convert the agent installer service workflow diagrams from PNG to
maintainable GraphViz DOT format. This allows the diagrams to be
edited as text files rather than requiring image editing tools.
Changes:
- Add GraphViz DOT source files for all four workflows
- Add Makefile to generate PNGs from DOT sources
- Add README with build and editing instructions
- Regenerate all PNG files from DOT sources
The new workflow enables easier maintenance and collaboration:
cd docs/user/agent/diagrams
edit *.dot files
make
Assisted-by: Claude Code
Created agent-extract-tui.service for the interactive-disconnected
workflow to extract the agent-tui and nmstate libraries during boot.
The files are extracted from the agent-install-utils image. In the
interactive-disconnected workflow, the image is available on the
local container storage. They need to be extracted before the
agent-interactive-console.service starts.
Bumping CAPI provider version is currently a manual step with little
documentation to follow. This commit gathers all knowledge of such steps
for other contributors.
* docs: remove ovirt from supported platforms
* docs: add ibmcloud, nutanix, and powervs as supported platform
* docs: reorganized and added powervs upi
* docs: remove libvirt from supported list
* docs: include official docs for supported platforms and deduplication
When using a network as an additional network in the OCP cluster
that has an IPv6 Subnet, that subnet must be included in the router
to provide router advertisements, otherwise the interface wouldn't get
an address configured. This happens because the network manager is
configured with method=auto.
Addition of doc changes for minimal ISO support. Since the minimal ISO
for all platforms is very similiar to the External platform, combine the
documentation into one file.
