Current Series Release Notes¶
17.0.0.0rc1-4¶
Upgrade Notes¶
The
cyborg-apiconsole script and the eventlet-based standalone API server have been removed. Deploy the Cyborg API with a standard WSGI server using thecyborg.wsgi.api:applicationmodule.The standalone-server
[api]optionshost_ip,port,api_workers, andenable_ssl_apihave also been removed. The obsolete, unmaintained Ansible deployment playbook undersetup/is no longer provided.
17.0.0.0rc1¶
Prelude¶
The 2026.2 release addresses two access-control vulnerabilities, CVE-2026-40213 and CVE-2026-40214, strengthening security, tenant isolation, and operational control for accelerator resources. Accelerator requests are now scoped to their owning projects. Operations on accelerator requests bound to instances require service-token validation, and access to hardware management APIs has been tightened.
The release also introduces opt-in persona-based policy defaults for the
reader, member, manager, service, and admin roles.
This aligns Cyborg with the OpenStack Consistent and Secure Default RBAC
community goal and provides operators with a migration path before the
new defaults are planned to become the default in 2027.1.
Operators also gain safer upgrade tooling for accelerator request ownership and device state, along with finer-grained control over which Intel SR-IOV NIC devices Cyborg manages. Standards-compliant API microversion handling has been restored for compatibility with OpenStack clients.
Testing and documentation were also major focuses of this release, improving release confidence and making Cyborg easier to deploy, upgrade, and use. As part of this work, the generic PCI driver has returned to fully supported status. The project also continued to pay down technical debt and improve code quality, strengthening long-term maintainability and reliability.