MTUI

The Maintenance Test Update Installer (MTUI) allows you to run shell commands on multiple hosts in parallel.

In addition, MTUI provides convenience commands to help with maintenance update testing and integrating with other systems like Bugzilla and test report templates.

Features

• Parallel SSH command execution across SUSE reference hosts (run, prepare, update, install, uninstall, downgrade, reboot, …) with per-host enabled / disabled / dryrun states and parallel / serial execution modes.
• OBS / IBS maintenance-request workflow: assign, unassign, approve, reject, comment, dispatched to the native OBS/IBS API for SUSE:Maintenance and Product Increment requests (no osc subprocess; credentials and the SSH signing key are read from the user's oscrc, discovered like osc via $OSC_CONFIG, $XDG_CONFIG_HOME/osc/oscrc, then ~/.oscrc) or to Gitea for SLFO / SL-Micro requests. approve -r REVIEWER records the reviewer in the testreport and commits to SVN in one step.
• Update-queue and template workflow: updates lists the actionable pickup queue (unassigned updates in testing) from the TeReGen API sorted by priority, checkers shows the build-check result runs for the loaded update, and regenerate rebuilds a loaded update's test-report template via TeReGen and reloads it in place.
• Multiple templates in one session: load_template adds each RRID to the session, list_templates / switch / unload manage the loaded set, and action commands fan out across every loaded template by default (scope a single one with -T RRID or force fan-out with --all-templates). Fan-out arbitrates a distinct free reference host per test-target slot from the shared pool so templates never collide on a host.
• openQA integration: reload_openqa, set_workflow {auto,manual,kernel}, openqa_overview (port of oqa-search) which prints PASSED/FAILED/RUNNING per SLE version, aggregated-update builds, and parsed build-check summaries (with --export to inject the block into the testreport's regression tests: section), and openqa_jobs which lists the individual openQA jobs for the incident build so you can see which scenarios passed or failed.
• Reference-host lock management: cooperative lock files, automatic locking of every connected host while a Product Increment is under test ([lock] pi_autolock), automatic reaping of stale locks left over from crashed sessions ([lock] reap_stale, [lock] stale_age), and independent host-pool claims (list_locks -p, unlock -p) that queue politely on an exhausted pool ([lock] wait, [lock] wait_poll).
• Test-report lifecycle: load_template, checkout, commit, edit, export, with SVN and Gitea checkout backends.
• Reference-host discovery: HTTPS- or filesystem-resolved refhosts.yml with a single merged host pool and configurable cache expiry, plus offline inventory search (list_refhosts) that filters the fleet by hostname glob, arch, product, version, addon, or testplatform query (and optionally probes live lock state) without connecting, locking, or loading a template.
• File transfer: put (glob upload to all hosts, preserving directory trees) and get (download with per-host filename suffix or recursive folder mode).
• Interactive prompt_toolkit-based shell: tab completion over the live command registry, persistent history with reverse-search (Ctrl-R), autosuggest-from-history (right-arrow to accept), lexer-highlighted command tokens, a bottom toolbar showing the loaded-template count and the active RRID, per-command --help, configurable log level, optional desktop notifications (notify extra), and OS-keyring credential storage (keyring extra).
• Shell-completion script via the completion extra (register-python-argcomplete mtui).
• MCP server (mtui-mcp, optional mcp extra): exposes every non-interactive mtui command as a Model Context Protocol tool, plus dedicated testreport_read / testreport_patch / testreport_write tools, so LLM clients can drive a headless mtui session over stdio or http. The HTTP transport isolates state per client, slow host commands can run as backgrounded jobs (job_list / job_status / job_result / job_cancel), and the exposed tool surface is tunable through the [mcp] config section.

License

This project is licensed under the GPLv2 license, see the COPYING file for details.

Contents

• Installation
• User Guide
• Developer Guide
• Support
• FAQ

Authors

MTUI was originally written by:

• Christian Kornacker
• Heiko Rommel rommel@suse.de
• Jan Matějka
• Roman Neuhauser
• David Santiago

The project is currently maintained mainly by:

• Ondřej Súkup osukup@suse.cz
• Jan Baier jbaier@suse.cz

Besides that, numerous other contributors have committed to MTUI. Thanks everyone for their contributions!