zw008/VMware-Storage

> **Author**: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com
> This is a community-driven project by a VMware engineer, not an official VMware product.
> For official VMware developer tools see developer.broadcom.com.
English | 中文
VMware vSphere storage management: datastores, iSCSI, vSAN, and read-only Fibre Channel / multipath diagnostics — 15 MCP tools, domain-focused and lightweight.
> Split from vmware-aiops for lighter context and local model compatibility.
Upgrading to 2.0
2.0 renames 10 of its MCP tools (all but the four that already started with a verb) so every name starts with a verb (e.g. fc_adapter_list → list_fc_adapters, storage_device_paths → list_storage_device_paths, storage_iscsi_add_target → add_iscsi_target). The full old → new table is in
RELEASE_NOTES.md. Three tools also change a parameter: browse_datastore and scan_datastore_images take
datastore_name (was ds_name, now the same as vmware-aiops' browse_datastore), and list_all_datastores gains an
optional limit (same as vmware-monitor's). Everything else stays: same tools, safety gates and CLI commands (the CLI
still takes the datastore name as before). 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.
Companion Skills
| Skill | Scope | Tools | Install |
|-------|-------|:-----:|---------|
| **vmware-aiops** ⭐ entry point | VM lifecycle, deployment, guest ops, clusters | 49 | uv tool install vmware-aiops |
| **vmware-monitor** | Read-only monitoring, alarms, events, VM info | 27 | uv tool install vmware-monitor |
| **vmware-vks** | Tanzu Namespaces, TKC cluster lifecycle | 20 | uv tool install vmware-vks |
| **vmware-nsx** | NSX networking: segments, gateways, NAT, IPAM | 33 | uv tool install vmware-nsx-mgmt |
| **vmware-nsx-security** | DFW microsegmentation, security groups, Traceflow | 21 | uv tool install vmware-nsx-security |
| **vmware-aria** | Aria Ops metrics, alerts, capacity planning | 28 | uv tool install vmware-aria |
Quick Install
Offline / Air-Gapped Install (from source)
This project uses the modern PEP 517 build system (hatchling), so there is **no
setup.py** by design — that is expected, not a missing file. If you cloned the
source and hit ERROR: File "setup.py" or "setup.cfg" not found ... editable mode
currently requires a setuptools-based build, your pip is older than 21.3 and
cannot do an *editable* (-e) install with a non-setuptools backend. Editable
mode is a developer convenience, not needed to run the tool — do one of:
For a **truly air-gapped host**, build the wheels on a connected machine and copy
them over — the target then needs no network:
Configuration
MCP Tools (15)
| Category | Tools | Type |
|----------|-------|------|
| Datastore | list_all_datastores, browse_datastore, scan_datastore_images, list_cached_images | Read |
| iSCSI | enable_iscsi, get_iscsi_status, add_iscsi_target, remove_iscsi_target, rescan_storage | Read/Write |
| vSAN | get_vsan_health, get_vsan_capacity, get_vsan_efficiency | Read |
| FC / multipath | list_fc_adapters, list_storage_device_paths | Read |
| Access | get_access_info — which account the server uses and whether it holds each tool's vSphere privileges (root folder) | Read |
Auto-Remediation Patterns (PoC)
The patterns/ directory hosts L5 auto-remediation candidate patterns from the Enterprise Harness Engineering framework. The first PoC pattern, patterns/iscsi-target-stale-rescan.yaml, describes an iSCSI HBA rescan as a low-risk, reversible, repeatable operation. The pattern schema is documented here only — runtime enforcement is **not yet wired up**, so this is a reference design, not production auto-remediation.