Getting around the web interface
Everything in VM2Cloud VE is done through one web interface, served by every node on port 8006. Learning its shape once makes the rest of these guides shorter: almost every instruction is “select this in the tree, then open this menu entry”.
The four regions
Section titled “The four regions”| Region | What it is |
|---|---|
| Header | Search, in-product help, Create VM, Create CT, and your account menu. |
| Tree (left) | Everything the cluster contains — the datacenter, its nodes, and the guests and storages on them. |
| Content panel (centre) | A menu down its left edge, and the selected view beside it. The menu changes depending on what you selected in the tree. |
| Task panel (bottom) | Everything that has run recently, cluster-wide, and whether it succeeded. |
Selecting something in the tree changes what the content panel’s menu offers. There are four such menus:
| Select this | You get |
|---|---|
| Datacenter | Settings that apply to the whole cluster — Datacenter menu |
| A node | Settings for one server — Node menu |
| A virtual machine or container | Settings for one guest — Guest menu |
| A storage | What that storage holds — Storage |
Changing how the tree groups things
Section titled “Changing how the tree groups things”The dropdown above the tree offers four groupings of the same objects:
| View | Groups by | Useful when |
|---|---|---|
| Server View | Node, then what runs on it | The default. Answering “what is on this server?” |
| Folder View | Object type — all machines together, all storages together | Comparing like with like across nodes |
| Pool View | Resource pool | A pool per team or per customer |
| Tag View | Tag | You label machines by role or environment |
Guests appear under whichever node currently runs them, so a machine that moves between nodes moves in the tree.
Finding things quickly
Section titled “Finding things quickly”- The Search box in the header filters a cluster-wide list of every machine, storage and node. It is quicker than expanding the tree when you know a name or ID.
- Datacenter → Search shows the same list with usage columns, so it doubles as a quick answer to “which storage is filling up” and “which machine is busy”.
Watching what happens
Section titled “Watching what happens”Actions do not block the interface — they become tasks. The Tasks tab at the bottom lists them cluster-wide with who ran each one; double-click a row for the full output. Cluster log beside it records cluster-level events.
There are narrower versions of the same thing:
| Scope | Where |
|---|---|
| Everything, all nodes | Task panel → Tasks |
| One node | node → Task History |
| One machine | guest → Task History |
When something fails, the task output is the first place to look — and Download on Task History saves it, which is what support will ask for.
Acting on many machines at once
Section titled “Acting on many machines at once”Bulk Actions, top right of the Datacenter and node views, offers Bulk Start, Bulk Shutdown, Bulk Suspend and Bulk Migrate. Each opens a list where you pick the machines to include.
How many run at the same time is set by Datacenter → Options → Maximal Workers/bulk-action.
Help, at the top right of nearly every panel, opens documentation for the panel you are looking at. Documentation in the header opens this site.
Signing in
Section titled “Signing in”https://<server IP address>:8006A new node presents a certificate issued by the cluster’s own certificate authority, so the browser warns that the connection is not private. That is expected — see Certificates to replace it with one your browser trusts.
Sign in with a user name, its realm, and the matching password. root uses the
Linux PAM standard authentication realm; administrators you create yourself should use
the VM2Cloud Virtual Environment authentication server realm instead — see
Users, roles and permissions.