Ciao everyone,
as a passionate proxmox user, I’m starting to draft a new OSIRIS JSON Producer for Proxmox VE and I would like to build it openly with this community.
I wrote OSIRIS as a vendor-neutral specification designed to describe infrastructure resources and their relationships in a consistent way, without depending on SaaS middleware, external AI agents, MCP layers, or third-party services.
I already experimented building producers for Cisco, AWS and Azure to demonstrate that the specification works and can be applied to real infrastructure scenarios from hyperscalers to on-premise and now I would like to bring Proxmox VE into the ecosystem as the first hypervisor platform.
The goal is simple: run the producer manually or as a scheduled job, and get a point-in-time snapshot of your Proxmox VE infrastructure in the OSIRIS specification format.
That snapshot, or a series of snapshots over time, could then be used to create automatically high quality documentation, topology diagrams in draw.io or Mermaid, audits, identify configuration drift analysis, feed CMDB/IPAM/DCIM workflows, or other internal use cases.
This is not intended to be a SaaS middleware, a control plane, an AI agent or an MCP layer. It would simply be an external Proxmox VE client that reads from Proxmox VE and emits an OSIRIS JSON document in a defined format.
I’m especially interested initially in feedback on how to map Proxmox VE objects such as clusters, nodes, vms, containers, storage pools, ha resources, network stack, firewall stack.
You can have a look at the specification that include examples and the producers.
I would really appreciate your thoughts and feedback on this idea.
Ciao from Italy
Tia and my dog Tyson
as a passionate proxmox user, I’m starting to draft a new OSIRIS JSON Producer for Proxmox VE and I would like to build it openly with this community.
I wrote OSIRIS as a vendor-neutral specification designed to describe infrastructure resources and their relationships in a consistent way, without depending on SaaS middleware, external AI agents, MCP layers, or third-party services.
I already experimented building producers for Cisco, AWS and Azure to demonstrate that the specification works and can be applied to real infrastructure scenarios from hyperscalers to on-premise and now I would like to bring Proxmox VE into the ecosystem as the first hypervisor platform.
The goal is simple: run the producer manually or as a scheduled job, and get a point-in-time snapshot of your Proxmox VE infrastructure in the OSIRIS specification format.
That snapshot, or a series of snapshots over time, could then be used to create automatically high quality documentation, topology diagrams in draw.io or Mermaid, audits, identify configuration drift analysis, feed CMDB/IPAM/DCIM workflows, or other internal use cases.
This is not intended to be a SaaS middleware, a control plane, an AI agent or an MCP layer. It would simply be an external Proxmox VE client that reads from Proxmox VE and emits an OSIRIS JSON document in a defined format.
I’m especially interested initially in feedback on how to map Proxmox VE objects such as clusters, nodes, vms, containers, storage pools, ha resources, network stack, firewall stack.
You can have a look at the specification that include examples and the producers.
I would really appreciate your thoughts and feedback on this idea.
Ciao from Italy
Tia and my dog Tyson