v0.2.0

zpodweb 0.2.0, the web UI for zPodFactory. Run this version with:

git clone https://github.com/zPodFactory/zpodweb.git && cd zpodweb
git checkout v0.2.0
docker compose up -d --build     # serves on port 8500

Added

• Users page. Superadmins create users (the API token is shown with a copy button), edit
  them, reset their token, enable, disable or delete them, and see which groups each one
  belongs to; other users see and edit their own profile only.
• Groups page. Superadmins create, rename and delete permission groups and manage their
  members, so zPod and endpoint access can be granted to a team at once.
• Endpoint access. Each endpoint card gets an Access section where superadmins grant or
  revoke the users and groups who can see and use it.
• zPod networks on the zPod detail page, the web side of zcli zpod network (zpodapi with
  user networks). The Networks card, now full width, lists every network on zcore with its live
  status, grouped by kind (zPod networks, routed globally; zCore networks, local; user
  networks) in groups you can fold, remembered between visits. A maintainer adds a VLAN network
  (the dialog derives the subnet from the gateway, shows the usable range and how many IPs it
  holds, and catches reserved VLANs, duplicates and overlaps before sending), enables or
  disables it, turns masquerade on or off, and removes it; a superadmin advertises it to the
  NSX fabric or withdraws it, optionally as a dry run of the checks, and follows the routing
  run to its verdict, with the failing check shown when it fails. After a dry run passes,
  "Advertise for real" starts the real run at once.
• A Topology tab in the Networks card that draws zcore and everything upstream of it,
  with the T1's interface and address on the zPod segment, and for a picked network animates
  the path to the internet, from the fabric and to the management network, saying why each
  one works or is blocked. The tab, network and path are
  in the URL, so a link opens the same view.
• zPod storage on the zPod detail page, the web side of zcli zpod disk, zcli zpod storage
  and zcli zpod nfs (zcore with zboxapi 0.2.1). A Storage card under Networks lists the
  storages with their folders as a tree, each with a usage bar coloured by how full it is (the
  sizes on hover), its raw or LVM layout, mount, disk and NFS clients, and a pulsing dot on a
  folder some host has mounted (who, on hover), with its share (zcore.<domain>:<path>) one
  click from the clipboard; above it a line gives the NFS server's state,
  and below it come the blank and leftover disks and the system exports outside /FILER. A
  Layout tab draws each of zcore's disks with what is on it, and the space they add up to. A
  maintainer adds a storage on a new disk or a blank one (following the vCenter run, then
  zcore's steps), grows it, adds folders, changes their owner and mode, exports them to any
  host or chosen clients (the zPod's networks offered in one click, with ready-to-copy ESXi
  and Linux mount commands), deletes a storage either keeping its data on the disk or removing
  the disk too, after typing its name, and removes a blank or leftover disk. What cannot be
  changed (STORAGE01, NFS-01, the deploy's disks, system exports) shows disabled with the
  reason, and an older zcore gets a note instead of failing on click.

Changed

• The Network Topology card lists every zcore interface grouped by kind with a live status
  dot, and its T1 static routes include the user networks that are advertised or being
  advertised.
• On a zPod whose zcore is older than 13.7, masquerade and enable/disable are shown as
  unavailable instead of failing after the click, since zboxapi before 0.2.0 has neither.
• The zPods list's Networks column shows only the zPod's own subnets, with the VLAN zpodapi
  reports, so a user network no longer appears there as "VLAN 0"; user networks are on the
  zPod's detail page.

Full changelog: v0.1.0...v0.2.0

Every release: https://github.com/zPodFactory/zpodweb/blob/main/CHANGELOG.md