Cores at their minimum.
Every CPU counted at least at the subscription's minimum, per vSphere cluster — unknown when sockets or cores are unknown.
The VMware exit
Every core you must renew.Every wave that leaves before.
For providers moving off VMware after the move to per-core subscriptions: Rymvard counts the cores your subscription needs — every CPU at least at its minimum — sets the renewal date against your migration waves, names the waves that land after it and the cores to renew if one slips, and compares staying with leaving using the costs you enter.
Read-only. New in version 0.27 — the screens show an illustrative example estate, not a customer.
The renewal date does not move. Your waves might.
Per-core subscriptions with a minimum per CPU make small hosts expensive. Every host still on vSphere at the renewal date must be renewed — and a move frees a host only when what remains still fits with its HA reserve.
Waves against the renewal.
The migration waves from vSphere to Proxmox, OpenStack or OpenShift, week by week, and which of them land after the renewal date.
Stay or leave.
The cost of staying and of leaving over one, three or five years, from the prices you enter — shown to administrators only.
What Rymvard shows
The renewal, cluster by cluster.
The cores to subscribe, the hosts that cannot be retired yet and the waves that decide it — each traceable to the inventory it came from.
Renewal at a glance.
The renewal date, the cores to subscribe and the cores still needed if a wave slips.
Clusters and hosts.
Cores per cluster, the hosts that cannot be retired yet and why.
Waves that free hosts.
A host is freed only when its cluster still holds the remaining load with its HA reserve.
Built on the private-cloud plan.
The same waves Rymvard checks week by week on the private-cloud page.
Read-only, from vCenter and the platforms you move to.
Rymvard reads the inventory. It never changes a cluster.
- vCenter inventory through the read-only connector; Proxmox, OpenStack and Kubernetes as targets.
- Licence rules, minimums and entitlements exactly as you enter them — your contract decides, Rymvard counts.
- Entered prices stay with administrators.
- Detailed records stay in their country; customer names are visible only to the people who need them.
New in 0.27 · Workspaces
A home for the VMware exit.
The exit team opens Rymvard on its own home — cores to subscribe at renewal, days to renewal, waves landing after it and clusters with unknown cores. See the workspaces
VMware Exit
Which cores must we renew — and which waves leave before the renewal?
- vSphere cores to subscribe at renewal
- Days to renewal
- Waves landing after the renewal
- Clusters with unknown cores
Screens from the running product on its example estate. Customer names appear only for planners and admins — findings never name a customer.
Across every vendor
Every licence, one table.
Oracle, Microsoft, Broadcom, Red Hat, SUSE and IBM positions side by side on Licences & Audit — what is short, what is unknown and what goes into this month's reports. Licence-aware placement
Know the renewal number before the renewal.
Your vSphere estate, read-only: the cores you must renew, and the waves that leave in time.