1
0
Fork 0
mirror of https://github.com/retspen/webvirtcloud synced 2026-11-08 19:26:48 +00:00
webvirtcloud/computes/tests
catborise 1b99d2eac5 feat(computes): the host overview shows its VMs, capacity and load, also when it cannot be reached
A host the panel could not reach made its overview the 500 page,
without the host's sections, and the Computes list gave such a host an
Overview button that led nowhere. The page now keeps the host's name,
sections, "Edit connection" and "Remove from panel" (the existing
confirmation), and says "Not connected" with the reason and a "Try
again". Details that cannot be read are said in an alert; the VMs,
capacity and load still show, as they are read on their own.

A reachable host's page leads with what it runs and what it gave:
- its VMs by state (running, shut off, paused, other), linked to
  Instances;
- the vCPUs, memory and storage pools given, as on the Computes list,
  which now shares those parts (computes/capacity_*.html) and their
  preparation (views.shown_capacity) with it;
- CPU and memory in use, side by side, with the current reading in
  words, a note on what the charts hold and when they were last
  updated, or since when not; memory in GB like the rest of the page;
- Hardware and Software and connection: logical CPUs and clock from
  virNodeGetInfo, but physical cores, sockets and NUMA nodes counted
  from the CPUs of the capabilities' NUMA cells, as virNodeGetInfo
  makes a topology up for hosts it cannot describe (asymmetric NUMA);
  the hypervisor's own name and version, libvirt, emulator, the guest
  architectures as text instead of menus of dead links. A host without
  sysinfo shows no processor instead of failing.
Empty notes no longer show "None"; labels stack over their values on a
phone instead of running into them.

Pools that cannot be read no longer drop a host's vCPUs and memory from
its capacity: the storage part says so. get_capacity also counts the
VMs by state.
2026-10-27 14:51:18 +03:00
..
__init__.py test: each app keeps its tests in a tests package 2026-10-12 15:17:30 +03:00
test_api_security.py refactor(computes): the lock helpers take claims instead of file locks 2026-10-14 23:27:57 +03:00
test_audit_rows.py feat(logs): admin changes and logins are recorded on the Logs page 2026-10-23 10:30:48 +03:00
test_capacity.py feat(computes): the host overview shows its VMs, capacity and load, also when it cannot be reached 2026-10-27 14:51:18 +03:00
test_compute_password.py fix(api): host API checks what the web forms check 2026-10-26 17:47:18 +03:00
test_cpu_graph.py feat(computes): the host overview shows its VMs, capacity and load, also when it cannot be reached 2026-10-27 14:51:18 +03:00
test_host_nav.py refactor(computes): the host pages share one section nav 2026-10-27 14:51:18 +03:00
test_migration_address.py test: each app keeps its tests in a tests package 2026-10-12 15:17:30 +03:00
test_operation_locks.py refactor(computes): the lock helpers take claims instead of file locks 2026-10-14 23:27:57 +03:00
test_overview.py feat(computes): the host overview shows its VMs, capacity and load, also when it cannot be reached 2026-10-27 14:51:18 +03:00
test_overview_status.py feat(computes): the host overview shows its VMs, capacity and load, also when it cannot be reached 2026-10-27 14:51:18 +03:00
test_ownership.py fix(admin): Removed VMs shows the host a VM left and confirms a delete 2026-10-26 11:48:40 +03:00
test_ownership_race.py fix(computes): a VM moved between computes keeps its owners on PostgreSQL 2026-10-23 15:31:04 +03:00
test_quota_down_host.py test: each app keeps its tests in a tests package 2026-10-12 15:17:30 +03:00
test_reconciliation.py test: each app keeps its tests in a tests package 2026-10-12 15:17:30 +03:00
test_validators.py test: each app keeps its tests in a tests package 2026-10-12 15:17:30 +03:00
test_views.py fix(computes): host pages survive a down host and a vTPM secret 2026-10-26 15:36:57 +03:00