Mathieu Benoit
7dc5df67c3
Un Proxmox dans un Proxmox hérite du réseau interne de son parent : la VM vivait en 10.10.10.152, passerelle 10.10.10.1. Le pont interne, lui, avait son adresse CODÉE EN DUR à 10.10.10.1/24. Lui demander de la poser sur son propre pont, c'est prendre l'adresse de sa passerelle et rendre tout le /24 local. La machine s'isole au milieu de la commande qui la configure : « ifup » n'a jamais rendu la main, la VM ne répondait plus ni en ssh ni en ping. Le réseau est donc CHOISI, d'après ce que l'hôte connaît déjà — ses adresses et ses routes, car une route sans adresse locale suffit à créer le conflit, et la route par défaut en est l'exemple exact. Le chevauchement se calcule sur les réseaux et non sur les trois premiers octets : « 10.0.0.0/8 » écarte alors bien tous les candidats en 10.x. Plus aucun libre ? On le dit, plutôt que d'en écraser un — écraser, ici, c'est couper la seule voie d'accès. Le repli « ifreload -a » s'en va aussi. Il rechargeait TOUTES les interfaces, y compris celle qui porte la session, et sur une image cloud l'interface principale est décrite ailleurs — ifupdown2 la descend sans la remonter. Le repli monte maintenant le pont à la main, sans toucher à rien d'autre ; la strophe le rend persistant. La règle de masquerading se teste avant de s'ajouter, donc une reprise n'empile rien. Le test d'origine interdisait « 2>/dev/null » sur toute la ligne pour que l'erreur d'ifup reste lisible. L'intention est gardée, portée sur l'appel à ifup seul : le repli, lui, sonde légitimement. --- EN --- Proxmox inside Proxmox inherits its parent's internal network: the VM lived at 10.10.10.152, gateway 10.10.10.1. The internal bridge had its address HARDCODED to 10.10.10.1/24. Asking it to put that on its own bridge takes its gateway's address and makes the whole /24 local. The machine isolates itself in the middle of the command configuring it: "ifup" never returned, the VM answered neither ssh nor ping. The subnet is now CHOSEN from what the host already knows — its addresses and its routes, since a route with no local address is enough to collide, and the default route is exactly that case. Overlap is computed on networks rather than on the first three octets, so "10.0.0.0/8" correctly rules out every 10.x candidate. None left? We say so rather than overwrite one — overwriting here means cutting the only way in. The "ifreload -a" fallback goes too. It reloaded ALL interfaces, including the one carrying the session, and on a cloud image the main interface is described elsewhere — ifupdown2 takes it down without bringing it back. The fallback now raises the bridge by hand, touching nothing else; the stanza makes it persistent. The masquerade rule is checked before being added, so a retry piles nothing up. The original test banned "2>/dev/null" across the whole line so ifup's error stayed readable. That intent is kept, narrowed to the ifup call itself: the fallback legitimately probes. Assisted-by: Claude Opus 5 (cherry picked from commit 57991b186cf891b0db6b7228fb626c4c1af317cd) |
||
|---|---|---|
| .. | ||
| auto_ask.py | ||
| database_manager.py | ||
| deploy_form_extras.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.