Developer

Ciao everyone,
I'm starting to draft a new OSIRIS JSON Producer development using Aruba Central as the first point of reference and I would like to build it openly within the community.

I wrote OSIRIS JSON 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 by building producers for Cisco, AWS, and Azure to demonstrate that the specification can be applied to real infrastructure scenarios, from hyperscalers to on-premise environments and now I would like to bring HPE Aruba Networking into the on-premise network ecosystem.

The goal is simple, run the OSIRIS JSON producer manually or as a scheduled job and get a point-in-time portable snapshot of the aruba networking infrastructure in OSIRIS JSON format.
That snapshot, or a series of snapshots over time, could then be used to create vendor-neutral high-quality architectural or operational documentation, generate topology diagrams in draw.io or mermaid, support audits, identify configuration drift, feed AI platforms or agents in a controlled way without exposing direct access, feed CMDB/IPAM/DCIM workflows, or serve other use cases.

This is not intended to replace aruba central or management tools, or any existing control plane. OSIRIS JSON infact is not a SaaS middleware, a control plane, an AI agent, or an MCP layer, it would simply be an external client that reads from Aruba Central or direct device access and emits an OSIRIS JSON vendor-neutral document following the defined specification format.

I would really appreciate your thoughts and feedback on the idea of bringing a vendor-neutral open specification to aruba networking environments, with the goal of clearly seeing infrastructure end-to-end from the network layer to the application layer.

Ciao from Italy,
Tia and my dog Tyson