netbox-bmc 0.4.0__tar.gz

netbox_bmc-0.4.0/LICENSE

@@ -0,0 +1,182 @@
+                                 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 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, as submitted to the 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 Legal Entity on behalf of
+      whom a Contribution has been received by the 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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Contribution, either by you alone or on behalf of the Licensor.
+
+   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 reasonable and customary use in 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 reproducing 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 exemplary 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 all other
+      commercial damages or losses), even if such Contributor has been
+      advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. 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 additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2024 tak-labo
+
+   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.

netbox_bmc-0.4.0/NOTICE

@@ -0,0 +1,4 @@
+netbox-bmc
+Copyright 2024 tak-labo
+
+This product is licensed under the Apache License, Version 2.0.

netbox_bmc-0.4.0/PKG-INFO

@@ -0,0 +1,230 @@
+Metadata-Version: 2.4
+Name: netbox-bmc
+Version: 0.4.0
+Summary: Unified out-of-band management for NetBox: Redfish & IPMI inventory sync, power control, console access
+Author: tak-labo
+License: Apache-2.0
+Project-URL: Documentation, https://github.com/tak-labo/netbox-bmc/blob/main/README.md
+Project-URL: Source, https://github.com/tak-labo/netbox-bmc
+Project-URL: Tracker, https://github.com/tak-labo/netbox-bmc/issues
+Keywords: netbox,netbox-plugin
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.12.0
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: requests>=2.31
+Requires-Dist: pyghmi>=1.5
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-mock>=3.14; extra == "dev"
+Requires-Dist: ruff>=0.4; extra == "dev"
+Dynamic: license-file
+
+# netbox-bmc
+
+[![NetBox](https://img.shields.io/badge/NetBox-4.5%20|%204.6-blue)](https://github.com/netbox-community/netbox)
+[![Python](https://img.shields.io/badge/Python-3.10%2B-blue)](https://www.python.org/)
+[![License](https://img.shields.io/badge/License-Apache%202.0-green)](LICENSE)
+
+[日本語](README_ja.md)
+
+Unified out-of-band management plugin for NetBox.  
+Inventory sync and power control via Redfish & IPMI.
+
+## Supported Protocols / Vendors
+
+| Protocol | Vendors |
+|---|---|
+| Redfish | Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro, Generic |
+| IPMI | Fallback for any IPMI-capable BMC |
+
+Protocol is auto-detected: probes `/redfish/v1` first, falls back to IPMI on failure.
+
+## Tested Hardware
+
+| Manufacturer | Model Series | BMC | Protocol | Status |
+|---|---|---|---|---|
+| Dell | PowerEdge | iDRAC 9 | Redfish | Expected to work |
+| HPE | ProLiant | iLO 5 | Redfish | Expected to work |
+| HPE | ProLiant | iLO 6 | Redfish | Expected to work |
+| Lenovo | ThinkSystem | XCC2 / XCC3 | Redfish | Expected to work |
+| Supermicro | X12 / X13 | BMC | Redfish | Expected to work |
+| Generic | — | Any IPMI-capable BMC | IPMI | Expected to work (fallback) |
+
+## Features
+
+- **Module Builder**: Sync BMC hardware inventory to NetBox Modules
+  - Scan via Redfish → preview detected components with diff badges (new / updated / unchanged / removed)
+  - Select individual components before applying
+  - Auto-create ModuleBays when missing (warned in preview)
+  - Detect serial number changes after FRU replacement and apply diff updates
+  - Only manages `bmc-synced`-tagged Modules; never touches manually created Modules
+- **Collected components**: CPU, Memory, Drive, PSU, Fan, Firmware, PCI devices
+  - PSU and Fan collected via Chassis link; PCIe via PCIeDevices collection
+- **Vendor auto-detection**: Dispatches to Dell / HPE / Lenovo subclass drivers based on ServiceRoot `Vendor` / `Oem` keys
+- **Power control**: on / off / soft / cycle / reset (both protocols)
+
+## Install
+
+### Standard (non-Docker)
+
+```bash
+pip install netbox-bmc
+```
+
+Add to `configuration.py`:
+
+```python
+PLUGINS = ["netbox_bmc"]
+PLUGINS_CONFIG = {
+    "netbox_bmc": {
+        "sync_interval_minutes": 0,
+        "default_verify_ssl": False,
+    },
+}
+```
+
+Run migrations:
+
+```bash
+python manage.py migrate
+```
+
+### Docker (netbox-docker)
+
+Add a volume mount in `docker-compose.override.yml`:
+
+```yaml
+services:
+  netbox: &netbox
+    volumes:
+      - ./netbox-bmc:/opt/netbox-bmc
+```
+
+Install in editable mode and restart:
+
+```bash
+docker compose exec netbox pip install -e /opt/netbox-bmc
+docker compose exec netbox python manage.py migrate
+docker compose restart netbox netbox-worker
+```
+
+## Configure
+
+Edit `PLUGINS_CONFIG["netbox_bmc"]` in `configuration.py`:
+
+| Key | Default | Description |
+|---|---|---|
+| `sync_interval_minutes` | `0` | Scheduled bulk sync interval in minutes. `0` disables. |
+| `default_verify_ssl` | `False` | Default SSL verification for new BMC Endpoints. |
+| `service_account` | — | Service account name for background jobs (netbox-secrets). |
+| `service_private_key_path` | — | Path to private key for service account (netbox-secrets). |
+
+## Use
+
+1. Open a Device in NetBox and click **BMC Endpoints** → **Add**
+2. Enter the BMC address and credentials, then save
+3. On the Endpoint detail page, click **[Build Modules]**
+4. Review the component preview (new / updated / unchanged / removed)
+5. Check the components to sync and click **[Apply Selected]**
+
+ModuleBays, ModuleTypes, and Modules are created or updated automatically.
+
+### Module Naming
+
+Vendor-specific names are normalized to a consistent format:
+
+| Raw name (Redfish) | Normalized |
+|---|---|
+| `CPU.Socket.1` / `Processor 0` | `CPU 0` |
+| `DIMM.A1` / `Memory 0` | `Memory 0` |
+| `Disk.Bay.0` | `Drive 0` |
+| `NIC.Slot.1` (PCIe) | `PCI 0` |
+
+### Custom Fields
+
+The following custom fields are set automatically on each Module:
+
+| Field | Content |
+|---|---|
+| `bmc_redfish_path` | Source Redfish URI |
+| `bmc_firmware_version` | Firmware version string |
+
+## Versions
+
+| netbox-bmc | NetBox |
+|---|---|
+| 0.4.x | 4.5, 4.6 |
+
+## Vendor Notes
+
+### Dell iDRAC
+
+iDRAC 9 (Redfish 1.x) is the primary target. URI traversal starts from `ServiceRoot` links — no hardcoded paths — so firmware variations should be absorbed automatically.
+
+### HPE iLO
+
+iLO 5 and iLO 6 are supported via the HPE subclass driver. iLO 4 (Redfish 1.0 partial compliance) is **not tested** and may not work correctly.
+
+### Lenovo XCC
+
+XCC2 and XCC3 are supported. Some older XCC firmware versions expose non-standard collection URIs; the link-traversal approach handles most variations.
+
+### Supermicro
+
+Generic Redfish driver is used. Supermicro BMC firmware varies significantly; behaviour may differ across firmware versions.
+
+## Development
+
+```bash
+# Install dev dependencies
+uv sync --extra dev
+
+# Run tests
+uv run pytest
+```
+
+### Adding a New Vendor
+
+1. Add a subclass in `netbox_bmc/drivers/redfish.py` extending `RedfishDriver`
+2. Register it in `detect_and_build()` in `netbox_bmc/drivers/base.py` by matching `ServiceRoot` vendor keys
+3. Add unit tests in `tests/test_redfish_extensions.py`
+
+### Adding a New Protocol
+
+Implement `BaseDriver` (`netbox_bmc/drivers/base.py`) and return `InventoryResult` from `get_inventory()`.
+
+## Credentials
+
+netbox-bmc resolves BMC credentials in the following order:
+
+1. **netbox-secrets** (preferred) — `Secret` with role `bmc-credentials` assigned to the Device.  
+   `Secret.name` = BMC username, `Secret.plaintext` = BMC password (RSA-encrypted).
+2. **Plaintext fallback** — `username` / `password` fields on `BMCEndpoint`, used when netbox-secrets is not installed or no matching secret is found.
+
+For background jobs (scheduled sync), set `service_account` and `service_private_key_path` in `PLUGINS_CONFIG` so the job can decrypt secrets without an HTTP session.
+
+## Known Limitations
+
+- REST API (serializers / viewsets) not yet implemented
+- Multi-node chassis (multiple `Systems`) not supported
+- Scheduled bulk sync (`ScheduledInventorySyncJob`) not yet implemented
+- KVM / SOL console not yet ported from the predecessor plugin
+- Old BMCs with low Redfish compliance (e.g. HPE iLO 4) not validated
+
+## License
+
+Apache License 2.0 — see [LICENSE](LICENSE).

netbox_bmc-0.4.0/README.md

@@ -0,0 +1,195 @@
+# netbox-bmc
+
+[![NetBox](https://img.shields.io/badge/NetBox-4.5%20|%204.6-blue)](https://github.com/netbox-community/netbox)
+[![Python](https://img.shields.io/badge/Python-3.10%2B-blue)](https://www.python.org/)
+[![License](https://img.shields.io/badge/License-Apache%202.0-green)](LICENSE)
+
+[日本語](README_ja.md)
+
+Unified out-of-band management plugin for NetBox.  
+Inventory sync and power control via Redfish & IPMI.
+
+## Supported Protocols / Vendors
+
+| Protocol | Vendors |
+|---|---|
+| Redfish | Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro, Generic |
+| IPMI | Fallback for any IPMI-capable BMC |
+
+Protocol is auto-detected: probes `/redfish/v1` first, falls back to IPMI on failure.
+
+## Tested Hardware
+
+| Manufacturer | Model Series | BMC | Protocol | Status |
+|---|---|---|---|---|
+| Dell | PowerEdge | iDRAC 9 | Redfish | Expected to work |
+| HPE | ProLiant | iLO 5 | Redfish | Expected to work |
+| HPE | ProLiant | iLO 6 | Redfish | Expected to work |
+| Lenovo | ThinkSystem | XCC2 / XCC3 | Redfish | Expected to work |
+| Supermicro | X12 / X13 | BMC | Redfish | Expected to work |
+| Generic | — | Any IPMI-capable BMC | IPMI | Expected to work (fallback) |
+
+## Features
+
+- **Module Builder**: Sync BMC hardware inventory to NetBox Modules
+  - Scan via Redfish → preview detected components with diff badges (new / updated / unchanged / removed)
+  - Select individual components before applying
+  - Auto-create ModuleBays when missing (warned in preview)
+  - Detect serial number changes after FRU replacement and apply diff updates
+  - Only manages `bmc-synced`-tagged Modules; never touches manually created Modules
+- **Collected components**: CPU, Memory, Drive, PSU, Fan, Firmware, PCI devices
+  - PSU and Fan collected via Chassis link; PCIe via PCIeDevices collection
+- **Vendor auto-detection**: Dispatches to Dell / HPE / Lenovo subclass drivers based on ServiceRoot `Vendor` / `Oem` keys
+- **Power control**: on / off / soft / cycle / reset (both protocols)
+
+## Install
+
+### Standard (non-Docker)
+
+```bash
+pip install netbox-bmc
+```
+
+Add to `configuration.py`:
+
+```python
+PLUGINS = ["netbox_bmc"]
+PLUGINS_CONFIG = {
+    "netbox_bmc": {
+        "sync_interval_minutes": 0,
+        "default_verify_ssl": False,
+    },
+}
+```
+
+Run migrations:
+
+```bash
+python manage.py migrate
+```
+
+### Docker (netbox-docker)
+
+Add a volume mount in `docker-compose.override.yml`:
+
+```yaml
+services:
+  netbox: &netbox
+    volumes:
+      - ./netbox-bmc:/opt/netbox-bmc
+```
+
+Install in editable mode and restart:
+
+```bash
+docker compose exec netbox pip install -e /opt/netbox-bmc
+docker compose exec netbox python manage.py migrate
+docker compose restart netbox netbox-worker
+```
+
+## Configure
+
+Edit `PLUGINS_CONFIG["netbox_bmc"]` in `configuration.py`:
+
+| Key | Default | Description |
+|---|---|---|
+| `sync_interval_minutes` | `0` | Scheduled bulk sync interval in minutes. `0` disables. |
+| `default_verify_ssl` | `False` | Default SSL verification for new BMC Endpoints. |
+| `service_account` | — | Service account name for background jobs (netbox-secrets). |
+| `service_private_key_path` | — | Path to private key for service account (netbox-secrets). |
+
+## Use
+
+1. Open a Device in NetBox and click **BMC Endpoints** → **Add**
+2. Enter the BMC address and credentials, then save
+3. On the Endpoint detail page, click **[Build Modules]**
+4. Review the component preview (new / updated / unchanged / removed)
+5. Check the components to sync and click **[Apply Selected]**
+
+ModuleBays, ModuleTypes, and Modules are created or updated automatically.
+
+### Module Naming
+
+Vendor-specific names are normalized to a consistent format:
+
+| Raw name (Redfish) | Normalized |
+|---|---|
+| `CPU.Socket.1` / `Processor 0` | `CPU 0` |
+| `DIMM.A1` / `Memory 0` | `Memory 0` |
+| `Disk.Bay.0` | `Drive 0` |
+| `NIC.Slot.1` (PCIe) | `PCI 0` |
+
+### Custom Fields
+
+The following custom fields are set automatically on each Module:
+
+| Field | Content |
+|---|---|
+| `bmc_redfish_path` | Source Redfish URI |
+| `bmc_firmware_version` | Firmware version string |
+
+## Versions
+
+| netbox-bmc | NetBox |
+|---|---|
+| 0.4.x | 4.5, 4.6 |
+
+## Vendor Notes
+
+### Dell iDRAC
+
+iDRAC 9 (Redfish 1.x) is the primary target. URI traversal starts from `ServiceRoot` links — no hardcoded paths — so firmware variations should be absorbed automatically.
+
+### HPE iLO
+
+iLO 5 and iLO 6 are supported via the HPE subclass driver. iLO 4 (Redfish 1.0 partial compliance) is **not tested** and may not work correctly.
+
+### Lenovo XCC
+
+XCC2 and XCC3 are supported. Some older XCC firmware versions expose non-standard collection URIs; the link-traversal approach handles most variations.
+
+### Supermicro
+
+Generic Redfish driver is used. Supermicro BMC firmware varies significantly; behaviour may differ across firmware versions.
+
+## Development
+
+```bash
+# Install dev dependencies
+uv sync --extra dev
+
+# Run tests
+uv run pytest
+```
+
+### Adding a New Vendor
+
+1. Add a subclass in `netbox_bmc/drivers/redfish.py` extending `RedfishDriver`
+2. Register it in `detect_and_build()` in `netbox_bmc/drivers/base.py` by matching `ServiceRoot` vendor keys
+3. Add unit tests in `tests/test_redfish_extensions.py`
+
+### Adding a New Protocol
+
+Implement `BaseDriver` (`netbox_bmc/drivers/base.py`) and return `InventoryResult` from `get_inventory()`.
+
+## Credentials
+
+netbox-bmc resolves BMC credentials in the following order:
+
+1. **netbox-secrets** (preferred) — `Secret` with role `bmc-credentials` assigned to the Device.  
+   `Secret.name` = BMC username, `Secret.plaintext` = BMC password (RSA-encrypted).
+2. **Plaintext fallback** — `username` / `password` fields on `BMCEndpoint`, used when netbox-secrets is not installed or no matching secret is found.
+
+For background jobs (scheduled sync), set `service_account` and `service_private_key_path` in `PLUGINS_CONFIG` so the job can decrypt secrets without an HTTP session.
+
+## Known Limitations
+
+- REST API (serializers / viewsets) not yet implemented
+- Multi-node chassis (multiple `Systems`) not supported
+- Scheduled bulk sync (`ScheduledInventorySyncJob`) not yet implemented
+- KVM / SOL console not yet ported from the predecessor plugin
+- Old BMCs with low Redfish compliance (e.g. HPE iLO 4) not validated
+
+## License
+
+Apache License 2.0 — see [LICENSE](LICENSE).

netbox_bmc-0.4.0/netbox_bmc/__init__.py

@@ -0,0 +1,78 @@
+from netbox.plugins import PluginConfig
+
+__version__ = "0.4.0"
+__author__ = "tak-labo"
+__email__ = ""
+
+
+class NetBoxBMCConfig(PluginConfig):
+    name = "netbox_bmc"
+    verbose_name = "NetBox BMC (IPMI/Redfish)"
+    description = "Unified out-of-band management: Redfish & IPMI inventory sync, power control, console access"
+    version = __version__
+    author = __author__
+    author_email = __email__
+    base_url = "bmc"
+    min_version = "4.5"
+    max_version = "4.6.99"
+    default_settings = {
+        # 定期一括同期の間隔 (分)。0 で無効。
+        "sync_interval_minutes": 0,
+        "default_verify_ssl": False,
+        # netbox-secrets バックグラウンドジョブ用サービスアカウント設定
+        # (netbox-secrets 使用時のみ必要)
+        # "service_account": "bmc-sync",
+        # "service_private_key_path": "/opt/netbox/bmc-sync.pem",
+    }
+
+    def ready(self):
+        super().ready()
+        from . import jobs  # noqa: F401
+
+        interval = (getattr(self, "settings", None) or {}).get("sync_interval_minutes") or 0
+        if interval:
+            self._enqueue_scheduled_sync(interval)
+
+    @staticmethod
+    def _enqueue_scheduled_sync(interval_minutes: int) -> None:
+        """
+        ScheduledInventorySyncJob の定期ジョブを登録する。
+
+        ready() は workers / web プロセスの起動ごとに呼ばれるため、
+        既に pending / scheduled / running の同名ジョブがあればスキップして
+        冪等にする。初回マイグレーション前など Job テーブル未作成の場合は黙って抜ける。
+        """
+        import logging
+
+        from django.db import DatabaseError
+
+        from .jobs import ScheduledInventorySyncJob
+
+        logger = logging.getLogger("netbox_bmc")
+
+        try:
+            from datetime import timedelta
+
+            from core.models import Job
+            from django.utils import timezone
+
+            active = Job.objects.filter(
+                name=ScheduledInventorySyncJob.Meta.name,
+                status__in=("pending", "scheduled", "running"),
+            ).exists()
+            if active:
+                return
+
+            ScheduledInventorySyncJob.enqueue(
+                instance=None,
+                schedule_at=timezone.now() + timedelta(minutes=interval_minutes),
+                interval=interval_minutes,
+            )
+        except DatabaseError:
+            # マイグレーション前: Job テーブルが存在しない
+            pass
+        except Exception as e:
+            logger.warning("Failed to schedule recurring inventory sync: %s", e)
+
+
+config = NetBoxBMCConfig