vmware-aiops 2.4.1__tar.gz → 2.4.3__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_aiops-2.4.1 → vmware_aiops-2.4.3}/.claude-plugin/plugin.json +1 -1
- vmware_aiops-2.4.3/.github/workflows/windows-file-lock.yml +32 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.mcp.json +1 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/PKG-INFO +6 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/README-CN.md +2 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/README.md +2 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/RELEASE_NOTES.md +56 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/openclaw.plugin.json +1 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/package.json +1 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/pyproject.toml +4 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/server.json +2 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/SKILL.md +4 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/references/capabilities.md +2 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/references/setup-guide.md +5 -5
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_code_review_fixes.py +3 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_daemon_calls_are_audited.py +8 -8
- vmware_aiops-2.4.3/tests/eval/regression/test_delegated_lookup_errors.py +70 -0
- vmware_aiops-2.4.3/tests/eval/regression/test_image_registry_cross_process.py +134 -0
- vmware_aiops-2.4.3/tests/eval/regression/test_image_registry_legacy_rows.py +150 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_login_without_vsphere_role.py +56 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_mcp_frame_marks_failures.py +1 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_set_ttl_safety.py +12 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_write_round_low_findings.py +1 -1
- vmware_aiops-2.4.3/tests/test_ambiguous_inventory_names.py +127 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_cluster_ttl_plan_gate.py +2 -2
- vmware_aiops-2.4.3/tests/test_executors_act_on_the_previewed_vm.py +221 -0
- vmware_aiops-2.4.3/tests/test_filelock.py +81 -0
- vmware_aiops-2.4.3/tests/test_fsutil.py +53 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_gate_review_fixes.py +2 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_host_network_mgmt.py +10 -0
- vmware_aiops-2.4.3/tests/test_migrate_compatibility_check.py +405 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_plan_gate_narrow_fixes.py +3 -3
- vmware_aiops-2.4.3/tests/test_power_off_and_preview_policy.py +581 -0
- vmware_aiops-2.4.3/tests/windows_lock_check.py +125 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/uv.lock +12 -10
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/__init__.py +1 -1
- vmware_aiops-2.4.3/vmware_aiops/_filelock.py +94 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/_common.py +2 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/cluster.py +7 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/deploy.py +3 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/vm.py +38 -6
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/connection.py +39 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/_shared.py +16 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/datastore.py +2 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/guest.py +27 -10
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/plan.py +9 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/ttl.py +31 -8
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/vm.py +12 -4
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/datastore_browser.py +69 -17
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/guest_ops.py +28 -9
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/host_network_mgmt.py +16 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/inventory.py +69 -17
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/plan_executor.py +28 -6
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/plan_gate.py +48 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/planner.py +6 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/step_policy.py +74 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/ttl.py +19 -3
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/vm_gate.py +125 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/vm_lifecycle.py +92 -14
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/policy_roles.py +2 -1
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/scanner/scheduler.py +46 -2
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.clawhubignore +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.env.example +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.github/ISSUE_TEMPLATE/bug_report.yml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.github/ISSUE_TEMPLATE/config.yml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.github/ISSUE_TEMPLATE/feature_request.yml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.github/PULL_REQUEST_TEMPLATE.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.github/dependabot.yml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/.gitignore +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/Dockerfile +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/LICENSE +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/SECURITY.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/config.example.yaml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docker-compose.yml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/continue.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/cursor.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/goose.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/localcowork.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/mcp-agent.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/integrations/vscode-copilot.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/docs/plans/2026-03-09-plan-apply-design.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/deploy.yaml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/README.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/claude-code.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/continue.yaml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/cursor.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/goose.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/localcowork.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/mcp-agent.yaml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/mcp-configs/vscode-copilot.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/examples/ollama-local-setup.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/evals/evals.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/references/agent-guardrails.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/references/cli-reference.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/skills/vmware-aiops/references/investigation-protocol.md +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/smithery.yaml +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/conftest.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/_family.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/_scores.json +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/_scoring.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/_skill.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/conftest.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/test_entity_reachability.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/test_error_actionability.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/test_tool_description_quality.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/capability/test_tool_manifest_budget.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/_diag_fakes.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/_pc_fakes.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_aiops_specific.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_alarm_health_scale_n1.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_atexit_handlers_do_not_accumulate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_browse_ds_path_join.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_browse_sees_every_file.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_capability_grader.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_cli_destructive_guards.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_cli_writes_guarded.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_cluster_health_summary_delegation.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_config_path_resolution_is_shared.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_daemon_host_log_cycles.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_deploy_correctness.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_deploy_failures_are_failures.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_doctor_authenticates_every_target.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_documented_gates_match_the_registry.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_enum_params_match_implementation.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_env_secret_obfuscation.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_error_hints_fit_the_surface.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_event_sets_match_real_class_names.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_events_are_read_newest_first.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_guest_download_writes_the_local_disk.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_guest_username_is_explicit.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_host_log_scan_reads_real_logs.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_host_paths_protected.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_image_registry_per_target.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_instructions_name_targets.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_inventory_scale_issue31.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_linked_clone_failure_on_the_wire.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_list_envelope_conformance.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_list_plans_is_non_destructive.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_ova_network_mapping.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_release_blockers.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_result_envelope.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_returned_failure_is_audited.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_session_probe_eviction.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_snapshot_async.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_text_io_declares_encoding.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_tool_annotations_match_behaviour.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_unreachable_host_vmks.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_v1_5_25_blockers.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_vim_attribute_conformance.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_access_info.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_cluster_mgmt_sanitize.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_composite_tools_obey_policy.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_concurrent_local_state.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_config.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_drs_rules.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_guest_tools_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_init_and_onboarding.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_network_mgmt.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_no_destructive_ops.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_plan_rollback_final_fixes.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_plan_steps_obey_policy.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_policy_roles.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_reset_alarm_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_results_name_their_target.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_safe_error_passthrough.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_session_pool.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_stop_signal_runs_atexit.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_vm_delete_blast_radius.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/test_vm_tools_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/_fsutil.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/access_requirements.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/_root.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/access.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/alarm.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/doctor.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/hub.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/investigate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/mcp_config.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/plan.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/scan.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/cli/summary.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/config.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/doctor.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/init_wizard.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/__main__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/server.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/access.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/alarm.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/cluster.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/deploy.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/network.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/mcp_server/tools/summary.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/notify/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/notify/audit.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/notify/logger.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/notify/webhook.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/_paging.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/alarm_mgmt.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/cluster_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/cluster_mgmt.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/guest_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/health.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/iscsi_config.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/network_mgmt.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/ova_deploy.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/vm_delete_gate.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/ops/vm_deploy.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/policy_environment.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/scanner/__init__.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/scanner/alarm_scanner.py +0 -0
- {vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/vmware_aiops/scanner/log_scanner.py +0 -0
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
|
|
3
3
|
"name": "vmware-aiops",
|
|
4
4
|
"displayName": "VMware AIops",
|
|
5
|
-
"version": "2.4.
|
|
5
|
+
"version": "2.4.3",
|
|
6
6
|
"description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
|
|
7
7
|
"author": {
|
|
8
8
|
"name": "Wei Zhou",
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
name: Windows file lock
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
pull_request:
|
|
5
|
+
paths:
|
|
6
|
+
- 'vmware_aiops/_filelock.py'
|
|
7
|
+
- 'tests/windows_lock_check.py'
|
|
8
|
+
- '.github/workflows/windows-file-lock.yml'
|
|
9
|
+
push:
|
|
10
|
+
branches: [main]
|
|
11
|
+
paths:
|
|
12
|
+
- 'vmware_aiops/_filelock.py'
|
|
13
|
+
- 'tests/windows_lock_check.py'
|
|
14
|
+
- '.github/workflows/windows-file-lock.yml'
|
|
15
|
+
workflow_dispatch:
|
|
16
|
+
|
|
17
|
+
permissions:
|
|
18
|
+
contents: read
|
|
19
|
+
|
|
20
|
+
jobs:
|
|
21
|
+
real-msvcrt:
|
|
22
|
+
runs-on: windows-latest
|
|
23
|
+
timeout-minutes: 10
|
|
24
|
+
steps:
|
|
25
|
+
- uses: actions/checkout@v7
|
|
26
|
+
with:
|
|
27
|
+
persist-credentials: false
|
|
28
|
+
- uses: actions/setup-python@v7
|
|
29
|
+
with:
|
|
30
|
+
python-version: '3.12'
|
|
31
|
+
- name: Check four-process serialization, bounded timeout, and release
|
|
32
|
+
run: python tests/windows_lock_check.py vmware_aiops/_filelock.py
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: vmware-aiops
|
|
3
|
-
Version: 2.4.
|
|
3
|
+
Version: 2.4.3
|
|
4
4
|
Summary: VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool
|
|
5
5
|
Project-URL: Homepage, https://github.com/vmware-skills/VMware-AIops
|
|
6
6
|
Project-URL: Repository, https://github.com/vmware-skills/VMware-AIops
|
|
@@ -11,20 +11,23 @@ License-Expression: MIT
|
|
|
11
11
|
License-File: LICENSE
|
|
12
12
|
Requires-Python: >=3.10
|
|
13
13
|
Requires-Dist: apscheduler<4.0,>=3.10
|
|
14
|
+
Requires-Dist: certifi>=2026.10.19
|
|
14
15
|
Requires-Dist: httpx<1.0,>=0.27
|
|
15
|
-
Requires-Dist: mcp[cli]<2.0,>=1.
|
|
16
|
+
Requires-Dist: mcp[cli]<2.0,>=1.30
|
|
16
17
|
Requires-Dist: pyaml<27.0,>=24.0
|
|
17
18
|
Requires-Dist: python-dotenv<2.0,>=1.0
|
|
18
19
|
Requires-Dist: pyvmomi<10.0,>=8.0.3.0
|
|
19
20
|
Requires-Dist: rich<16.0,>=13.0
|
|
20
21
|
Requires-Dist: typer<1.0,>=0.12
|
|
21
|
-
Requires-Dist: vmware-monitor<3.0,>=2.
|
|
22
|
+
Requires-Dist: vmware-monitor<3.0,>=2.4.2
|
|
22
23
|
Requires-Dist: vmware-policy<2.0,>=1.23.1
|
|
23
24
|
Description-Content-Type: text/markdown
|
|
24
25
|
|
|
25
26
|
<!-- mcp-name: io.github.vmware-skills/vmware-aiops -->
|
|
26
27
|
# VMware AIops
|
|
27
28
|
|
|
29
|
+
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.
|
|
30
|
+
|
|
28
31
|
> **Author**: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com
|
|
29
32
|
> This is a community-driven project by a VMware engineer, not an official VMware product.
|
|
30
33
|
> For official VMware developer tools see [developer.broadcom.com](https://developer.broadcom.com).
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
<!-- mcp-name: io.github.vmware-skills/vmware-aiops -->
|
|
2
2
|
# VMware AIops
|
|
3
3
|
|
|
4
|
+
要用自己的模型和 Agent 平台进行只读自测,请看 marketplace 根目录的[共享模型适配自测任务](https://github.com/vmware-skills/marketplace/blob/main/MODEL_FIT_SELF_TEST.md)。
|
|
5
|
+
|
|
4
6
|
> **作者**: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com
|
|
5
7
|
> 本项目由 VMware 工程师维护的社区项目,非 VMware 官方产品。
|
|
6
8
|
> VMware 官方开发者工具请访问 [developer.broadcom.com](https://developer.broadcom.com)。
|
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
<!-- mcp-name: io.github.vmware-skills/vmware-aiops -->
|
|
2
2
|
# VMware AIops
|
|
3
3
|
|
|
4
|
+
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.
|
|
5
|
+
|
|
4
6
|
> **Author**: Wei Zhou, VMware by Broadcom — wei-wz.zhou@broadcom.com
|
|
5
7
|
> This is a community-driven project by a VMware engineer, not an official VMware product.
|
|
6
8
|
> For official VMware developer tools see [developer.broadcom.com](https://developer.broadcom.com).
|
|
@@ -1,3 +1,58 @@
|
|
|
1
|
+
## v2.4.3 — bind confirmed writes to measured identities; reject ambiguous inventory names (2026-11-08)
|
|
2
|
+
|
|
3
|
+
* **Confirmed MCP writes re-check the identities measured during that call.** The eight confirm-gated VM and snapshot tools pass the current blast-radius measurement's VM instance UUID and snapshot id into execution, refusing a replacement object found by the executor. Each `confirm=True` invocation measures afresh; the separate earlier preview supplies no identity token. The existing `delete_vm` acknowledgement requirement is unchanged, as are the CLI and plan-executor paths (AIops#49).
|
|
4
|
+
* **Missing objects in delegated investigation tools keep their remedy.** VM, host and datastore lookup errors from vmware-monitor retain the exact-name/listing guidance through AIops MCP and are classified as request errors; unexpected delegate failures remain reduced to their type.
|
|
5
|
+
* **Ambiguous host, cluster, datastore and datacenter names are refused.** A lookup that finds more than one match raises `AmbiguousNameError` with the matching managed-object ids; plan prechecks and CLI output expose the ambiguity instead of selecting the first result (AIops#48).
|
|
6
|
+
* The image-cache and TTL cross-process file lock is exercised on a real Windows GitHub Actions runner: four concurrent writers retain every row, a held lock times out with the lock path, and the lock is released after the holder exits (AIops#51).
|
|
7
|
+
* Require certifi 2026.10.19 or later to exclude the compromised emSign root CA from the TLS trust bundle (GHSA-6q48-6c7w-9gw2). The development lock resolves 2026.10.23 (AIops#53).
|
|
8
|
+
|
|
9
|
+
## v2.4.2 — a login refused for lack of a role says so; an unreadable host is not called unreachable (2026-10-19)
|
|
10
|
+
|
|
11
|
+
Needs vmware-monitor 2.4.2 (now the floor). Found on a vCenter 8.0.3 lab with two restricted SSO accounts
|
|
12
|
+
(follow-up to AIops#47).
|
|
13
|
+
|
|
14
|
+
* **A login vCenter refuses with `NoPermission` gets the role error, not the raw fault.** For an account with no
|
|
15
|
+
permission anywhere, vCenter refuses the login itself (`System.View` on the root folder), so the post-login
|
|
16
|
+
no-role check never ran and `doctor` and every tool showed the raw fault with a connectivity hint. It now raises
|
|
17
|
+
the no-role error: the "no vSphere role / Global Permissions" remedy only for a vCenter target and `System.View`;
|
|
18
|
+
an ESXi target or another privilege gets a neutral text naming the (sanitized) privilege. A wrong password
|
|
19
|
+
(`InvalidLogin`) is unchanged. Same text as vmware-monitor.
|
|
20
|
+
* **vmk tools and `cluster info` no longer call an unreadable host unreachable.** When the account cannot read a
|
|
21
|
+
host's connection state, `list_host_vmks` rows and the vmk write tools' refusal say the account cannot read the
|
|
22
|
+
host (`reachable: false` means "not read"), instead of advising a reconnect. `cluster info` colours the state
|
|
23
|
+
yellow, not red.
|
|
24
|
+
* **From vmware-monitor 2.4.2 (through `get_cluster_health_summary` / `get_cross_vcenter_attention`):** a host this
|
|
25
|
+
account cannot read is counted `hosts_unreadable` with a warning issue `host_unreadable`, not ranked as a
|
|
26
|
+
critical `host_down`.
|
|
27
|
+
|
|
28
|
+
## Unreleased — follow-ups to the 2.4.1 review
|
|
29
|
+
|
|
30
|
+
* **Previews show policy refusals.** `restore_vm_clean_slate`, `provision_vm_guest` and
|
|
31
|
+
`run_vm_guest_command_with_output` were refused by `rules.yaml` only at `confirm=True`; the preview now lists that
|
|
32
|
+
refusal in `blast_radius.blockers`, so the user sees it before agreeing.
|
|
33
|
+
* **A delete that powers the VM off first is checked as `power_off_vm` too:** the CLI `vm delete`, the TTL daemon,
|
|
34
|
+
and a plan rollback deleting the VM it created (checked when the VM is running or its state cannot be read). The
|
|
35
|
+
TTL daemon records one `delete_vm` row per change of outcome, as for a deny on `delete_vm`, and keeps the entry.
|
|
36
|
+
**Behaviour change for custom network roles:** a role that allows `set_vm_ttl` must also allow `power_off_vm`.
|
|
37
|
+
* **Image cache:** writes take a lock across processes (a CLI and an MCP scan at the same time lost one side's
|
|
38
|
+
rows); a scan keeps rows on datastores it failed to browse (its own or legacy ones) and drops this target's rows
|
|
39
|
+
on datastores that no longer exist. A cache that cannot be written no longer fails the scan: the images come back
|
|
40
|
+
with a `cache_note`, as in vmware-storage.
|
|
41
|
+
* **Each call is checked for what it will do, at the moment it does it.** `restore_vm_clean_slate` asks about
|
|
42
|
+
`power_off_vm` only when it actually powers the VM off; `provision_vm_guest` asks about the guest tools its step
|
|
43
|
+
types use (an exec-only provision is not refused by a deny on `upload_vm_guest_file`); a plan rollback asks about
|
|
44
|
+
the power-off after confirming it is the VM the plan created, just before powering it off.
|
|
45
|
+
* **`set_vm_ttl` is checked as the deletion it schedules:** the preview lists a deny on `delete_vm` (and on
|
|
46
|
+
`power_off_vm` for a running VM), and `confirm=True` refuses it, instead of scheduling a TTL the daemon can never
|
|
47
|
+
act on. The daemon still asks again at expiry.
|
|
48
|
+
* **`migrate_vm` previews run vCenter's own vMotion compatibility check** (`CheckMigrate_Task`, read-only): its
|
|
49
|
+
errors (CPU features, devices, networks, datastores) become blockers, with the CPU-feature remedy where it applies,
|
|
50
|
+
so a move vCenter would refuse is refused in the preview and before the CLI asks for confirmation; warnings are
|
|
51
|
+
shown and do not block. On a standalone ESXi host, or when the check cannot run, the preview says "not checked"
|
|
52
|
+
and does not block (vCenter checks again when the move starts). Plan migrate steps get the same check.
|
|
53
|
+
* The TTL store takes the same cross-process lock as the image cache (`set_vm_ttl` and the daemon run in separate
|
|
54
|
+
processes).
|
|
55
|
+
|
|
1
56
|
## v2.4.1 — fixes from the 2026-10-17 real-hardware read and write rounds
|
|
2
57
|
|
|
3
58
|
* **Tools that run other tools' operations obey `rules.yaml` for those tools**, on the MCP and CLI surfaces.
|
|
@@ -2595,4 +2650,4 @@ vmware-aiops vks clusters|health|scale|nodes
|
|
|
2595
2650
|
多目标配置。
|
|
2596
2651
|
|
|
2597
2652
|
- Environment variable password management.
|
|
2598
|
-
环境变量密码管理。
|
|
2653
|
+
环境变量密码管理。
|
|
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
|
|
|
4
4
|
|
|
5
5
|
[project]
|
|
6
6
|
name = "vmware-aiops"
|
|
7
|
-
version = "2.4.
|
|
7
|
+
version = "2.4.3"
|
|
8
8
|
description = "VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool"
|
|
9
9
|
readme = "README.md"
|
|
10
10
|
license = "MIT"
|
|
@@ -17,13 +17,14 @@ dependencies = [
|
|
|
17
17
|
"rich>=13.0,<16.0",
|
|
18
18
|
"apscheduler>=3.10,<4.0",
|
|
19
19
|
"httpx>=0.27,<1.0",
|
|
20
|
+
"certifi>=2026.10.19", # GHSA-6q48-6c7w-9gw2: exclude compromised emSign root
|
|
20
21
|
"python-dotenv>=1.0,<2.0",
|
|
21
|
-
"mcp[cli]>=1.
|
|
22
|
+
"mcp[cli]>=1.30,<2.0",
|
|
22
23
|
"vmware-policy>=1.23.1,<2.0",
|
|
23
24
|
# Read-only cluster-health triage (summary + HTML snapshot) is owned by
|
|
24
25
|
# vmware-monitor; AIops delegates to it so a conversation with the AIops
|
|
25
26
|
# entry point can produce the same report without duplicating the code.
|
|
26
|
-
"vmware-monitor>=2.
|
|
27
|
+
"vmware-monitor>=2.4.2,<3.0", # unreadable host != down, login refused -> role error
|
|
27
28
|
]
|
|
28
29
|
|
|
29
30
|
|
|
@@ -7,12 +7,12 @@
|
|
|
7
7
|
"url": "https://github.com/vmware-skills/VMware-AIops",
|
|
8
8
|
"source": "github"
|
|
9
9
|
},
|
|
10
|
-
"version": "2.4.
|
|
10
|
+
"version": "2.4.3",
|
|
11
11
|
"packages": [
|
|
12
12
|
{
|
|
13
13
|
"registryType": "pypi",
|
|
14
14
|
"identifier": "vmware-aiops",
|
|
15
|
-
"version": "2.4.
|
|
15
|
+
"version": "2.4.3",
|
|
16
16
|
"runtimeHint": "uvx",
|
|
17
17
|
"packageArguments": [
|
|
18
18
|
{
|
|
@@ -25,6 +25,8 @@ compatibility: >
|
|
|
25
25
|
|
|
26
26
|
# VMware AIops
|
|
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" and "vSphere" are trademarks of Broadcom. Source code is publicly auditable at [github.com/vmware-skills/VMware-AIops](https://github.com/vmware-skills/VMware-AIops) under the MIT license.
|
|
29
31
|
|
|
30
32
|
VMware family entry point — AI-powered VM lifecycle, deployment, and alarm management — 61 MCP tools.
|
|
@@ -63,7 +65,7 @@ Read before connecting an agent. Per-tool inventory: `references/capabilities.md
|
|
|
63
65
|
## Quick Install
|
|
64
66
|
|
|
65
67
|
```bash
|
|
66
|
-
uv tool install vmware-aiops==2.4.
|
|
68
|
+
uv tool install vmware-aiops==2.4.3
|
|
67
69
|
vmware-aiops doctor
|
|
68
70
|
vmware-aiops hub status # see which family members are installed
|
|
69
71
|
```
|
|
@@ -303,7 +305,7 @@ The account has no vSphere role. Assign one (Read-Only or higher) on the vCenter
|
|
|
303
305
|
## Setup
|
|
304
306
|
|
|
305
307
|
```bash
|
|
306
|
-
uv tool install vmware-aiops==2.4.
|
|
308
|
+
uv tool install vmware-aiops==2.4.3
|
|
307
309
|
mkdir -p ~/.vmware-aiops
|
|
308
310
|
vmware-aiops init # generates config.yaml and .env templates
|
|
309
311
|
chmod 600 ~/.vmware-aiops/.env
|
|
@@ -59,6 +59,8 @@ well-meaning agents, not a replacement for RBAC.
|
|
|
59
59
|
- **Cluster** (`delete_cluster`, `remove_cluster_host`): member hosts, VMs, datastores. Refused while hosts or VMs are still in the cluster, or when the host is not in maintenance mode or still runs powered-on VMs.
|
|
60
60
|
- **Clean Slate / TTL** (`restore_vm_clean_slate`, `set_vm_ttl`): the snapshot and what the revert discards; for a TTL, the VM that will be deleted unattended and when. Clean Slate is refused when the baseline snapshot is missing or its name is ambiguous — before anything is powered off — and reports an error, not `reverted`, if the revert did not happen. The TTL entry records the VM's target and instance UUID; at expiry the daemon deletes only a VM that still has that UUID (another VM under the same name is left alone, the entry dropped and the refusal audited). A TTL is refused on every `delete_vm` blocker except the power state (the daemon powers off first).
|
|
61
61
|
- **Snapshot names** (`revert_vm_snapshot`, `delete_vm_snapshot`, `restore_vm_clean_slate`): a name matches a snapshot's raw name or the name `list_vm_snapshots` shows (control/invisible characters stripped). Two snapshots matching the same name — duplicates, or names that differ only by stripped characters — are refused by the gate and by the executors, which no longer take the first.
|
|
62
|
+
- **Object names**: looking up a VM, host, cluster, datastore or datacenter by name across the vCenter refuses a name that matches more than one object of that kind, and lists the matches' managed-object ids, instead of taking the first. Cluster and datastore names are unique only within a datacenter, so two datacenters can each have a `Cluster01`.
|
|
63
|
+
- **What a confirmed call acts on** (`power_off_vm`, `migrate_vm`, `revert_vm_snapshot`, `delete_vm_snapshot`, `run_vm_guest_command`, `run_vm_guest_command_with_output`, `upload_vm_guest_file`, `provision_vm_guest`): the VM measured within that invocation, checked by instance UUID, and for snapshots the snapshot measured then, checked by id. Replacement between that measurement and the executor's lookup is refused ("not the VM that was previewed") before it changes anything. Each `confirm=True` invocation measures afresh; an earlier separate preview supplies no identity token. The `delete_vm` acknowledgement below remains the explicit check against a prior preview.
|
|
62
64
|
- **Plans** (`apply_vm_plan`, `rollback_vm_plan`): every step with its full parameters (passwords and other secret-looking keys redacted), which are destructive and which cannot be rolled back. Each destructive step is measured as its own tool measures it, and that tool's `blockers` / `unmeasured` become the plan's, prefixed `Step N (action):`. A step on an object an earlier step creates or changes (power off, then delete; a VM a step creates) is shown `check: "deferred"` and measured immediately before it runs; every destructive step is re-checked then, and a failed check stops the plan with a teaching error in that step's result. Refused when `target` does not match the plan's (no target is a target of its own), a step would be refused by its tool, or a plan step with action delete_vm carries no `acknowledge_blast_radius`. Every action the executor can run is classified: measured by its tool's gate (including `migrate`, measured as `migrate_vm`), refused, or non-destructive with a stated reason; anything else is refused rather than run unchecked. The plan actions `iscsi_enable`, `iscsi_add_target`, `iscsi_remove_target` and `storage_rescan` (plan-file action names, not tools) are gated in vmware-storage and cannot be measured here, so a plan containing one is refused at preview, apply and rollback — use `enable_iscsi`, `add_iscsi_target`, `remove_iscsi_target` / `rescan_storage` instead. Rollback steps get the same checks: each destructive rollback step (power off, delete snapshot, cluster delete, host removal) is measured in the `rollback_vm_plan` preview and again just before it runs; a refused check stops the rollback with a teaching error for that step, and the plan stays `failed` so rollback can be run again. A step that creates a VM records its instance UUID; rollback deletes the VM only if it still has that UUID, and refuses that rollback step otherwise. Plan responses never echo step passwords; secret keys are matched as whole name tokens (`password`, `passwd`, `pwd`, `secret`, `token`, `api_key`, `auth`, `credential(s)`, `private_key`).
|
|
63
65
|
- **Refusal messages** lead with the first blocker (problem and remedy) and count the rest ("…and 2 more blockers"), and stay within 480 characters; the preview lists every blocker.
|
|
64
66
|
- **Network / DRS** (`add_host_vmk`, `remove_host_vmk`, `set_vmk_service`, `create_dvs_portgroup`, `create_drs_rule`, `delete_drs_rule`, `set_drs_rule_enabled`): what would be created, changed or removed, with `blockers` and `unmeasured`; `remove_host_vmk` and `set_vmk_service` fail closed on an unreadable service map. Their refusals (a protected or the only management vmk, a VM-Host DRS rule) are reported as blockers in the preview and still raise on `confirm=True`.
|
|
@@ -6,13 +6,13 @@ All install methods fetch from the same source: [github.com/vmware-skills/VMware
|
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
8
|
# Via PyPI (recommended for version pinning)
|
|
9
|
-
uv tool install vmware-aiops==2.4.
|
|
9
|
+
uv tool install vmware-aiops==2.4.3
|
|
10
10
|
|
|
11
11
|
# Via Skills.sh (fetches from GitHub)
|
|
12
|
-
npx skills add vmware-skills/VMware-AIops#v2.4.
|
|
12
|
+
npx skills add vmware-skills/VMware-AIops#v2.4.3
|
|
13
13
|
|
|
14
14
|
# Via ClawHub (fetches from ClawHub registry snapshot of GitHub)
|
|
15
|
-
clawhub install @zw008/vmware-aiops --version 2.4.
|
|
15
|
+
clawhub install @zw008/vmware-aiops --version 2.4.3
|
|
16
16
|
```
|
|
17
17
|
|
|
18
18
|
### Claude Code
|
|
@@ -35,7 +35,7 @@ claude mcp add vmware-aiops -- vmware-aiops mcp
|
|
|
35
35
|
|
|
36
36
|
```bash
|
|
37
37
|
# 1. Install from PyPI (source: github.com/vmware-skills/VMware-AIops)
|
|
38
|
-
uv tool install vmware-aiops==2.4.
|
|
38
|
+
uv tool install vmware-aiops==2.4.3
|
|
39
39
|
|
|
40
40
|
# 2. Verify installation source
|
|
41
41
|
vmware-aiops --version # confirms installed version
|
|
@@ -73,7 +73,7 @@ The `vmware-aiops` package installs a Python CLI binary and its dependencies (py
|
|
|
73
73
|
## Development Install
|
|
74
74
|
|
|
75
75
|
```bash
|
|
76
|
-
git clone --branch v2.4.
|
|
76
|
+
git clone --branch v2.4.3 https://github.com/vmware-skills/VMware-AIops.git
|
|
77
77
|
cd VMware-AIops
|
|
78
78
|
uv venv && source .venv/bin/activate
|
|
79
79
|
# --no-sources: pyproject's [tool.uv.sources] points vmware-monitor at a sibling
|
|
@@ -127,7 +127,7 @@ def test_ttl_entry_kept_on_transient_failure(monkeypatch: pytest.MonkeyPatch) ->
|
|
|
127
127
|
monkeypatch.setattr(scheduler, "remove_entry", removed.append)
|
|
128
128
|
monkeypatch.setattr(
|
|
129
129
|
scheduler, "delete_vm",
|
|
130
|
-
lambda si, name: (_ for _ in ()).throw(RuntimeError("vCenter task timeout")),
|
|
130
|
+
lambda si, name, **k: (_ for _ in ()).throw(RuntimeError("vCenter task timeout")),
|
|
131
131
|
)
|
|
132
132
|
|
|
133
133
|
scheduler._run_ttl_check(MagicMock())
|
|
@@ -143,7 +143,7 @@ def test_ttl_entry_removed_when_vm_already_gone(monkeypatch: pytest.MonkeyPatch)
|
|
|
143
143
|
monkeypatch.setattr(scheduler, "remove_entry", removed.append)
|
|
144
144
|
monkeypatch.setattr(
|
|
145
145
|
scheduler, "delete_vm",
|
|
146
|
-
lambda si, name: (_ for _ in ()).throw(VMNotFoundError("VM 'ttl-vm' not found")),
|
|
146
|
+
lambda si, name, **k: (_ for _ in ()).throw(VMNotFoundError("VM 'ttl-vm' not found")),
|
|
147
147
|
)
|
|
148
148
|
|
|
149
149
|
scheduler._run_ttl_check(MagicMock())
|
|
@@ -156,7 +156,7 @@ def test_ttl_entry_removed_on_success(monkeypatch: pytest.MonkeyPatch) -> None:
|
|
|
156
156
|
removed: list[str] = []
|
|
157
157
|
monkeypatch.setattr(scheduler, "get_expired_entries", lambda: [_ttl_entry()])
|
|
158
158
|
monkeypatch.setattr(scheduler, "remove_entry", removed.append)
|
|
159
|
-
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
|
|
159
|
+
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
|
|
160
160
|
|
|
161
161
|
scheduler._run_ttl_check(MagicMock())
|
|
162
162
|
assert removed == ["ttl-vm"]
|
{vmware_aiops-2.4.1 → vmware_aiops-2.4.3}/tests/eval/regression/test_daemon_calls_are_audited.py
RENAMED
|
@@ -71,7 +71,7 @@ def ttl(monkeypatch):
|
|
|
71
71
|
|
|
72
72
|
def test_a_ttl_delete_writes_one_vm_delete_row(ttl, monkeypatch):
|
|
73
73
|
scheduler, removed = ttl
|
|
74
|
-
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
|
|
74
|
+
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
|
|
75
75
|
|
|
76
76
|
scheduler._run_ttl_check(MagicMock())
|
|
77
77
|
|
|
@@ -88,7 +88,7 @@ def test_a_ttl_delete_writes_one_vm_delete_row(ttl, monkeypatch):
|
|
|
88
88
|
def test_a_failed_ttl_delete_is_recorded_as_error_and_the_entry_kept(ttl, monkeypatch):
|
|
89
89
|
scheduler, removed = ttl
|
|
90
90
|
|
|
91
|
-
def boom(si, name):
|
|
91
|
+
def boom(si, name, **k):
|
|
92
92
|
raise RuntimeError("vCenter task timeout")
|
|
93
93
|
|
|
94
94
|
monkeypatch.setattr(scheduler, "delete_vm", boom)
|
|
@@ -106,7 +106,7 @@ def test_a_ttl_vm_already_gone_is_recorded_and_the_stale_entry_dropped(ttl, monk
|
|
|
106
106
|
|
|
107
107
|
scheduler, removed = ttl
|
|
108
108
|
|
|
109
|
-
def gone(si, name):
|
|
109
|
+
def gone(si, name, **k):
|
|
110
110
|
raise VMNotFoundError(f"VM '{name}' not found")
|
|
111
111
|
|
|
112
112
|
monkeypatch.setattr(scheduler, "delete_vm", gone)
|
|
@@ -122,7 +122,7 @@ def test_a_ttl_vm_already_gone_is_recorded_and_the_stale_entry_dropped(ttl, monk
|
|
|
122
122
|
def test_a_ttl_delete_refused_by_policy_never_runs(ttl, monkeypatch):
|
|
123
123
|
scheduler, removed = ttl
|
|
124
124
|
deleted: list[str] = []
|
|
125
|
-
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: deleted.append(name))
|
|
125
|
+
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: deleted.append(name))
|
|
126
126
|
|
|
127
127
|
def deny(skill, tool, params=None, *, risk_level="low", target=""):
|
|
128
128
|
raise PolicyDenied(
|
|
@@ -144,7 +144,7 @@ def test_a_refused_ttl_entry_writes_one_row_per_outcome_not_one_per_minute(ttl,
|
|
|
144
144
|
failing entry wrote a delete_vm row on every run — 1,440 a day per entry, on
|
|
145
145
|
this lab whose rules.yaml denies delete_vm — burying real calls."""
|
|
146
146
|
scheduler, removed = ttl
|
|
147
|
-
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: None)
|
|
147
|
+
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: None)
|
|
148
148
|
|
|
149
149
|
def deny(skill, tool, params=None, *, risk_level="low", target=""):
|
|
150
150
|
raise PolicyDenied(
|
|
@@ -165,7 +165,7 @@ def test_a_failing_ttl_delete_writes_again_only_when_its_outcome_changes(ttl, mo
|
|
|
165
165
|
scheduler, removed = ttl
|
|
166
166
|
attempts: list[str] = []
|
|
167
167
|
|
|
168
|
-
def flaky(si, name):
|
|
168
|
+
def flaky(si, name, **k):
|
|
169
169
|
attempts.append(name)
|
|
170
170
|
if len(attempts) <= 3:
|
|
171
171
|
raise RuntimeError("vCenter task timeout")
|
|
@@ -315,7 +315,7 @@ def test_a_ttl_vm_whose_name_is_ambiguous_is_not_deleted_and_the_entry_dropped(t
|
|
|
315
315
|
|
|
316
316
|
scheduler, removed = ttl
|
|
317
317
|
|
|
318
|
-
def ambiguous(si, name):
|
|
318
|
+
def ambiguous(si, name, **k):
|
|
319
319
|
raise AmbiguousVMError(f"2 VMs are named '{name}'.")
|
|
320
320
|
|
|
321
321
|
monkeypatch.setattr(scheduler, "delete_vm", ambiguous)
|
|
@@ -332,7 +332,7 @@ def test_daemon_rows_say_daemon_not_mcp(ttl, monkeypatch):
|
|
|
332
332
|
"""HLD §16 D-14: a TTL delete made by the daemon is not an MCP call. Without
|
|
333
333
|
an explicit surface the row read `mcp-stdio` — non-empty, and wrong."""
|
|
334
334
|
scheduler, _removed = ttl
|
|
335
|
-
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
|
|
335
|
+
monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
|
|
336
336
|
|
|
337
337
|
scheduler._run_ttl_check(MagicMock())
|
|
338
338
|
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
"""Monitor's missing-object remedies must survive the AIops MCP error wrapper.
|
|
2
|
+
|
|
3
|
+
Found on real vCenter, 2026-11-08: investigate_vm reduced Monitor's authored
|
|
4
|
+
VMNotFoundError to a generic failure and incorrectly suggested checking login.
|
|
5
|
+
The host and datastore delegates use different authored exception classes too.
|
|
6
|
+
"""
|
|
7
|
+
from __future__ import annotations
|
|
8
|
+
|
|
9
|
+
import asyncio
|
|
10
|
+
import importlib
|
|
11
|
+
import json
|
|
12
|
+
|
|
13
|
+
import mcp.types as mcp_types
|
|
14
|
+
import pytest
|
|
15
|
+
from vmware_policy.policy import reset_policy_engine
|
|
16
|
+
|
|
17
|
+
from vmware_aiops.mcp_server.server import mcp
|
|
18
|
+
from vmware_aiops.mcp_server.tools import summary
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
@pytest.fixture(autouse=True)
|
|
22
|
+
def policy_home(tmp_path, monkeypatch):
|
|
23
|
+
monkeypatch.setenv("OPS_HOME", str(tmp_path))
|
|
24
|
+
reset_policy_engine()
|
|
25
|
+
yield
|
|
26
|
+
reset_policy_engine()
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
def call(tool, arguments):
|
|
30
|
+
handler = mcp._mcp_server.request_handlers[mcp_types.CallToolRequest]
|
|
31
|
+
request = mcp_types.CallToolRequest(
|
|
32
|
+
method="tools/call",
|
|
33
|
+
params=mcp_types.CallToolRequestParams(name=tool, arguments=arguments),
|
|
34
|
+
)
|
|
35
|
+
result = asyncio.run(handler(request)).root
|
|
36
|
+
text = "".join(b.text for b in result.content if isinstance(b, mcp_types.TextContent))
|
|
37
|
+
return result, json.loads(text)
|
|
38
|
+
|
|
39
|
+
|
|
40
|
+
@pytest.mark.parametrize(("kind", "lookup", "listing"), [
|
|
41
|
+
("vm", "find_vm_by_name", "list_virtual_machines"),
|
|
42
|
+
("host", "find_host_by_name", "list_esxi_hosts"),
|
|
43
|
+
("datastore", "find_datastore_by_name", "list_all_datastores"),
|
|
44
|
+
])
|
|
45
|
+
def test_missing_delegate_object_keeps_its_real_remedy(monkeypatch, kind, lookup, listing):
|
|
46
|
+
# Exercise the real Monitor raise site, not a reconstructed exception.
|
|
47
|
+
module = importlib.import_module(f"vmware_monitor.ops.investigate_{kind}")
|
|
48
|
+
monkeypatch.setattr(module, lookup, lambda *_args: None)
|
|
49
|
+
monkeypatch.setattr(summary, "_get_connection", lambda *_args: object())
|
|
50
|
+
result, payload = call(f"investigate_{kind}", {f"{kind}_name": "missing-\x00object"})
|
|
51
|
+
assert result.isError is True
|
|
52
|
+
assert "not found" in payload["error"]
|
|
53
|
+
assert listing in payload["error"]
|
|
54
|
+
assert "missing-object" in payload["error"]
|
|
55
|
+
assert "\x00" not in payload["error"]
|
|
56
|
+
assert "doctor" not in payload["hint"]
|
|
57
|
+
|
|
58
|
+
|
|
59
|
+
@pytest.mark.parametrize("error_type", [RuntimeError, type("VMNotFoundError", (Exception,), {})])
|
|
60
|
+
def test_unplanned_delegate_errors_are_still_reduced(monkeypatch, error_type):
|
|
61
|
+
def fail(*_args, **_kwargs):
|
|
62
|
+
raise error_type("https://svc:secret-example@internal.invalid/api")
|
|
63
|
+
|
|
64
|
+
monkeypatch.setattr(summary, "_get_connection", lambda *_args: object())
|
|
65
|
+
monkeypatch.setattr(summary, "get_vm_investigation_bundle", fail)
|
|
66
|
+
result, payload = call("investigate_vm", {"vm_name": "missing-object"})
|
|
67
|
+
assert result.isError is True
|
|
68
|
+
assert payload["error"] == f"{error_type.__name__}: operation failed."
|
|
69
|
+
assert "secret-example" not in str(payload)
|
|
70
|
+
assert "doctor" in payload["hint"]
|
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
"""Two processes scanning at once must not drop each other's cached images.
|
|
2
|
+
|
|
3
|
+
Review 2026-10-18: the registry's read-modify-write was guarded by a
|
|
4
|
+
``threading.Lock``, which only serialises one process. A CLI scan and an MCP
|
|
5
|
+
server scan running side by side each read the old file, and the last
|
|
6
|
+
``os.replace`` wrote the other's rows away. The atomic replace stops a reader
|
|
7
|
+
seeing half a file; it does nothing for a lost update.
|
|
8
|
+
"""
|
|
9
|
+
|
|
10
|
+
from __future__ import annotations
|
|
11
|
+
|
|
12
|
+
import json
|
|
13
|
+
import os
|
|
14
|
+
import subprocess
|
|
15
|
+
import sys
|
|
16
|
+
import textwrap
|
|
17
|
+
import time
|
|
18
|
+
from pathlib import Path
|
|
19
|
+
|
|
20
|
+
import pytest
|
|
21
|
+
|
|
22
|
+
from vmware_aiops.ops import datastore_browser as dsb
|
|
23
|
+
|
|
24
|
+
_WRITERS = 4
|
|
25
|
+
|
|
26
|
+
_CHILD = textwrap.dedent(
|
|
27
|
+
"""
|
|
28
|
+
import sys, time
|
|
29
|
+
from pathlib import Path
|
|
30
|
+
from vmware_aiops.ops import datastore_browser as dsb
|
|
31
|
+
|
|
32
|
+
reg, target = Path(sys.argv[1]), sys.argv[2]
|
|
33
|
+
dsb.IMAGE_REGISTRY_FILE = reg
|
|
34
|
+
dsb.CONFIG_DIR = reg.parent
|
|
35
|
+
real_load = dsb._load_registry
|
|
36
|
+
|
|
37
|
+
def slow_load():
|
|
38
|
+
# Widen the read-modify-write window so the race is not left to luck.
|
|
39
|
+
data = real_load()
|
|
40
|
+
time.sleep(0.3)
|
|
41
|
+
return data
|
|
42
|
+
|
|
43
|
+
dsb._load_registry = slow_load
|
|
44
|
+
(reg.parent / f"ready-{target}").touch()
|
|
45
|
+
go = reg.parent / "go"
|
|
46
|
+
deadline = time.monotonic() + 60
|
|
47
|
+
while not go.exists():
|
|
48
|
+
if time.monotonic() > deadline:
|
|
49
|
+
sys.exit("parent never said go")
|
|
50
|
+
time.sleep(0.01)
|
|
51
|
+
img = {"name": f"{target}.iso", "ds_path": f"[datastore1] {target}.iso",
|
|
52
|
+
"size_mb": 1.0, "type": "File", "modified": ""}
|
|
53
|
+
dsb.scan_all_datastores = lambda si: {"datastore1": [img]}
|
|
54
|
+
dsb.update_registry(object(), target=target)
|
|
55
|
+
"""
|
|
56
|
+
)
|
|
57
|
+
|
|
58
|
+
|
|
59
|
+
def _child_env() -> dict[str, str]:
|
|
60
|
+
env = dict(os.environ)
|
|
61
|
+
# The children must import exactly the code this test process imported.
|
|
62
|
+
env["PYTHONPATH"] = os.pathsep.join(p for p in sys.path if p)
|
|
63
|
+
return env
|
|
64
|
+
|
|
65
|
+
|
|
66
|
+
def _run_writers(reg: Path, script: str, targets: list[str]) -> None:
|
|
67
|
+
procs = [
|
|
68
|
+
subprocess.Popen([sys.executable, "-c", script, str(reg), t], env=_child_env())
|
|
69
|
+
for t in targets
|
|
70
|
+
]
|
|
71
|
+
try:
|
|
72
|
+
deadline = time.monotonic() + 60
|
|
73
|
+
while not all((reg.parent / f"ready-{t}").exists() for t in targets):
|
|
74
|
+
assert time.monotonic() < deadline, "writers never became ready"
|
|
75
|
+
assert all(p.poll() is None for p in procs), "a writer exited early"
|
|
76
|
+
time.sleep(0.02)
|
|
77
|
+
(reg.parent / "go").touch()
|
|
78
|
+
for p in procs:
|
|
79
|
+
assert p.wait(timeout=60) == 0
|
|
80
|
+
finally:
|
|
81
|
+
for p in procs:
|
|
82
|
+
if p.poll() is None:
|
|
83
|
+
p.kill()
|
|
84
|
+
|
|
85
|
+
|
|
86
|
+
@pytest.mark.unit
|
|
87
|
+
def test_concurrent_scans_in_separate_processes_keep_every_row(tmp_path) -> None:
|
|
88
|
+
reg = tmp_path / "image_registry.json"
|
|
89
|
+
targets = [f"t{i}" for i in range(_WRITERS)]
|
|
90
|
+
|
|
91
|
+
_run_writers(reg, _CHILD, targets)
|
|
92
|
+
|
|
93
|
+
rows = json.loads(reg.read_text(encoding="utf-8"))["images"]
|
|
94
|
+
assert sorted(r["target"] for r in rows) == targets
|
|
95
|
+
|
|
96
|
+
|
|
97
|
+
@pytest.fixture
|
|
98
|
+
def registry(tmp_path, monkeypatch):
|
|
99
|
+
path = tmp_path / "image_registry.json"
|
|
100
|
+
monkeypatch.setattr(dsb, "IMAGE_REGISTRY_FILE", path)
|
|
101
|
+
monkeypatch.setattr(dsb, "CONFIG_DIR", tmp_path)
|
|
102
|
+
img = {"name": "x.iso", "ds_path": "[ds1] x.iso", "size_mb": 1.0,
|
|
103
|
+
"type": "File", "modified": ""}
|
|
104
|
+
monkeypatch.setattr(dsb, "scan_all_datastores", lambda si: {"ds1": [img]})
|
|
105
|
+
return path
|
|
106
|
+
|
|
107
|
+
|
|
108
|
+
def _hold_lock(reg: Path):
|
|
109
|
+
fcntl = pytest.importorskip("fcntl")
|
|
110
|
+
fh = open(reg.with_name(reg.name + ".lock"), "a+b") # noqa: SIM115
|
|
111
|
+
fcntl.flock(fh.fileno(), fcntl.LOCK_EX | fcntl.LOCK_NB)
|
|
112
|
+
return fh
|
|
113
|
+
|
|
114
|
+
|
|
115
|
+
@pytest.mark.unit
|
|
116
|
+
def test_a_held_lock_is_a_bounded_wait_that_names_the_lock_file(registry, monkeypatch) -> None:
|
|
117
|
+
monkeypatch.setattr(dsb, "REGISTRY_LOCK_TIMEOUT_S", 0.3, raising=False)
|
|
118
|
+
holder = _hold_lock(registry)
|
|
119
|
+
try:
|
|
120
|
+
started = time.monotonic()
|
|
121
|
+
# The scan is returned; the note says the cache was not updated and why.
|
|
122
|
+
out = dsb.update_registry(object(), target="vc")
|
|
123
|
+
assert "image_registry.json.lock" in out["cache_note"]
|
|
124
|
+
assert time.monotonic() - started < 5
|
|
125
|
+
finally:
|
|
126
|
+
holder.close()
|
|
127
|
+
assert not registry.exists(), "nothing may be written without the lock"
|
|
128
|
+
|
|
129
|
+
|
|
130
|
+
@pytest.mark.unit
|
|
131
|
+
def test_the_lock_is_released_after_a_write(registry) -> None:
|
|
132
|
+
dsb.update_registry(object(), target="vc")
|
|
133
|
+
holder = _hold_lock(registry) # would raise BlockingIOError if still held
|
|
134
|
+
holder.close()
|