Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-26368

CLI tool for automated, coordinated patching across multiple OpenStack's repositories at once with Gerrit integration

XMLWordPrintable

    • Create an Industrialized Multi-Repository Patch Management Tool for OpenStack (changes-roller)
    • Initiative Tracking
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • ?
    • ?
    • In Progress
    • ?
    • rhos-ops-platform-services-pidone
    • ?
    • 14% To Do, 0% In Progress, 86% Done

      GitHub Link

      Goal:

      Under hberaud's mentorship, develop changes-roller to enable OpenStack developers to coordinate patch series across 50+ repositories in under 1 hour instead of 2-3 days of manual work. The tool automates Git operations, integrates with OpenStack's Gerrit workflow, and becomes the standard approach for applying consistent changes across the OpenStack ecosystem.

      Acceptance Criteria:

      Value Proposition: Enable coordinated multi-repository changes with zero manual Git operations, full Gerrit integration, and automated testing.

      Required Outcomes:

      1. Production-Ready CLI Tool
        • Functional CLI with multi-repository processing and Gerrit integration
        • Comprehensive test coverage (>90%) and code quality enforcement
        • Complete documentation (README, SPECIFICATION, USAGE, examples)
      2. Professional Infrastructure
        • Automated quality gates (pre-commit hooks, CI/CD pipeline)
        • Community standards (CONTRIBUTING, CHANGELOG, CODE_OF_CONDUCT, SECURITY)
        • Complete PyPI metadata and GitHub templates
      3. Distribution and Documentation
        • Professional documentation site with OpenStack integration guide
        • Automated PyPI publishing via OIDC
        • Package installable via `pip install changes-roller`
      4. OpenStack Ecosystem Validation
        • Investigation of code quality tool adoption patterns
        • Demonstration of industrial-scale standardization rollout

      Success Metrics:

      • Patches 50+ repositories in under 5 minutes
      • Zero manual Git operations required
      • Community adoption as standard OpenStack workflow tool

      Open questions:

      1. Why was flake8 removed from OpenStack pre-commit hooks and what prevents its restoration?
        • Investigation required to understand the reason for the removal
        • Determines whether Ruff/flake8 standardization is viable across OpenStack
        • Resolution needed before proposing code quality standardization 

              rh-ee-pkostian Pavlo Kostianov
              hberaud Hervé Beraud
              Hervé Beraud, Pavlo Kostianov
              rhos-dfg-pidone
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: