Netris vs OpenDaylight

Netris is a network automation, abstraction, and multi-tenancy platform for AI infrastructure operators, including neoclouds, sovereign cloud operators, and AI factories. It spans Ethernet, InfiniBand, NVLink, DPUs, virtual networks, and edge networks. The Netris Controller uses algorithms to configure VRFs, VXLANs, BGP, and other settings with closed-loop assurance. It runs in the customer environment on dedicated bare-metal hosts, with a minimum of three nodes. Engineers can use a web console, REST API, or Kubernetes integration; the controller also works with Terraform and documents an NVIDIA UFM integration for InfiniBand. That plugin can automate PKey configuration and optionally create SHARP reservations for server clusters. Netris documents tenant isolation through VRFs, VXLANs, ACLs, InfiniBand PKeys, and NVLink fabric partitions. API requests, including GUI activity, are logged. If the controller is unreachable, devices continue forwarding traffic and enforcing existing policies, while new changes and telemetry pause. Pricing is on request.

OpenDaylight is a free, open-source SDN controller for centralized, programmable network control and monitoring. Its modular design uses YANG models and MD-SAL to connect applications with network hardware through northbound REST APIs and southbound plugins. Listed protocol support includes OpenFlow, NETCONF, BGP-LS, PCEP, OVSDB, LISP, and SNMP, among others. Clustering, sharded data stores, and leader-based consensus support scaling across nodes. The project describes uses in optical transport, service-provider WAN automation, data center SDN, network telemetry, enterprise network control, and ONAP. Its AAA project provides authentication, authorization, accounting, and role-based access control for northbound interfaces. OpenDaylight is self-hosted and runs on Linux, macOS, and Windows; setup requires Java 21 or later. The downloads page identifies Chromium-SR0 as the current release and lists Vanadium-SR1 and Titanium-SR3 under supported releases. Documentation, Zulip chat, mailing lists, a wiki, and weekly Technical Steering Committee meetings are listed as community resources.