[horizon][ptg] Horizon 2027.1 Indri PTG Summary
Hi all, The Horizon team met virtually during the October 2026 PTG to reflect on the Hibiscus cycle accomplishments and chart priorities for the 2027.1 Indri release cycle. The detailed summary can be found here: https://etherpad.opendev.org/p/oct2026-ptg-horizon --- *Hibiscus Retrospective* We kicked off with a review of our accomplishments over the past cycle: * Deangularization Progress: - Key Pairs Panel: Switched over to the Python/Django implementation by default. - Images Table (Python): Gained search filters and activate/deactivate actions; significant progress on the new image metadata form. - Trove Dashboard: Complete removal of AngularJS (ready for review for 2027.1). - Barbican UI: Porting effort actively underway ( https://review.opendev.org/q/topic:%22port_to_horizon_2026.1%22). * OpenStackSDK Migration: - Removed the final remaining direct neutronclient calls. - Nova interactions (Flavors, Key Pairs, Availability Zones, Services) now fetch through OpenStackSDK. * Python & Django Toolchain Modernization: - Added support for Python 3.14 (voting job); dropped Python 3.9 and 3.10. - Voting job added for Django 5.2, non-voting job for Django 6.0, and the rigid Django constraint was removed from requirements.txt. - Removed Enmerkar translation dependency; message extraction logic now lives directly in Horizon. - Packaging modernized: setup and coverage configuration migrated to pyproject.toml, and linters run via pre-commit. * Retrospective Takeaway: While toolchain modernization and Python/Django updates are strong, Deangularization speed remains our major bottleneck and MUST be our highest priority going into Indri. --- *Horizon Deangularization Strategy* Goal: Eliminate unsupported AngularJS 1.8.2 dependencies completely due to ongoing security, compatibility, and maintenance risks. * Panel Transition Status & Next Steps: - Key Pairs: Complete (default Django/Python). - Images Panel: Partial. Currently working on Enum/Multiselect fields in image metadata (#1007928) and editable Kernel/Ramdisk fields (#1000331). - Next Up: Roles (revisit legacy Python implementation), Backups (align existing Python implementation with Angular parity), and Security Groups (Python panel exists, but Launch Instance workflow still invokes Angular). - Heavy Rewrites Ahead: Containers, Network QoS, Server Groups, Trunks, Launch Instance, and the Login Form. - Challenge Area: Network Topology. (If Network Topology ends up being the last remaining Angular component, we may consider disabling/hiding it when no Angular stack is loaded). * Action Items & New Contributor Opportunities: - Low-hanging fruit: Refactoring Chevrons and Metadata forms into reusable Python components. - Track all progress via the Launchpad Blueprint: https://blueprints.launchpad.net/horizon/+spec/removing-angularjs --- *XStatic Dependencies & Governance (PTI)* We evaluated the OpenStack Governance Project Template Interface (PTI) requirement insisting on minimal pyproject.toml layouts across repos: * Current State: - Horizon owns 31 `xstatic-*` repos. None currently use pyproject.toml or PBR (they stick to upstream XStatic conventions). - Bumping horizon/pyproject.toml to pbr>=6.1.1 is required (and will follow for plugins). - XStatic lower bounds in requirements.txt need raising to Feb 2026 native-namespace releases. * Future Architecture Consideration (NPM vs XStatic): - Discussed adopting an architectural approach similar to Skyline Console (building via yarn/webpack and shipping prebuilt static asset wheels). - Moving to "NPM as source, PyPI as delivery" via CI could replace hand-maintaining 31 individual XStatic repos down the road. - Decision: Postpone major XStatic shifts to discuss with the TC, keeping Deangularization as the top focus for Indri. Apply a minimal 4-line [build-system] block to XStatic repos if strict compliance is mandated. --- *Community & User Group Updates* Abby Nduta presented updates from the OpenInfra User Group Kenya. It was great to hear about the local community's growth, ongoing activities, and efforts to engage new regional contributors with OpenStack and OpenInfra projects. Building strong pipelines with regional user groups remains a key avenue for onboarding new talent and expanding ecosystem adoption. --- *Review Throughput & Contributor Policy on AI-Generated Content* We spent time discussing our review queue health and how to better handle patches that have stalled without reviews. * Review Backlog Actions: - Discussed implementing cutoffs or team review targets during weekly meetings to avoid letting contributor patches sit unreviewed. * AI-Generated Code Policy: - Unfiltered or unverified AI-generated patches place a heavy review burden on maintainers. - Decision: Create an explicit AI Contributor Guide section in Horizon docs (aligned with Kolla and Zuul policies): https://docs.openstack.org/horizon/latest/contributor/contributing.html - Outline clear expectations on review prioritization and author responsibilities when using AI assistants. --- *Indri (2027.1) Priority Summary* 1. Top Priority: Horizon & Plugin Deangularization. 2. MFA Enrollment: Merge Horizon panel for TOTP MFA enrollment ( https://review.opendev.org/c/openstack/horizon/+/977939). 3. OpenStackSDK: Complete transition of remaining Nova interactions. 4. Governance & UI Alignment: Engage with the TC and neighboring teams regarding OpenStack frontend architecture strategy and plugin support. Thanks to everyone who attended and contributed to the sessions! Best regards, Tatiana Ovchinnikova (tmazur) OpenStack Horizon PTL
participants (1)
-
Tatiana Ovchinnikova