Mathieu Benoit
f8bd1c30df
La colonne Odoo testait le port 8069 depuis le poste : une VM sur pont interne n'y répond jamais, elle restait « — » quel que soit l'état d'Odoo. Le test part maintenant DE L'HÔTE, glissé dans l'appel des statistiques déjà payé — aucun aller-retour de plus. Éprouvé sur une VM d'essai servant sur 8069 : 🟢, et « — » sur la voisine qui n'a rien. Deux dernières actions visaient encore la mauvaise machine. La touche « w » ouvrait une page morte : l'adresse d'un pont interne n'est pas routable d'ici, elle passe donc par un tunnel local le temps de la visite — tenu par son PID, car « pkill -f <motif> » tuait le shell qui l'avait lancé, le motif figurant dans sa propre ligne de commande. Et la SUPPRESSION appelait « virsh undefine <nom> », qui aurait effacé le domaine local homonyme : elle passe par « qm destroy <vmid> » sur l'hôte. --- EN --- The Odoo column probed port 8069 from the workstation: a VM on an internal bridge never answers there, so it stayed "—" whatever Odoo was doing. The probe now runs FROM THE HOST, folded into the stats call already paid for — no extra round trip. Proven on a test VM serving on 8069: 🟢, and "—" on the neighbour that serves nothing. Two last actions still aimed at the wrong machine. Key "w" opened a dead page: an internal-bridge address is not routable from here, so it now goes through a local tunnel for the length of the visit — held by its PID, since "pkill -f <pattern>" killed the very shell that had launched it, the pattern being in its own command line. And DELETION called "virsh undefine <name>", which would have erased the homonymous local domain: it now goes through "qm destroy <vmid>" on the host. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .. | ||
| auto_ask.py | ||
| database_manager.py | ||
| deploy_form_lib.py | ||
| deploy_form_plan.py | ||
| kdbx_manager.py | ||
| logo_ascii.txt | ||
| migration_form.py | ||
| migration_stats.py | ||
| migration_status.py | ||
| migration_status_tui.py | ||
| proxmox_deploy_form.py | ||
| proxmox_menu.py | ||
| qemu_access.py | ||
| qemu_deploy.py | ||
| qemu_deploy_form.py | ||
| qemu_hardware.py | ||
| qemu_install.py | ||
| qemu_install_monitor.py | ||
| qemu_manage.py | ||
| qemu_menu.py | ||
| README.base.md | ||
| README.fr.md | ||
| README.md | ||
| source_todo.sh | ||
| textual_setup.py | ||
| todo.json | ||
| todo.py | ||
| todo_example.json | ||
| todo_file_browser.py | ||
| todo_i18n.py | ||
| todo_prefs.py | ||
| todo_telemetry.py | ||
| todo_upgrade.py | ||
| version_manager.py | ||
TODO is an assistant robot to use ERPLibre
Execute it with ./script/todo/todo.py or make todo.
For a new project, copy todo_example.json to private/todo/todo_override.json | private/todo/todo_override_private.json and edit it.
The mail/ package is the mail client reachable from Assistant > Mail:
several IMAP/SMTP accounts, a local cache, and a Textual TUI. See
../../doc/EMAIL.md.
Where the code lives
todo.py carries the menus and the general helpers. Everything around a
single subject sits in its own file, and the whole thing is assembled by
mixins on the TODO class — one file, one subject, its header states its
boundary.
| File | What it owns |
|---|---|
todo.py |
the menus, the configuration, the general helpers |
qemu_menu.py |
the QEMU/KVM menu, the image catalogue, the statistics |
qemu_deploy.py |
deciding then running a deployment |
qemu_install.py |
the recipes run inside a VM |
qemu_manage.py |
lifecycle, disks, hardware, cleanup, addresses |
qemu_access.py |
SSH, tunnels, consoles, Android emulator |
proxmox_menu.py |
the same, on a REMOTE Proxmox VE host |
The two deployment forms — libvirt here, Proxmox over there — ask the same questions, so they share a foundation rather than each holding a copy:
| File | What it owns |
|---|---|
deploy_form_lib.py |
pure logic (sizes, plan, totals, spec), the shared CSS, the resource-row factory, the progress view |
deploy_form_plan.py |
the plan's gestures: overrides, locks, copies, renaming, free values |
qemu_deploy_form.py |
what QEMU/KVM adds: desktops, tools, branches, install profiles |
proxmox_deploy_form.py |
what Proxmox adds: host, storage, bridge, VMID, address |
A form inherits PlanMixin and provides three hooks: which presets each
resource offers, the name a VM would fall back to, and what a lock freezes.
test_todo_deploy_form_lib.py fails if a form redefines a gesture the
foundation already carries — that is what keeps the architecture from drifting
back into two copies.