VMware Private AI (Foundation with NVIDIA) — GPU & Model-Serving Ops
Disclaimer: This is a community-maintained open-source project and is not affiliated with, endorsed by, or sponsored by VMware, Inc., Broadcom Inc., or NVIDIA Corporation. "VMware", "vSphere", and "VCF" are trademarks of Broadcom; "NVIDIA" is a trademark of NVIDIA. Source is auditable at github.com/vmware-skills/VMware-PrivateAI under the MIT license.
Status: pre-MVP skeleton (2026-08-06). Skill #15 of the VMware family. Manages the GPU / AI-infrastructure layer of VMware Private AI Foundation with NVIDIA (PAIF-N) on vSphere 9.x / VCF 9.1 — GPU host/device inventory, vGPU & DirectPath profiles, GPU consumers and utilization, vGPU assignment, and Private AI Service (PAIS) model serving. Independent version line.
Companion of vmware-aiops (the vCenter VMs behind AI workloads), vmware-vks (GPU-enabled Kubernetes), and vmware-monitor (read-only health). This skill is the GPU lens over all three.
Every API path is verified against official Broadcom/NVIDIA docs before use (see
tests/eval/spec/privateai_endpoints.py) — no endpoints written from memory.
The one write, assign_vgpu, takes confirm (default false). Without it the call returns
blast_radius — the VM's name and id, current and target profile, whether its vGPU device is edited or a
new one added, power state, blockers and unmeasured — and changes nothing. confirm=true is refused
for a powered-on or suspended VM, a name shared by several VMs, and a VM whose power state or devices
cannot be read. It never powers a VM off itself.
Upgrading to 2.0
2.0 renames all 17 MCP tools so every name starts with a verb (e.g. directpath_profile_list → list_directpath_profiles, gpu_consumer_list → list_gpu_consumers, gpu_device_list → list_gpu_devices). The full old → new table is in
RELEASE_NOTES.md. Nothing else changes: same tools, parameters,
safety gates and CLI commands. If an agent prompt, script or ~/.vmware/rules.yaml names a tool, update it — though deny
rules written with the old names keep working with vmware-policy ≥ 1.18 (vmware-audit policy lists any rule the
renames widened), and vmware-pilot ≥ 1.13 translates old names in saved workflows.
If an install older than 2.0 shares that rules.yaml, give it vmware-policy ≥ 1.18.2 too: it matches each rule
against both the old and the new name, so one file serves both.
1 maintainer
Metadata
1 maintainer
Release files for vmware-privateai 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vmware_privateai-2.0.0.tar.gz | 188.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vmware_privateai-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 262.5 kB
Release files / vmware_privateai-2.0.0.tar.gz
| Download URL | vmware_privateai-2.0.0.tar.gz |
|---|---|
| Size | 188.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08aec72d9c5f10c1f549b239e42577372b59e3074f2e8d092efef0e474c14104
|
|
BLAKE2b-256 checksum How to use checksums |
da66f50f0809bb5aa6bbaa5a9628b3ae99e3dee2b6cef5ecd67ea62695593762
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / vmware_privateai-2.0.0-py3-none-any.whl
| Download URL | vmware_privateai-2.0.0-py3-none-any.whl |
|---|---|
| Size | 74.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9350915b663dc72ff3d9bae8bf2de92ddb5f7845bfebbc3fad311c9b7d25d13d
|
|
BLAKE2b-256 checksum How to use checksums |
0d324bfa6e47691c32ed033093c97d78797a8041c0387e628b3a69b25650c71e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
