Overview

Global View is WolfStack's fleet management dashboard. It scans all nodes in your cluster and presents every Docker container, LXC container, and VM in a single unified table — organised by cluster → server → containers → VMs. You get full control over every workload without switching between individual node pages.

Accessing Global View

1. Open the WolfStack dashboard on any node
2. In the left sidebar under Datacenter, click Global View
3. The Fleet Containers & VMs table starts loading from every node as soon as the page opens — no extra click
4. Click Scan in the page header when you also want the WolfNet IP table below it

You can also open the command palette and type containers — the All Containers & VMs entry takes you to the Control Panel, which shows the same inventory as tiles with grouping and custom groups.

Fleet Dashboard

Global View shows a unified table of every workload across your infrastructure:

Table Hierarchy

Containers and VMs are grouped under their parent node and cluster:

🏢 Production Cluster
  🖥️ web-server-01 (10.10.10.1)
      🐳 Docker  nginx-proxy       ● running   172.17.0.2
      🐳 Docker  redis-cache        ● running   172.17.0.3
      📦 LXC     app-backend        ● running   10.10.10.5
  🖥️ db-server-01 (10.10.10.2)
      📦 LXC     mariadb-primary    ● running   10.10.10.6
      🖥️ VM      windows-dev        ● stopped   10.10.10.10

Cluster headers only appear when you have multiple clusters. Single-cluster setups show server headers directly.

Live Stats Bars

Each container row has a stats sub-row showing CPU, memory, and disk usage as coloured bar charts:

Colour	CPU	Memory / Disk
Green	< 50%	< 70%
Amber	50 – 80%	70 – 90%
Red	> 80%	> 90%

VMs display static resource info (vCPU count, memory, disk size) rather than live percentages.

Container & VM Controls

Global View includes the full set of action buttons for every workload — exactly the same controls available on individual node pages.

Docker Containers

Button	Action	Available When
▶️	Start / Unpause	Stopped or paused
⏹️	Stop	Running
🔄	Restart	Running
⏸️	Pause	Running
💻	Open terminal console	Running
🗑️	Remove container	Stopped
📜	View logs	Always
📁	Browse volumes	Always
📂	Browse container files	Always
⚙️	Container settings	Always
📋	Clone container	Always
🚀	Migrate to another node	Always

LXC Containers

Button	Action	Available When
▶️	Start	Stopped
⏹️	Stop	Running
🔄	Restart	Running
⏸️	Freeze	Running
💻	Open terminal console	Running
🗑️	Destroy container	Stopped
📜	View logs	Always
📂	Browse container files	Always
⚙️	Container settings	Always
📋	Clone container	Always
🚀	Migrate to another node	Always
📦	Export container	Always

Virtual Machines

Button	Action	Available When
▶️	Start VM	Stopped
⏹️	Stop VM	Running
🖥️	Open VNC console	Running (with VNC)
⚙️	VM settings	Stopped
🗑️	Delete VM	Stopped
📋	View logs	Always

Search, Filter & Sort

The card header has three controls that act on the table instantly, without refetching:

• Search — matches name, LXC hostname, state, IP address, server name, cluster name and service badge names
• Type — All, Docker, LXC or VM
• State — All, Running or Not running

Click the Type, Name, Status or IP Address column header to sort; click again to reverse. Sorting reorders the rows under each server — the cluster → server hierarchy stays put. When a filter is active, servers with no matching rows are hidden, and the status line above the table reports how many of the fleet's items are showing.

Bulk Actions

Tick the checkbox on any row, or the header checkbox to select everything currently visible (so filter first, then select all). A bar appears above the table with the selection count and three buttons:

• Start — starts every selected item that is not running (a paused Docker container is unpaused)
• Stop — stops every selected item that is running (VMs get a graceful ACPI shutdown)
• Restart — restarts every selected item that is running

Items whose state makes the action meaningless are skipped rather than failed. After you confirm, a progress dialog lists each item with its result; the commands run four at a time so a large selection does not flood the node proxies. Selection survives a refresh — use Clear selection to drop it.

Cross-Node Operations

All actions work transparently across remote nodes. WolfStack automatically routes commands through its node proxy system:

• Local node — API calls go directly to /api/...
• Remote nodes — API calls are proxied through /api/nodes/{id}/proxy/...

Console and VNC sessions connect directly to the correct host for the best experience. Logs, volumes, file browsing, settings, clone, migrate, and export operations all route through the proxy automatically.

WolfNet IP Scanning

Global View also scans the WolfNet overlay network across all nodes, giving you a table of:

• Every WolfNet peer and its assigned IP address
• Connection status per peer
• Cluster membership
• Summary stats — total nodes, WolfNet peers, LXC containers, Docker containers, and VMs

Loading & Performance

Fetching container stats from every node can be slow, especially on large clusters. Global View handles this with:

• Per-node loading placeholders — each server shows a spinner while its data is fetched, results appear as they arrive, and the status line names the nodes still being waited on
• Parallel fetching — all nodes are queried simultaneously, not one at a time
• Activity indicator — a pulsing red dot appears in the bottom-left corner whenever an action is in-flight, so you always know something is working
• Button loading states — when you click an action button, it shows a spinner and all buttons in that row are disabled until the operation completes

Requirements

• A current version of WolfStack
• Multi-node features require clustering to be configured
• WolfNet IP scanning requires WolfNet to be installed on your nodes
• Single-node setups work too — Global View will show all local containers and VMs