kvmfleet-bmc-adapters 0.7.0__tar.gz

kvmfleet_bmc_adapters-0.7.0/.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: ruff check .
+
+      - name: Typecheck with mypy
+        run: mypy bmc_adapters
+
+      - name: Run tests
+        run: pytest -v

kvmfleet_bmc_adapters-0.7.0/.github/workflows/release.yml

@@ -0,0 +1,39 @@
+name: Release
+
+# Publishes to PyPI when a version tag is pushed (e.g. `v0.7.0`). Uses PyPI
+# Trusted Publishing (OIDC) — no API token stored in the repo. This requires a
+# one-time setup on PyPI: project settings → Publishing → add a GitHub
+# publisher for owner `KVMFleet`, repo `bmc-adapters`, workflow `release.yml`,
+# environment `pypi`.
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write # OIDC token for Trusted Publishing
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build + test deps
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev,all]" build
+
+      - name: Test (gate the publish on a green suite)
+        run: pytest -q
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

kvmfleet_bmc_adapters-0.7.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.venv/
+venv/
+dist/
+build/
+.coverage
+htmlcov/

kvmfleet_bmc_adapters-0.7.0/CHANGELOG.md

@@ -0,0 +1,289 @@
+# Changelog
+
+All notable changes to `kvmfleet-bmc-adapters` are recorded here.
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
+versioning is [SemVer](https://semver.org/).
+
+## [0.7.0] — 2026-06-15
+
+### Added — Command-line interface (`kvmfleet-bmc`)
+
+A new console script ships with the package — an operator CLI over the async
+Redfish client. It's a thin dispatch layer with no behaviour of its own; the
+library remains the primary surface.
+
+- `kvmfleet-bmc --host <url> -u <user> info` — make / model / serial /
+  firmware inventory.
+- `kvmfleet-bmc ... power {status,on,off,off-hard,cycle,reboot}` — power
+  control and current state.
+- `kvmfleet-bmc ... thermal` — temperature and fan readings.
+- `kvmfleet-bmc ... health` — power state + health rollup; exits non-zero
+  (3) when health is not OK, so it drops straight into monitoring.
+- Password via `--password` or the `BMC_PASSWORD` environment variable
+  (preferred — keeps it out of the process table and shell history).
+- `--json` on every command for machine-readable output.
+- TLS verification is off by default (BMCs ship self-signed certs); pass
+  `--verify-tls` to enforce it.
+
+### Added — Redfish Server-Sent Events (`RedfishClient.stream_events`)
+
+- `stream_events()` — async generator that opens the BMC's Redfish
+  EventService SSE stream (`ServerSentEventUri`) and yields
+  `RedfishEventRecord`s as the BMC pushes them (power, thermal, lifecycle
+  alerts) — no polling. Runs until the stream closes or the caller stops
+  iterating; no read timeout, but a connect timeout so a dead BMC fails fast.
+- `event_service_sse_uri()` — returns the SSE URI, or `None` when the BMC has
+  no EventService / doesn't advertise SSE (the signal to fall back to
+  `sel_entries()` polling). Vendor support varies (common on iDRAC9 / iLO5 /
+  OpenBMC; absent on older firmware).
+- `RedfishEventRecord` dataclass — `message_id`, `message`, `severity`,
+  `event_type`, `event_timestamp`, `origin_of_condition`, and `raw`.
+- Tolerant SSE framing: keep-alive comment lines are skipped, both the
+  `Event`-with-`Events[]` and bare-record payload shapes are handled, and
+  malformed JSON from a noisy BMC is dropped rather than crashing the consumer.
+
+### Added — Redfish collection pagination + `$expand` (fleet scale)
+
+- `RedfishClient` now follows `Members@odata.nextLink` on every collection it
+  walks (processors, memory, drives, volumes, NICs, firmware, SEL, BMC users),
+  so dense chassis and long event logs no longer silently lose members past
+  the first page.
+- `expand_collection(path)` — read a whole collection in one paginated
+  `$expand=.($levels=1)` sweep (member bodies inlined, no N+1 round-trips),
+  falling back to plain paginated reads when the BMC rejects `$expand`.
+- The internal collection walker takes an optional `limit` so capped reads
+  (e.g. `sel_entries(limit=…)`) stop paging once they have enough.
+
+### Added — Opt-in Redfish response validation
+
+- `validate_redfish_resource(data)` — dependency-free check of the Redfish
+  structural contract: required `@odata.id`, well-formed `@odata.type`,
+  collection consistency (`Members` list, `Members@odata.count` vs page),
+  and legal `Status.Health` / `Status.State` / `PowerState` enum values.
+  Returns collected `RedfishValidationIssue`s; never raises.
+- `validate_against_schema(data, schema)` — full JSON-Schema validation
+  against a schema *you* supply, via the optional `jsonschema` dependency
+  (`pip install 'kvmfleet-bmc-adapters[schema]'`). The multi-megabyte DMTF
+  schema set is intentionally **not** vendored — point this at your own copy.
+- `RedfishClient.validate_resource(path, *, schema=None)` — GET + validate.
+
+### Added — Wider vendor recognition
+
+- `detect_vendor()` now recognises **Cisco** (CIMC/UCS → `cisco-cimc`),
+  **Fujitsu** (PRIMERGY iRMC → `fujitsu-irmc`), **Huawei** (iBMC →
+  `huawei-ibmc`), and **OpenBMC** (→ `openbmc`) from their documented Oem
+  keys / Manager ids, alongside the existing iDRAC / iLO / Supermicro /
+  Lenovo XCC. These all speak standard Redfish, so the client's operations
+  work regardless of the label — it just drives caller branching and
+  incremental per-vendor quirk handling.
+- Plus the **AMI MegaRAC whitebox family** — `gigabyte`, `asrockrack`,
+  `tyan`, `quanta`, `inspur`, and the generic `ami-megarac` OEM stack
+  (specific vendor key wins over the generic AMI key). These boards already
+  worked via the `redfish-generic` path; naming them lets callers branch and
+  enables the right per-board firmware findings. **Recognised from documented
+  signatures, not yet hardware-verified** (see README) — no overclaim.
+
+### Fixed
+
+- Collection-iterating methods previously read only the first page of
+  paginated collections — now corrected (see above).
+- `ACTION_TO_REDFISH` contract test now covers the `reboot` verb.
+
+## [0.6.0] — 2026-06-06
+
+Tier 3: Dell RACADM legacy adapter and a reusable async-SSH
+transport. Scope intentionally tight — 10 commands cover the
+operator surface that Redfish doesn't reach on iDRAC6/7 (and the
+"Redfish wedged, fall back" path on iDRAC8/9).
+
+### Added — Shared SSH transport (`bmc_adapters.transport.ssh`)
+
+- `AsyncSSHCLIClient` — persistent asyncssh connection with
+  bounded per-host concurrency, idle-friendly defaults, and
+  legacy KEX / host-key algorithm support for older BMCs
+  (iDRAC6/7, older CMC).
+- `SSHCreds` — username + password / key pair.
+- Used by the RACADM adapter; reserved for future SSH-CLI
+  wrappers.
+
+### Added — Dell RACADM adapter (`bmc_adapters.racadm`)
+
+- `RACADMClient` — async wrapper around the `racadm` SSH shell.
+- 10-command core:
+  - Power: `power_action` (on/off/off_hard/cycle/reboot/soft),
+    `power_status`.
+  - Inventory: `get_system_info`, `get_version`,
+    `get_service_tag`.
+  - Logs: `get_sel`.
+  - BMC mgmt: `racreset` (soft / hard).
+  - Property DB: `get(fqdd)`, `set(fqdd, value)`.
+- Per-command parsers; permissive against firmware-version
+  output churn.
+- Optional dependency — install with `[ssh]` extra
+  (`pip install 'kvmfleet-bmc-adapters[ssh]'`).
+
+### Dropped from scope (intentional)
+
+- **HPE RIBCL** — iLO 4 firmware ≥ 2.30 (April 2016) has
+  working Redfish. iLO 5/6 are Redfish-first. Niche of a
+  shrinking niche. Implement only if a paying customer asks.
+- **Supermicro SUM / SMCIPMITool** — closed-source; can't
+  bundle. Redfish covers X12+.
+- **Lenovo OneCLI** — XCC3 is Redfish-aligned by design.
+  Closed-source.
+- **Cisco UCS IMC** — wrong audience (Intersight shops).
+- **OpenBMC console** — console multiplexing is a different
+  product surface entirely.
+
+## [0.5.0] — 2026-06-05
+
+Tier 2 expansion: PiKVM ATX, IPMI Serial-over-LAN, and two more
+PDU vendors.
+
+### Added — PiKVM adapter
+
+- `bmc_adapters.pikvm.PiKVMClient` — async client for PiKVM's
+  `kvmd` ATX endpoint (`/api/atx`, `/api/atx/power?action=...`).
+  Friendly verbs `on / off / off_hard / cycle / reboot` collapse
+  to kvmd's ATX action set.
+- Default-credential finding for the documented `admin/admin`.
+- Useful when KVM Fleet (or any orchestrator) needs to address a
+  PiKVM-managed target under the same shape as a BMC.
+
+### Added — IPMI Serial-over-LAN
+
+- `bmc_adapters.ipmi.sol_session(client)` — async context manager
+  that wraps `pyghmi.ipmi.console.Console` callbacks behind an
+  async iterator + send coroutine pair.
+- Always sends Deactivate Payload on exit (Supermicro X10 SoL
+  hang fix).
+
+### Added — PDU vendors
+
+- `bmc_adapters.pdu.TrippLitePDUClient` — Tripp Lite WEBCARDLX
+  (TRIPPLITE-PRODUCTS-MIB).
+- `bmc_adapters.pdu.CyberPowerPDUClient` — CyberPower
+  PDU15Mxxx/20Mxxx/30Mxxx (CyberPower-MIB).
+
+### Deferred from this release
+
+- JetKVM adapter — held until we have hardware to test against
+  (per the project's no-overpromising rule).
+
+## [0.4.0] — 2026-06-05
+
+Multi-protocol expansion. The library is no longer Redfish-only — it
+now covers the operator-facing surface across every relevant out-of-
+band path.
+
+### Added — IPMI
+
+- `bmc_adapters.ipmi.IPMIClient` — async wrapper around `pyghmi`
+  (Apache 2.0). Mirrors `RedfishClient` shape: `power_action`,
+  `chassis_status`, `sensors`, `fru`, `sel_entries`, `sel_clear`.
+- Secure defaults: refuses IPMI 1.5, refuses cipher suites
+  0/1/2/6/7/8/11/12, prefers cipher 17 (SHA-256) and falls back to
+  cipher 3 (SHA-1).
+- Default-credential detection — constant-time compare against a
+  documented vendor/user/password table. The library never *probes*
+  the BMC with a default cred; the check is local.
+- Vendor fingerprinting via Get Device ID Manufacturer ID (IANA
+  Enterprise number).
+- Optional dependency — install with `[ipmi]` extra.
+
+### Added — Smart PDU control
+
+- `bmc_adapters.pdu.APCPDUClient` — APC AP86xx / AP88xx / AP89xx via
+  SNMPv2c or SNMPv3 (PowerNet-MIB).
+- `bmc_adapters.pdu.EatonPDUClient` — Eaton ePDU G4 via
+  EATON-EPDU-MIB.
+- `bmc_adapters.pdu.RaritanPDUClient` — Raritan PX2 / PX3 / PX4 (and
+  rebranded Legrand PDUs) via JSON-RPC over HTTPS.
+- `bmc_adapters.pdu.vendor_from_sysobjectid()` — vendor auto-detect
+  from SNMP `sysObjectID` prefix.
+- Refuses SNMPv2c by default unless `allow_snmpv2c=True` is passed;
+  emits `PDU_SNMPV2C_PLAINTEXT` finding when accepted.
+- Default-credential warnings for APC `apc/apc`, Raritan
+  `admin/raritan`, Legrand `admin/legrand@1`.
+- Optional dependency — install with `[pdu]` extra.
+
+### Added — Wake-on-LAN
+
+- `bmc_adapters.wake_on_lan()` — async wrapper around the stdlib
+  socket sender; pure-stdlib, no dependency.
+- `bmc_adapters.wake_on_lan_sync()` — synchronous variant.
+
+### Added — Cross-protocol orchestration
+
+- `bmc_adapters.BMC` — top-level orchestrator composing Redfish +
+  IPMI + PDU adapters. Dispatches `power_action` to the first
+  adapter that supports it. Inspired by `bmclib`'s registry
+  pattern (github.com/bmc-toolbox/bmclib).
+- `bmc_adapters.BMCFinding` — structured security observations
+  emitted by adapters (cipher 0 accepted, default credentials
+  matched, Pantsdown firmware window, etc.). JSON-serialisable
+  via `.to_dict()`. Hooks into KVM Fleet's Merkle audit chain in
+  the hosted product.
+- `bmc_adapters.Feature` enum — taxonomy of operations an OOB
+  path may support (POWER_STATE, OUTLET_CONTROL, SOL, SEL_READ,
+  ...). Used by the orchestrator for feature dispatch.
+- `bmc_adapters.matches_default_credential()` — constant-time
+  detector for documented vendor/user/password defaults.
+- `bmc_adapters.pantsdown_finding()` — Pantsdown / CVE-2019-6260
+  fingerprint helper for AST2400/AST2500 BMC firmware.
+
+### Changed
+
+- README hero rewritten to reflect multi-protocol scope.
+- Package `description` updated.
+- `keywords` expanded.
+
+### Migration notes
+
+All v0.3.0 APIs (`RedfishClient` and friends) remain compatible.
+No breaking changes. The new protocol modules are independent.
+
+## [0.3.0] — 2026-06-05
+
+Maximise-within-scope pass: expand `RedfishClient` from a platform-pull
+minimum to the full operator surface a BMC adapter should reasonably
+expose. No breaking changes — all v0.1.0 APIs remain.
+
+### Added (23 methods)
+
+- **Identity + topology** — `system_info`, `chassis_health`
+- **Sensors** — `temperatures`, `fans`, `power_supplies`, `power_metrics`
+- **Inventory** — `processors`, `memory_modules`, `drives`, `volumes`,
+  `network_adapters`, `firmware_inventory`
+- **Boot** — `boot_config`, `set_next_boot`, `set_boot_order`
+- **System event log** — `sel_entries`, `clear_sel` (probes SEL,
+  iDRAC Lifecycle, and iLO IML registries in turn)
+- **BIOS / settings** — `bios_attributes`, `set_bios_attribute`
+- **Power control extras** — `force_off`, `graceful_shutdown`,
+  `graceful_restart`, `nmi`
+
+All new methods follow the existing async + vendor-quirks-handling
+pattern from v0.1.0; tests use `respx` to mock vendor responses.
+
+## [0.1.0] — 2026-06-03
+
+Initial public release. Extracted from the production KVM Fleet platform
+code (in production since 2026-Q2) under Apache 2.0.
+
+### Added
+
+- `RedfishClient` — async Redfish client with:
+  - SessionService auth + HTTP Basic-auth fallback for vendor firmware
+    that returns 204/404/405/2xx-without-token on `/SessionService/Sessions`
+  - Cached session token with auto-refresh + retry-on-401
+  - Per-client TLS-verify toggle (defaults false because of factory
+    self-signed certs)
+  - Plaintext-or-callable password source (sync + async callable)
+  - Power actions mapped from four friendly verbs (`on` / `off` /
+    `off_hard` / `cycle`) to `ComputerSystem.Reset`
+  - Virtual media insert / eject with vendor-quirks handling (pre-eject
+    busy slots, fall back to first slot when MediaTypes missing)
+- `HeartbeatSnapshot` dataclass for poll-cycle state
+- `RedfishError` for protocol-level failures
+- Test suite using `respx` to mock httpx — no live BMC required
+- CI: ruff + mypy + pytest on Python 3.11 / 3.12

kvmfleet_bmc_adapters-0.7.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 KVM Fleet
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.