vmware-avi 2.3.0__tar.gz → 2.5.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.claude-plugin/plugin.json +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.mcp.json +1 -1
- vmware_avi-2.3.0/README.md → vmware_avi-2.5.0/PKG-INFO +38 -3
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/README-CN.md +14 -3
- vmware_avi-2.3.0/PKG-INFO → vmware_avi-2.5.0/README.md +15 -25
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/RELEASE_NOTES.md +38 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/SECURITY.md +2 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/openclaw.plugin.json +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/package.json +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/pyproject.toml +4 -3
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/server.json +2 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/skills/vmware-avi/SKILL.md +5 -3
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/skills/vmware-avi/references/capabilities.md +7 -7
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/skills/vmware-avi/references/cli-reference.md +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/skills/vmware-avi/references/setup-guide.md +19 -4
- vmware_avi-2.5.0/tests/eval/regression/test_error_hints_fit_the_request.py +231 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_fix_pack.py +4 -4
- vmware_avi-2.5.0/tests/eval/regression/test_read_failures_are_failures.py +463 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_ako_write_gate.py +21 -43
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_lb_write_gate.py +19 -27
- vmware_avi-2.5.0/tests/test_policy_roles.py +69 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_session_pool.py +8 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/uv.lock +21 -19
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/__init__.py +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/cli.py +1 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/config.py +6 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/connection.py +10 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/mcp_server/server.py +116 -52
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ako_config.py +10 -1
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ako_ingress.py +47 -14
- vmware_avi-2.5.0/vmware_avi/ops/ako_multi_cluster.py +197 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/analytics.py +3 -6
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ssl_mgmt.py +22 -5
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/vs_mgmt.py +9 -2
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/write_gate.py +6 -37
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/policy_environment.py +4 -0
- vmware_avi-2.5.0/vmware_avi/policy_roles.py +69 -0
- vmware_avi-2.3.0/vmware_avi/ops/ako_multi_cluster.py +0 -125
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.clawhubignore +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.env.example +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.gitattributes +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/.gitignore +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/Dockerfile +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/config.example.yaml +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/evals/evals.json +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/examples/mcp-configs/claude-code.json +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/examples/mcp-configs/cursor.json +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/skills/vmware-avi/references/agent-guardrails.md +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/smithery.yaml +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/conftest.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/_family.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/_scores.json +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/_scoring.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/_skill.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/conftest.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/test_entity_reachability.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/test_error_actionability.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/test_tool_description_quality.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/capability/test_tool_manifest_budget.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_ako_diff_predicts_upgrade.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_avi_specific.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_capability_grader.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_cli_writes_guarded.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_config_path_resolution_is_shared.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_env_secret_obfuscation.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_every_tool_parameter_is_documented.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_external_text_sanitized.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_helm_output_display_is_redacted.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_helm_values_redaction.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_init_and_onboarding.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_instructions_name_targets.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_list_scaling.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_release_blockers.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_text_io_declares_encoding.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/eval/regression/test_write_command_teaching.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_ako_pod.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_ako_sync.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_analytics.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_audit.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_config.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_error_logs.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_mcp_error_paths.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_mcp_tools.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_no_destructive_ops.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_pool_mgmt.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_safe_error_passthrough.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_se_mgmt.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/tests/test_vs_mgmt.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/_errors.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/_safety.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/doctor.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/init_wizard.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/k8s_connection.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/mcp_server/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/mcp_server/__main__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/notify/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/notify/audit.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/__init__.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ako_gate.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ako_pod.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/ako_sync.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/lb_gate.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/pool_mgmt.py +0 -0
- {vmware_avi-2.3.0 → vmware_avi-2.5.0}/vmware_avi/ops/se_mgmt.py +0 -0
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
|
|
3
3
|
"name": "vmware-avi",
|
|
4
4
|
"displayName": "VMware AVI",
|
|
5
|
-
"version": "2.
|
|
5
|
+
"version": "2.5.0",
|
|
6
6
|
"description": "VMware AVI (NSX ALB) load balancer plus AKO Kubernetes ops — 28 MCP tools.",
|
|
7
7
|
"author": {
|
|
8
8
|
"name": "Wei Zhou",
|
|
@@ -1,7 +1,35 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: vmware-avi
|
|
3
|
+
Version: 2.5.0
|
|
4
|
+
Summary: AVI (NSX Advanced Load Balancer) management and AKO Kubernetes operations tool
|
|
5
|
+
Project-URL: Homepage, https://github.com/vmware-skills/VMware-AVI
|
|
6
|
+
Project-URL: Repository, https://github.com/vmware-skills/VMware-AVI
|
|
7
|
+
Project-URL: Issues, https://github.com/vmware-skills/VMware-AVI/issues
|
|
8
|
+
Project-URL: Changelog, https://github.com/vmware-skills/VMware-AVI/blob/main/RELEASE_NOTES.md
|
|
9
|
+
Author-email: Wei Zhou <zhouwei008@gmail.com>
|
|
10
|
+
License-Expression: MIT
|
|
11
|
+
Requires-Python: >=3.10
|
|
12
|
+
Requires-Dist: avisdk<31.0,>=22.1
|
|
13
|
+
Requires-Dist: httpx<1.0,>=0.27
|
|
14
|
+
Requires-Dist: kubernetes<33.0,>=28.0
|
|
15
|
+
Requires-Dist: mcp[cli]<2.0,>=1.30
|
|
16
|
+
Requires-Dist: pyaml<27.0,>=24.0
|
|
17
|
+
Requires-Dist: pyasn1<1.0,>=0.6.5
|
|
18
|
+
Requires-Dist: python-dotenv<2.0,>=1.0
|
|
19
|
+
Requires-Dist: rich<15.0,>=13.0
|
|
20
|
+
Requires-Dist: typer<1.0,>=0.12
|
|
21
|
+
Requires-Dist: vmware-policy<2.0,>=1.22.0
|
|
22
|
+
Description-Content-Type: text/markdown
|
|
23
|
+
|
|
1
24
|
<!-- mcp-name: io.github.vmware-skills/vmware-avi -->
|
|
25
|
+
|
|
26
|
+
MCP 2.5 migration: replace the removed `confirmed` / `dry_run` tool arguments with `confirm=true` for execution; omitting `confirm` previews. Old arguments are rejected without a write. CLI dry-run options are unchanged.
|
|
27
|
+
|
|
2
28
|
# VMware AVI
|
|
3
29
|
|
|
4
|
-
|
|
30
|
+
For a read-only check of this skill with your model and agent host, use the shared [model-fit self-test](https://github.com/vmware-skills/marketplace/blob/main/MODEL_FIT_SELF_TEST.md) in the marketplace root.
|
|
31
|
+
|
|
32
|
+
> **Author**: Wei Zhou, VMware by Broadcom — zhouwei008@gmail.com
|
|
5
33
|
> This is a community-driven project by a VMware engineer, not an official VMware product.
|
|
6
34
|
> For official VMware developer tools see [developer.broadcom.com](https://developer.broadcom.com).
|
|
7
35
|
|
|
@@ -308,7 +336,7 @@ vmware-avi ako sync force
|
|
|
308
336
|
### Multi-cluster AKO
|
|
309
337
|
|
|
310
338
|
```bash
|
|
311
|
-
# List
|
|
339
|
+
# List every kube-context and whether AKO runs there
|
|
312
340
|
vmware-avi ako clusters
|
|
313
341
|
|
|
314
342
|
# Cross-cluster AKO status overview
|
|
@@ -496,7 +524,7 @@ Force resync triggers AKO to re-reconcile all K8s objects. If the drift persists
|
|
|
496
524
|
|---------|---------|
|
|
497
525
|
| **Double Confirmation** | Destructive ops (VS disable, pool member disable, AKO restart, Helm upgrade, force resync) require 2 sequential confirmations |
|
|
498
526
|
| **Dry-Run Default** | `ako config upgrade` defaults to `--dry-run` mode -- user must explicitly confirm to apply |
|
|
499
|
-
| **MCP Blast Radius** | `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` take `confirm` (default `false`): a call without `confirm=true` returns `blast_radius` (what would change: VS/pool and member counts, the AKO pod and its Ingresses, the Helm release and chart move) and changes nothing. `confirm=true` is refused on a blocker (the pool's only enabled member, a terminating AKO pod, a failing `helm --dry-run`) or an unreadable field. `confirmed` / `dry_run` are
|
|
527
|
+
| **MCP Blast Radius** | `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` take `confirm` (default `false`): a call without `confirm=true` returns `blast_radius` (what would change: VS/pool and member counts, the AKO pod and its Ingresses, the Helm release and chart move) and changes nothing. `confirm=true` is refused on a blocker (the pool's only enabled member, a terminating AKO pod, a failing `helm --dry-run`) or an unreadable field. the old `confirmed` / `dry_run` aliases were removed in 2.4.1 and are refused as unknown arguments |
|
|
500
528
|
| **Audit Trail** | All operations logged to `~/.vmware/audit.db` via vmware-policy (`@vmware_tool` decorator) |
|
|
501
529
|
| **Password Protection** | `.env` file loading with permission check; never in shell history |
|
|
502
530
|
| **SSL Support** | `verify_ssl: false` for self-signed certs in isolated lab environments only |
|
|
@@ -591,11 +619,18 @@ claude mcp add --transport http vmware-avi https://mcp.example.com:8443/mcp \
|
|
|
591
619
|
before it binds that unauthenticated requests get 401. Use a certificate your clients trust for those names.
|
|
592
620
|
- Behind a TLS-terminating reverse proxy on the same machine use `--transport http --host 127.0.0.1
|
|
593
621
|
--public-name mcp.example.com` and pass the `Authorization` header through.
|
|
622
|
+
- Behind a load balancer or gateway on another machine, keep `--transport https` (a self-signed certificate is
|
|
623
|
+
fine), list in `--public-name` the host name the balancer sends as `Host`, and have it forward `Authorization`.
|
|
624
|
+
Its health probe can use `GET /healthz`, which needs no token and returns only `{"status": "ok"}`
|
|
625
|
+
(vmware-policy ≥ 1.23.0).
|
|
626
|
+
- Send `traceparent` or `X-Request-ID` with each request to have it stored on the audit row;
|
|
627
|
+
`vmware-audit log --correlation-id ID` then finds the calls behind one platform request.
|
|
594
628
|
- The audit log records each caller as `token:<name>`. Calls run side by side: each holds its own session to a
|
|
595
629
|
Controller (or Kubernetes context), up to `VMWARE_MCP_POOL_SIZE` (default 2) sessions per target. Each Controller
|
|
596
630
|
session is a login on the Controller; a call waits at most 300 s for a free one.
|
|
597
631
|
- **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
|
|
598
632
|
nothing on the platform. Run one endpoint per privilege level.
|
|
633
|
+
- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
|
|
599
634
|
|
|
600
635
|
**Offer only read tools, plus the writes you choose:**
|
|
601
636
|
|
|
@@ -1,7 +1,12 @@
|
|
|
1
1
|
<!-- mcp-name: io.github.vmware-skills/vmware-avi -->
|
|
2
|
+
|
|
3
|
+
MCP 2.5 迁移:工具参数中的旧 `confirmed` / `dry_run` 已移除;请求执行时使用 `confirm=true`,省略 `confirm` 则预览。旧参数会被拒绝且不执行写入,CLI 的 dry-run 选项不变。
|
|
4
|
+
|
|
2
5
|
# VMware AVI
|
|
3
6
|
|
|
4
|
-
|
|
7
|
+
要用自己的模型和 Agent 平台进行只读自测,请看 marketplace 根目录的[共享模型适配自测任务](https://github.com/vmware-skills/marketplace/blob/main/MODEL_FIT_SELF_TEST.md)。
|
|
8
|
+
|
|
9
|
+
> **作者**: Wei Zhou, VMware by Broadcom — zhouwei008@gmail.com
|
|
5
10
|
> 本项目由 VMware 工程师维护的社区项目,非 VMware 官方产品。
|
|
6
11
|
> VMware 官方开发者工具请访问 [developer.broadcom.com](https://developer.broadcom.com)。
|
|
7
12
|
|
|
@@ -305,7 +310,7 @@ vmware-avi ako sync force
|
|
|
305
310
|
### 多集群 AKO
|
|
306
311
|
|
|
307
312
|
```bash
|
|
308
|
-
#
|
|
313
|
+
# 列出所有 kube-context 及其上是否运行 AKO
|
|
309
314
|
vmware-avi ako clusters
|
|
310
315
|
|
|
311
316
|
# 跨集群 AKO 状态概览
|
|
@@ -493,7 +498,7 @@ vmware-avi-mcp
|
|
|
493
498
|
|------|------|
|
|
494
499
|
| **双重确认** | 破坏性操作(VS 禁用、池成员禁用、AKO 重启、Helm 升级、强制同步)需要 2 次确认 |
|
|
495
500
|
| **默认 Dry-Run** | `ako config upgrade` 默认为 `--dry-run` 模式,用户必须显式确认才会执行 |
|
|
496
|
-
| **MCP 影响范围(blast radius)** | `set_virtual_service_enabled`、`disable_lb_pool_member`、`restart_ako`、`force_ako_sync`、`upgrade_ako_config` 带 `confirm` 参数(默认 `false`):不传 `confirm=true` 时只返回 `blast_radius`(将改变什么:VS/池及成员数、AKO Pod 及其 Ingress、Helm release 与 chart 版本变化),不做任何修改。遇到阻断项(池内唯一启用的成员、正在终止的 AKO Pod、`helm --dry-run` 失败)或有字段读不到时,`confirm=true`
|
|
501
|
+
| **MCP 影响范围(blast radius)** | `set_virtual_service_enabled`、`disable_lb_pool_member`、`restart_ako`、`force_ako_sync`、`upgrade_ako_config` 带 `confirm` 参数(默认 `false`):不传 `confirm=true` 时只返回 `blast_radius`(将改变什么:VS/池及成员数、AKO Pod 及其 Ingress、Helm release 与 chart 版本变化),不做任何修改。遇到阻断项(池内唯一启用的成员、正在终止的 AKO Pod、`helm --dry-run` 失败)或有字段读不到时,`confirm=true` 会被拒绝。旧的 `confirmed` / `dry_run` 别名已在 2.4.1 移除,仍传它们会被当作未知参数拒绝 |
|
|
497
502
|
| **审计日志** | 所有操作通过 vmware-policy(`@vmware_tool` 装饰器)记录到 `~/.vmware/audit.db` |
|
|
498
503
|
| **密码保护** | `.env` 文件加载并检查权限;密码不会出现在 shell 历史记录中 |
|
|
499
504
|
| **SSL 支持** | `verify_ssl: false` 仅用于隔离实验环境中的自签名证书 |
|
|
@@ -571,11 +576,17 @@ claude mcp add --transport http vmware-avi https://mcp.example.com:8443/mcp \
|
|
|
571
576
|
证书要用客户端信任、且覆盖这些名字的证书。
|
|
572
577
|
- 在同一台机器上由反向代理终结 TLS 时,用 `--transport http --host 127.0.0.1 --public-name mcp.example.com`,
|
|
573
578
|
并让代理透传 `Authorization` 头。
|
|
579
|
+
- 负载均衡或网关在另一台机器上时,保持 `--transport https`(自签证书也可以),在 `--public-name` 里写上负载均衡
|
|
580
|
+
转发时带的 `Host` 名,并让它透传 `Authorization`。健康检查可以用 `GET /healthz`:不需要 token,只返回
|
|
581
|
+
`{"status": "ok"}`(需 vmware-policy ≥ 1.23.0)。
|
|
582
|
+
- 每个请求带上 `traceparent` 或 `X-Request-ID`,它会记进审计记录;用 `vmware-audit log --correlation-id ID`
|
|
583
|
+
就能查到平台上某一次请求对应的调用。
|
|
574
584
|
- 审计日志把每个调用者记为 `token:<名字>`。调用并行执行:每个调用独占一个到 Controller(或 Kubernetes context)的
|
|
575
585
|
会话,每个 target 最多 `VMWARE_MCP_POOL_SIZE`(默认 2)个会话。每个 Controller 会话都是在 Controller 上的一次登录;
|
|
576
586
|
调用最多等待 300 秒拿到空闲会话。
|
|
577
587
|
- **能连到这个端点的人,都以该 server 配置的账号操作。** token 只用来识别调用者,不在平台上授予任何权限。
|
|
578
588
|
每个权限级别单独起一个端点。
|
|
589
|
+
- **一个端点给多人或多种角色用:** 先运行一次 `vmware-audit roles enable`,再给每个 token 指定角色(`vmware-audit token create 名字 --role reader`,或在 `roles.yaml` 里定义可用的工具和 target;需 vmware-policy ≥ 1.24.0)。角色只能限定这个 token 在本端点上能调用什么,不能超出账号本身的权限。详见 vmware-policy README 的「网络调用者的角色」一节。
|
|
579
590
|
|
|
580
591
|
**只提供读工具,加上你选定的写工具:**
|
|
581
592
|
|
|
@@ -1,29 +1,12 @@
|
|
|
1
|
-
Metadata-Version: 2.5
|
|
2
|
-
Name: vmware-avi
|
|
3
|
-
Version: 2.3.0
|
|
4
|
-
Summary: AVI (NSX Advanced Load Balancer) management and AKO Kubernetes operations tool
|
|
5
|
-
Project-URL: Homepage, https://github.com/vmware-skills/VMware-AVI
|
|
6
|
-
Project-URL: Repository, https://github.com/vmware-skills/VMware-AVI
|
|
7
|
-
Project-URL: Issues, https://github.com/vmware-skills/VMware-AVI/issues
|
|
8
|
-
Project-URL: Changelog, https://github.com/vmware-skills/VMware-AVI/blob/main/RELEASE_NOTES.md
|
|
9
|
-
Author-email: Wei Zhou <wei-wz.zhou@broadcom.com>
|
|
10
|
-
License-Expression: MIT
|
|
11
|
-
Requires-Python: >=3.10
|
|
12
|
-
Requires-Dist: avisdk<31.0,>=22.1
|
|
13
|
-
Requires-Dist: httpx<1.0,>=0.27
|
|
14
|
-
Requires-Dist: kubernetes<33.0,>=28.0
|
|
15
|
-
Requires-Dist: mcp[cli]<2.0,>=1.28
|
|
16
|
-
Requires-Dist: pyaml<27.0,>=24.0
|
|
17
|
-
Requires-Dist: python-dotenv<2.0,>=1.0
|
|
18
|
-
Requires-Dist: rich<15.0,>=13.0
|
|
19
|
-
Requires-Dist: typer<1.0,>=0.12
|
|
20
|
-
Requires-Dist: vmware-policy<2.0,>=1.22.0
|
|
21
|
-
Description-Content-Type: text/markdown
|
|
22
|
-
|
|
23
1
|
<!-- mcp-name: io.github.vmware-skills/vmware-avi -->
|
|
2
|
+
|
|
3
|
+
MCP 2.5 migration: replace the removed `confirmed` / `dry_run` tool arguments with `confirm=true` for execution; omitting `confirm` previews. Old arguments are rejected without a write. CLI dry-run options are unchanged.
|
|
4
|
+
|
|
24
5
|
# VMware AVI
|
|
25
6
|
|
|
26
|
-
|
|
7
|
+
For a read-only check of this skill with your model and agent host, use the shared [model-fit self-test](https://github.com/vmware-skills/marketplace/blob/main/MODEL_FIT_SELF_TEST.md) in the marketplace root.
|
|
8
|
+
|
|
9
|
+
> **Author**: Wei Zhou, VMware by Broadcom — zhouwei008@gmail.com
|
|
27
10
|
> This is a community-driven project by a VMware engineer, not an official VMware product.
|
|
28
11
|
> For official VMware developer tools see [developer.broadcom.com](https://developer.broadcom.com).
|
|
29
12
|
|
|
@@ -330,7 +313,7 @@ vmware-avi ako sync force
|
|
|
330
313
|
### Multi-cluster AKO
|
|
331
314
|
|
|
332
315
|
```bash
|
|
333
|
-
# List
|
|
316
|
+
# List every kube-context and whether AKO runs there
|
|
334
317
|
vmware-avi ako clusters
|
|
335
318
|
|
|
336
319
|
# Cross-cluster AKO status overview
|
|
@@ -518,7 +501,7 @@ Force resync triggers AKO to re-reconcile all K8s objects. If the drift persists
|
|
|
518
501
|
|---------|---------|
|
|
519
502
|
| **Double Confirmation** | Destructive ops (VS disable, pool member disable, AKO restart, Helm upgrade, force resync) require 2 sequential confirmations |
|
|
520
503
|
| **Dry-Run Default** | `ako config upgrade` defaults to `--dry-run` mode -- user must explicitly confirm to apply |
|
|
521
|
-
| **MCP Blast Radius** | `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` take `confirm` (default `false`): a call without `confirm=true` returns `blast_radius` (what would change: VS/pool and member counts, the AKO pod and its Ingresses, the Helm release and chart move) and changes nothing. `confirm=true` is refused on a blocker (the pool's only enabled member, a terminating AKO pod, a failing `helm --dry-run`) or an unreadable field. `confirmed` / `dry_run` are
|
|
504
|
+
| **MCP Blast Radius** | `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` take `confirm` (default `false`): a call without `confirm=true` returns `blast_radius` (what would change: VS/pool and member counts, the AKO pod and its Ingresses, the Helm release and chart move) and changes nothing. `confirm=true` is refused on a blocker (the pool's only enabled member, a terminating AKO pod, a failing `helm --dry-run`) or an unreadable field. the old `confirmed` / `dry_run` aliases were removed in 2.4.1 and are refused as unknown arguments |
|
|
522
505
|
| **Audit Trail** | All operations logged to `~/.vmware/audit.db` via vmware-policy (`@vmware_tool` decorator) |
|
|
523
506
|
| **Password Protection** | `.env` file loading with permission check; never in shell history |
|
|
524
507
|
| **SSL Support** | `verify_ssl: false` for self-signed certs in isolated lab environments only |
|
|
@@ -613,11 +596,18 @@ claude mcp add --transport http vmware-avi https://mcp.example.com:8443/mcp \
|
|
|
613
596
|
before it binds that unauthenticated requests get 401. Use a certificate your clients trust for those names.
|
|
614
597
|
- Behind a TLS-terminating reverse proxy on the same machine use `--transport http --host 127.0.0.1
|
|
615
598
|
--public-name mcp.example.com` and pass the `Authorization` header through.
|
|
599
|
+
- Behind a load balancer or gateway on another machine, keep `--transport https` (a self-signed certificate is
|
|
600
|
+
fine), list in `--public-name` the host name the balancer sends as `Host`, and have it forward `Authorization`.
|
|
601
|
+
Its health probe can use `GET /healthz`, which needs no token and returns only `{"status": "ok"}`
|
|
602
|
+
(vmware-policy ≥ 1.23.0).
|
|
603
|
+
- Send `traceparent` or `X-Request-ID` with each request to have it stored on the audit row;
|
|
604
|
+
`vmware-audit log --correlation-id ID` then finds the calls behind one platform request.
|
|
616
605
|
- The audit log records each caller as `token:<name>`. Calls run side by side: each holds its own session to a
|
|
617
606
|
Controller (or Kubernetes context), up to `VMWARE_MCP_POOL_SIZE` (default 2) sessions per target. Each Controller
|
|
618
607
|
session is a login on the Controller; a call waits at most 300 s for a free one.
|
|
619
608
|
- **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
|
|
620
609
|
nothing on the platform. Run one endpoint per privilege level.
|
|
610
|
+
- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
|
|
621
611
|
|
|
622
612
|
**Offer only read tools, plus the writes you choose:**
|
|
623
613
|
|
|
@@ -1,3 +1,39 @@
|
|
|
1
|
+
## v2.5.0 — deprecated MCP alias migration and dependency security (2026-11-08)
|
|
2
|
+
|
|
3
|
+
* **MCP client migration:** the deprecated `confirmed` / `dry_run` aliases are removed from write tools as scheduled for the next minor release. Old arguments are rejected without executing a write. Omit `confirm` for a preview; use `confirm=true` to request execution through the same fresh measurement, Policy and audit gate. CLI dry-run options are unchanged.
|
|
4
|
+
* Update public author/project contact metadata to `zhouwei008@gmail.com`.
|
|
5
|
+
* Controller and Kubernetes behavior is covered by regression fixtures; this release does not add a live AVI 32.1.x/VCF 9.x validation claim.
|
|
6
|
+
|
|
7
|
+
* Require pyasn1 0.6.5 or later to avoid quadratic CPU use when parsing crafted ASN.1 data (CVE-2026-119194 through CVE-2026-119197); the development lock resolves 0.6.5.
|
|
8
|
+
* Connection-pool regression tests now gate overlapping calls before spawning, so they exercise the intended race without creating thousands of recursive threads. The avisdk idle cleanup keeps naive UTC timestamps while avoiding `datetime.utcnow()` in this package.
|
|
9
|
+
|
|
10
|
+
* **Error hints fit the error.** An error about the request itself (a 4xx other than 401/403, an unknown
|
|
11
|
+
controller) no longer tells the agent to run `doctor`, which would report green; an argument error that may
|
|
12
|
+
name no fix offers doctor only as a fallback. Connection, credential, 5xx and unparseable-response errors keep it.
|
|
13
|
+
* Duration errors no longer point MCP callers at `vmware-avi analytics --help`; they list the accepted forms.
|
|
14
|
+
|
|
15
|
+
* **A failed Kubernetes read is a failure, not "nothing there".** With no reachable cluster, `get_ako_amko_status`
|
|
16
|
+
answered "AMKO not deployed in avi-system namespace." — kubectl had failed. It now fails the call with kubectl's
|
|
17
|
+
reason; "not deployed" means kubectl answered and found no AMKO pods. A GSLBConfig that cannot be read is said,
|
|
18
|
+
not skipped. `list_ako_clusters` shows a context kubectl could not read as "Unreadable", not "Not deployed" (its
|
|
19
|
+
pod query no longer errors on an empty list), with kubectl's reason, says how many contexts are unknown, and
|
|
20
|
+
fails when none could be read, or when the kubeconfig has no contexts at all (kubectl exits 0 with nothing). An
|
|
21
|
+
image behind a registry port without a tag (`reg:5000/ako`) shows version `latest`, not `5000/ako`. `diagnose_ako_ingress` reports "not found"/"missing" only for a 404; a 403 or a
|
|
22
|
+
dropped connection is "could not be read", for the Ingress, each backend Service and each TLS secret.
|
|
23
|
+
* Same shape elsewhere: `check_ssl_cert_expiry` counts and names certificates whose expiry could not be read
|
|
24
|
+
(they used to drop out of the tally, reading as "not expiring"); unparseable `helm list` output is reported as
|
|
25
|
+
such, not as "No AKO Helm release found"; `get_virtual_service_status` says when the runtime read failed, with
|
|
26
|
+
the HTTP status. Certificate names and context names are shown as text, not Rich markup (a `[/]` in a name used
|
|
27
|
+
to fail the whole call).
|
|
28
|
+
|
|
29
|
+
## v2.4.0 — roles for network callers (HLD §18)
|
|
30
|
+
|
|
31
|
+
* Declares the role metadata vmware-policy ≥ 1.24.0 needs to apply **roles** to this server over HTTPS
|
|
32
|
+
(HLD §18): how a missing controller resolves, that tools without a `controller` argument act on the default controller, that the AKO tools act on a Kubernetes context (so a controller-limited role cannot use them), and that `diff_ako_config` and `upgrade_ako_config` escape a role (their Helm values can hold the controller password). With an older vmware-policy nothing changes. Once an operator runs
|
|
33
|
+
`vmware-audit roles enable`, a token's role decides which tools and targets it may use here; a refused call is
|
|
34
|
+
audited as `denied`. See vmware-policy's README, "Roles for network callers".
|
|
35
|
+
* README and setup guide: one endpoint for several people or roles.
|
|
36
|
+
|
|
1
37
|
## v2.3.0 — calls run side by side
|
|
2
38
|
|
|
3
39
|
**Calls no longer wait for each other** (HLD §16 D-13(2), via vmware-policy 1.22.0). When one server serves several
|
|
@@ -1169,7 +1205,7 @@ This release tracks vmware-pilot v1.5.17 (new `investigate_alert` template + `re
|
|
|
1169
1205
|
- **[READ]/[WRITE] tool prefixes**: All MCP tool descriptions now start with [READ] or [WRITE] to clearly indicate operation type
|
|
1170
1206
|
- **Read/write split counts**: SKILL.md MCP Tools section header shows exact read vs write tool counts
|
|
1171
1207
|
- **Negative routing**: Description frontmatter includes "Do NOT use when..." clause to prevent misrouting
|
|
1172
|
-
- **Broadcom author attestation**: README.md, README-CN.md, and pyproject.toml include VMware by Broadcom author identity (
|
|
1208
|
+
- **Broadcom author attestation**: README.md, README-CN.md, and pyproject.toml include VMware by Broadcom author identity (zhouwei008@gmail.com) to resolve Snyk E005 brand warnings
|
|
1173
1209
|
|
|
1174
1210
|
### AVI-specific
|
|
1175
1211
|
|
|
@@ -1226,4 +1262,4 @@ Initial release — AVI (NSX Advanced Load Balancer) management and AKO Kubernet
|
|
|
1226
1262
|
- Double confirmation for destructive operations
|
|
1227
1263
|
- Audit logging via vmware-policy
|
|
1228
1264
|
- 29 MCP tools + CLI commands
|
|
1229
|
-
- Doctor command for environment diagnostics
|
|
1265
|
+
- Doctor command for environment diagnostics
|
|
@@ -4,13 +4,13 @@
|
|
|
4
4
|
|
|
5
5
|
This is a community-maintained open-source project and is **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc.** "VMware", "NSX", and "AVI" are trademarks of Broadcom Inc.
|
|
6
6
|
|
|
7
|
-
**Author**: Wei Zhou, VMware by Broadcom —
|
|
7
|
+
**Author**: Wei Zhou, VMware by Broadcom — zhouwei008@gmail.com
|
|
8
8
|
|
|
9
9
|
## Reporting Vulnerabilities
|
|
10
10
|
|
|
11
11
|
If you discover a security vulnerability, please report it privately:
|
|
12
12
|
|
|
13
|
-
- **Email**:
|
|
13
|
+
- **Email**: zhouwei008@gmail.com
|
|
14
14
|
- **GitHub**: Open a [private security advisory](https://github.com/vmware-skills/VMware-AVI/security/advisories/new)
|
|
15
15
|
|
|
16
16
|
Do **not** open a public GitHub issue for security vulnerabilities.
|
|
@@ -4,12 +4,12 @@ build-backend = "hatchling.build"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "vmware-avi"
|
|
7
|
-
version = "2.
|
|
7
|
+
version = "2.5.0"
|
|
8
8
|
description = "AVI (NSX Advanced Load Balancer) management and AKO Kubernetes operations tool"
|
|
9
9
|
readme = "README.md"
|
|
10
10
|
license = "MIT"
|
|
11
11
|
requires-python = ">=3.10"
|
|
12
|
-
authors = [{ name = "Wei Zhou", email = "
|
|
12
|
+
authors = [{ name = "Wei Zhou", email = "zhouwei008@gmail.com" }]
|
|
13
13
|
dependencies = [
|
|
14
14
|
"avisdk>=22.1,<31.0",
|
|
15
15
|
"kubernetes>=28.0,<33.0",
|
|
@@ -17,8 +17,9 @@ dependencies = [
|
|
|
17
17
|
"typer>=0.12,<1.0",
|
|
18
18
|
"rich>=13.0,<15.0",
|
|
19
19
|
"httpx>=0.27,<1.0",
|
|
20
|
+
"pyasn1>=0.6.5,<1.0", # CVE-2026-119194–119197 via Kubernetes dependencies
|
|
20
21
|
"python-dotenv>=1.0,<2.0",
|
|
21
|
-
"mcp[cli]>=1.
|
|
22
|
+
"mcp[cli]>=1.30,<2.0",
|
|
22
23
|
"vmware-policy>=1.22.0,<2.0",
|
|
23
24
|
]
|
|
24
25
|
|
|
@@ -7,12 +7,12 @@
|
|
|
7
7
|
"url": "https://github.com/vmware-skills/VMware-AVI",
|
|
8
8
|
"source": "github"
|
|
9
9
|
},
|
|
10
|
-
"version": "2.
|
|
10
|
+
"version": "2.5.0",
|
|
11
11
|
"packages": [
|
|
12
12
|
{
|
|
13
13
|
"registryType": "pypi",
|
|
14
14
|
"identifier": "vmware-avi",
|
|
15
|
-
"version": "2.
|
|
15
|
+
"version": "2.5.0",
|
|
16
16
|
"runtimeHint": "uvx",
|
|
17
17
|
"packageArguments": [
|
|
18
18
|
{
|
|
@@ -25,6 +25,8 @@ compatibility: >
|
|
|
25
25
|
|
|
26
26
|
# VMware AVI
|
|
27
27
|
|
|
28
|
+
> Self-test: [guide](https://github.com/vmware-skills/marketplace/blob/main/MODEL_FIT_SELF_TEST.md).
|
|
29
|
+
|
|
28
30
|
> **Disclaimer**: This is a community-maintained open-source project and is **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc.** "VMware", "NSX", and "AVI" are trademarks of Broadcom. Source code is publicly auditable at [github.com/vmware-skills/VMware-AVI](https://github.com/vmware-skills/VMware-AVI) under the MIT license.
|
|
29
31
|
|
|
30
32
|
AVI (NSX Advanced Load Balancer) application delivery and AKO Kubernetes operations — 28 MCP tools.
|
|
@@ -53,7 +55,7 @@ AVI (NSX Advanced Load Balancer) application delivery and AKO Kubernetes operati
|
|
|
53
55
|
## Quick Install
|
|
54
56
|
|
|
55
57
|
```bash
|
|
56
|
-
uv tool install vmware-avi==2.
|
|
58
|
+
uv tool install vmware-avi==2.5.0
|
|
57
59
|
vmware-avi doctor # checks Controller connectivity + kubeconfig + avisdk
|
|
58
60
|
```
|
|
59
61
|
|
|
@@ -235,7 +237,7 @@ Force resync triggers AKO to re-reconcile all K8s objects. If the drift persists
|
|
|
235
237
|
## Setup
|
|
236
238
|
|
|
237
239
|
```bash
|
|
238
|
-
uv tool install vmware-avi==2.
|
|
240
|
+
uv tool install vmware-avi==2.5.0
|
|
239
241
|
mkdir -p ~/.vmware-avi
|
|
240
242
|
vmware-avi init # generates config.yaml and .env templates
|
|
241
243
|
chmod 600 ~/.vmware-avi/.env
|
|
@@ -254,7 +256,7 @@ All operations are automatically audited via vmware-policy (`@vmware_tool` decor
|
|
|
254
256
|
- Every tool call logged to `~/.vmware/audit.db` (SQLite, framework-agnostic)
|
|
255
257
|
- Policy rules enforced via `~/.vmware/rules.yaml` (deny rules, maintenance windows, risk levels)
|
|
256
258
|
- Each controller may declare `environment:` in `config.yaml` (`production` / `staging` / `lab`) as an optional label; an environment-scoped `deny` rule in `~/.vmware/rules.yaml` can match on it to block writes (e.g. freeze `production`). A controller with no label is simply not matched by such a rule. Reads are never affected
|
|
257
|
-
- MCP: `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` preview by default. Without `confirm=true` they return `blast_radius` — the VS or pool with its member counts, the AKO pod and the Ingresses it programs, or the Helm release and the chart it would move to — and change nothing. Show it to the user; do not pass `confirm=true` on your own because they asked earlier. `confirm=true` is refused when a blocker is found (the pool's only enabled member, a terminating AKO pod, a failing `helm upgrade --dry-run`) or a field could not be read. `confirmed` and `dry_run` are
|
|
259
|
+
- MCP: `set_virtual_service_enabled`, `disable_lb_pool_member`, `restart_ako`, `force_ako_sync` and `upgrade_ako_config` preview by default. Without `confirm=true` they return `blast_radius` — the VS or pool with its member counts, the AKO pod and the Ingresses it programs, or the Helm release and the chart it would move to — and change nothing. Show it to the user; do not pass `confirm=true` on your own because they asked earlier. `confirm=true` is refused when a blocker is found (the pool's only enabled member, a terminating AKO pod, a failing `helm upgrade --dry-run`) or a field could not be read. the old `confirmed` and `dry_run` aliases were removed in 2.4.1 and are refused as unknown arguments
|
|
258
260
|
- CLI: destructive commands require double confirmation; `vmware-avi ako config upgrade` defaults to `--dry-run`
|
|
259
261
|
- View recent operations: `vmware-audit log --last 20`
|
|
260
262
|
|
|
@@ -37,7 +37,7 @@ All 28 MCP tools exposed by `vmware-avi mcp` (v1.5.15+; legacy entry point: `vmw
|
|
|
37
37
|
| `vmware-avi mcp` (CLI subcommand, stdio) | ✅ Full | ✅ v1.5.15+ default — no PyPI re-resolve, works behind corporate TLS proxies. |
|
|
38
38
|
| `vmware-avi-mcp` (legacy console script, stdio) | ✅ Full | Kept for backward compatibility with pre-1.5.15 configs. |
|
|
39
39
|
| `python -m vmware_avi.mcp_server` (stdio, via `__main__.py`) | ✅ Full | Docker image `CMD` only — not for end-user CLI install, and no longer used by `smithery.yaml` (which now calls the `vmware-avi mcp` entry point). Added v1.5.22. |
|
|
40
|
-
| `uvx --from vmware-avi==2.
|
|
40
|
+
| `uvx --from vmware-avi==2.5.0 vmware-avi-mcp` | ⚠ Fallback | Re-resolves PyPI on each launch; fails behind corporate TLS proxies (踩坑 #25). Use `UV_NATIVE_TLS=true` workaround. |
|
|
41
41
|
|
|
42
42
|
## Automation Level Reference
|
|
43
43
|
|
|
@@ -67,7 +67,7 @@ Each operation is classified by autonomy level per the Enterprise Harness Engine
|
|
|
67
67
|
|------|-------------|------------|:----:|:-------:|
|
|
68
68
|
| `list_virtual_services` | List all Virtual Services on the active controller | `controller` (string, optional) | Low | No |
|
|
69
69
|
| `get_virtual_service_status` | Show detailed status of a single VS (VIP, health score, pool binding, enabled state) | `name` (string, **required**) | Low | No |
|
|
70
|
-
| `set_virtual_service_enabled` | Enable or disable a Virtual Service. Returns `blast_radius` (VS, uuid, current state, VIPs, pools and member counts); previews unless `confirm=true` | `name` (string, **required**), `enable` (boolean, **required**), `confirm` (boolean, default `false`)
|
|
70
|
+
| `set_virtual_service_enabled` | Enable or disable a Virtual Service. Returns `blast_radius` (VS, uuid, current state, VIPs, pools and member counts); previews unless `confirm=true` | `name` (string, **required**), `enable` (boolean, **required**), `confirm` (boolean, default `false`) | Medium | Yes (both directions) |
|
|
71
71
|
|
|
72
72
|
### Pool Member (4)
|
|
73
73
|
|
|
@@ -76,7 +76,7 @@ Each operation is classified by autonomy level per the Enterprise Harness Engine
|
|
|
76
76
|
| `list_lb_pools` | Discover pools on the Controller, with VS bindings (uses `/virtualservice-inventory` to include K8S-managed pool groups) | `vs_filter` (string, optional) | Low | No |
|
|
77
77
|
| `list_lb_pool_members` | List all members of a pool with health status and ratio | `pool` (string, **required**) | Low | No |
|
|
78
78
|
| `enable_lb_pool_member` | Enable a pool member (restore traffic after maintenance) | `pool` (string, **required**), `server` (string, **required**) | Low | No |
|
|
79
|
-
| `disable_lb_pool_member` | Disable a pool member with graceful connection drain. Returns `blast_radius` (pool, member, enabled members before/after); refuses the pool's only enabled member | `pool` (string, **required**), `server` (string, **required**), `confirm` (boolean, default `false`)
|
|
79
|
+
| `disable_lb_pool_member` | Disable a pool member with graceful connection drain. Returns `blast_radius` (pool, member, enabled members before/after); refuses the pool's only enabled member | `pool` (string, **required**), `server` (string, **required**), `confirm` (boolean, default `false`) | Medium | Yes |
|
|
80
80
|
|
|
81
81
|
### SSL Certificate (2)
|
|
82
82
|
|
|
@@ -107,7 +107,7 @@ Each operation is classified by autonomy level per the Enterprise Harness Engine
|
|
|
107
107
|
|------|-------------|------------|:----:|:-------:|
|
|
108
108
|
| `get_ako_status` | Check AKO pod status (phase, restart count, readiness) | `context` (string, optional) | Low | No |
|
|
109
109
|
| `get_ako_logs` | View AKO pod logs (tail mode) | `tail` (integer, default: 100), `since` (string, optional) | Low | No |
|
|
110
|
-
| `restart_ako` | Restart AKO pod by deleting it (its StatefulSet recreates it). Returns `blast_radius` (pod, uid, phase, Ingresses); the delete is pinned to the measured uid | `context` (string, optional), `confirm` (boolean, default `false`)
|
|
110
|
+
| `restart_ako` | Restart AKO pod by deleting it (its StatefulSet recreates it). Returns `blast_radius` (pod, uid, phase, Ingresses); the delete is pinned to the measured uid | `context` (string, optional), `confirm` (boolean, default `false`) | High | Yes |
|
|
111
111
|
| `get_ako_version` | Show AKO container image tag and Helm chart version | `context` (string, optional) | Low | No |
|
|
112
112
|
|
|
113
113
|
### AKO Config (3)
|
|
@@ -116,7 +116,7 @@ Each operation is classified by autonomy level per the Enterprise Harness Engine
|
|
|
116
116
|
|------|-------------|------------|:----:|:-------:|
|
|
117
117
|
| `get_ako_config` | Show current AKO Helm values (values.yaml snapshot; release auto-discovered via `helm list` — official installs use `--generate-name`) | *(none)* | Low | No |
|
|
118
118
|
| `diff_ako_config` | Preview the pending Helm change, running the same command `upgrade_ako_config` does (`--reuse-values` included) so the diff describes the actual upgrade rather than the chart's defaults. Chart: `oci://projects.packages.broadcom.com/ako/helm-charts/ako` | `chart_version` (optional — empty resolves to registry latest, which can move between calls) | Low | No |
|
|
119
|
-
| `upgrade_ako_config` | Helm upgrade the discovered AKO release from the official Broadcom OCI chart with `--reuse-values`. Without `confirm=true` returns `blast_radius` (release, chart now → chart to, status) plus the `helm upgrade --dry-run` output | `confirm` (boolean, default `false`), `chart_version` (optional)
|
|
119
|
+
| `upgrade_ako_config` | Helm upgrade the discovered AKO release from the official Broadcom OCI chart with `--reuse-values`. Without `confirm=true` returns `blast_radius` (release, chart now → chart to, status) plus the `helm upgrade --dry-run` output | `confirm` (boolean, default `false`), `chart_version` (optional) | High | Yes |
|
|
120
120
|
|
|
121
121
|
### Ingress Diagnostics (3)
|
|
122
122
|
|
|
@@ -132,13 +132,13 @@ Each operation is classified by autonomy level per the Enterprise Harness Engine
|
|
|
132
132
|
|------|-------------|------------|:----:|:-------:|
|
|
133
133
|
| `get_ako_sync_status` | Check overall K8s-to-Controller sync health | *(none)* | Low | No |
|
|
134
134
|
| `diff_ako_sync` | Show objects present in K8s but missing on Controller, and vice versa | *(none)* | Low | No |
|
|
135
|
-
| `force_ako_sync` | Force AKO to re-reconcile all K8s objects against the Controller (deletes the AKO pod). Returns `blast_radius` like `restart_ako` | `context` (string, optional), `confirm` (boolean, default `false`)
|
|
135
|
+
| `force_ako_sync` | Force AKO to re-reconcile all K8s objects against the Controller (deletes the AKO pod). Returns `blast_radius` like `restart_ako` | `context` (string, optional), `confirm` (boolean, default `false`) | Medium | Yes |
|
|
136
136
|
|
|
137
137
|
### Multi-cluster (2)
|
|
138
138
|
|
|
139
139
|
| Tool | Description | Parameters | Risk | Confirm |
|
|
140
140
|
|------|-------------|------------|:----:|:-------:|
|
|
141
|
-
| `list_ako_clusters` | List
|
|
141
|
+
| `list_ako_clusters` | List every K8s context and whether AKO runs there (unreadable ones say so) | *(none)* | Low | No |
|
|
142
142
|
| `get_ako_amko_status` | Show AMKO (Avi Multi-cluster Kubernetes Operator) GSLB status | *(none)* | Low | No |
|
|
143
143
|
|
|
144
144
|
## Risk Level Definitions
|
|
@@ -85,7 +85,7 @@ Complete command reference for the `vmware-avi` CLI (v1.4.0).
|
|
|
85
85
|
|
|
86
86
|
| Command | Description | Arguments / Flags |
|
|
87
87
|
|---------|-------------|-------------------|
|
|
88
|
-
| `vmware-avi ako clusters` | List
|
|
88
|
+
| `vmware-avi ako clusters` | List every kube-context and whether AKO runs there | -- |
|
|
89
89
|
| `vmware-avi ako amko-status` | Show AMKO (multi-cluster GSLB) status | -- |
|
|
90
90
|
|
|
91
91
|
## Destructive Operations Summary
|
|
@@ -21,7 +21,7 @@ Complete installation, configuration, and AI platform integration guide for the
|
|
|
21
21
|
### Standard Install (recommended)
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
|
-
uv tool install vmware-avi==2.
|
|
24
|
+
uv tool install vmware-avi==2.5.0
|
|
25
25
|
```
|
|
26
26
|
|
|
27
27
|
This installs the CLI (`vmware-avi`, with `vmware-avi mcp` subcommand for the MCP server in v1.5.15+), the legacy `vmware-avi-mcp` entry point (for backward compatibility), and all Python dependencies in an isolated environment.
|
|
@@ -29,7 +29,7 @@ This installs the CLI (`vmware-avi`, with `vmware-avi mcp` subcommand for the MC
|
|
|
29
29
|
### Development Install
|
|
30
30
|
|
|
31
31
|
```bash
|
|
32
|
-
git clone --branch v2.
|
|
32
|
+
git clone --branch v2.5.0 https://github.com/vmware-skills/VMware-AVI.git
|
|
33
33
|
cd VMware-AVI
|
|
34
34
|
uv pip install -e ".[dev]"
|
|
35
35
|
```
|
|
@@ -43,7 +43,7 @@ For platforms that prefer containerized MCP servers (e.g., Smithery registry, Ku
|
|
|
43
43
|
Build and run the MCP server in a container. The image uses `python:3.12-slim` with `uv` for dependency installation and runs `python -m vmware_avi.mcp_server` on stdio (no port exposed — MCP uses stdin/stdout).
|
|
44
44
|
|
|
45
45
|
```bash
|
|
46
|
-
git clone --branch v2.
|
|
46
|
+
git clone --branch v2.5.0 https://github.com/vmware-skills/VMware-AVI.git
|
|
47
47
|
cd VMware-AVI
|
|
48
48
|
|
|
49
49
|
# Build
|
|
@@ -72,7 +72,7 @@ Users can install via the Smithery UI or CLI without managing Python environment
|
|
|
72
72
|
|
|
73
73
|
| Deployment | Best For |
|
|
74
74
|
|------------|----------|
|
|
75
|
-
| `uv tool install vmware-avi==2.
|
|
75
|
+
| `uv tool install vmware-avi==2.5.0` + `vmware-avi mcp` | Local developer workstation, single-user CLI + MCP |
|
|
76
76
|
| Docker image | Self-hosted agents, CI runners, isolated environments, multi-user servers |
|
|
77
77
|
| Smithery | Zero-install agent integration, registry-managed discovery, hosted-MCP workflows |
|
|
78
78
|
|
|
@@ -257,6 +257,13 @@ vmware-avi mcp --transport https --host 0.0.0.0 --port 8443 \
|
|
|
257
257
|
- Behind a reverse proxy that terminates TLS (Nginx, HAProxy) on the same machine, use
|
|
258
258
|
`--transport http --host 127.0.0.1 --public-name mcp.example.com` (the names the proxy forwards in `Host`), and
|
|
259
259
|
have the proxy pass the `Authorization` header through.
|
|
260
|
+
- Behind a load balancer or gateway on another machine, keep `--transport https` (a self-signed certificate is
|
|
261
|
+
fine: the balancer is the client that has to trust it), list in `--public-name` the host name the balancer sends
|
|
262
|
+
as `Host`, and have it forward `Authorization`. Point its health probe at `GET /healthz`: it needs no token, returns
|
|
263
|
+
only `{"status": "ok"}` and accepts any `Host` (vmware-policy ≥ 1.23.0). Every other path still needs the token.
|
|
264
|
+
- Correlation: each audit row stores the caller's `traceparent` trace-id, else its `X-Request-ID` /
|
|
265
|
+
`X-Correlation-ID`. Have the agent platform send one, and `vmware-audit log --correlation-id ID` lists the calls
|
|
266
|
+
behind one platform request.
|
|
260
267
|
- `vmware-audit token list` / `token revoke NAME` manage callers; a revoked token is refused from its next request.
|
|
261
268
|
Replace a leaked token under a new name.
|
|
262
269
|
- The server will not start without at least one token, and checks before it binds that unauthenticated requests
|
|
@@ -267,6 +274,7 @@ vmware-avi mcp --transport https --host 0.0.0.0 --port 8443 \
|
|
|
267
274
|
- **Everyone who can reach the endpoint acts with this server's account.** Tokens identify callers; they grant
|
|
268
275
|
nothing on the platform. Run one endpoint per privilege level (for example a read-only account behind
|
|
269
276
|
`--expose read`, and a separate endpoint for operators).
|
|
277
|
+
- **Several people or roles on one endpoint:** run `vmware-audit roles enable` once, then give each token a role (`vmware-audit token create NAME --role reader`, or a role in `roles.yaml` naming tools and targets; vmware-policy ≥ 1.24.0). A role limits what the token may call on this endpoint; it cannot grant more than the account has. See vmware-policy's README, "Roles for network callers".
|
|
270
278
|
|
|
271
279
|
## Security
|
|
272
280
|
|
|
@@ -448,3 +456,10 @@ Update `ako.namespace` in config.yaml to match your deployment (default: `avi-sy
|
|
|
448
456
|
```bash
|
|
449
457
|
chmod 600 ~/.vmware-avi/.env
|
|
450
458
|
```
|
|
459
|
+
|
|
460
|
+
### MCP 2.5 legacy argument migration
|
|
461
|
+
|
|
462
|
+
The deprecated `confirmed` and `dry_run` MCP write-tool aliases are removed in
|
|
463
|
+
2.5. Old arguments fail validation without executing a write. Omit `confirm` for
|
|
464
|
+
a preview; pass `confirm=true` for execution through the existing fresh
|
|
465
|
+
measurement, Policy and audit gate. CLI dry-run flags are unchanged.
|