Esx.Settings.Clusters.Vms.Solutions.DeploymentInfo.Status

The Esx.Settings.Clusters.Vms.Solutions.DeploymentInfo.Status enumerated type defines how well a deployment conforms to the desired specification that is specified by the solution_info.

Possible values:

• NOT_APPLIED: The desired specification of the solution has never been applied.
• IN_PROGRESS: The system is actively working to reach the desired specification.
• COMPLIANT: The deployment is in full compliance with the desired specification.
• ISSUE: The system has hit issues that do not allow the deployment to reach the desired specification. See Esx.Settings.Clusters.Vms.Solutions.DeploymentInfo.issues.
• IN_LIFECYCLE_HOOK: The system is waiting on an activated VM lifecycle hook to be processed by the solution in order to continue attempting to reach the desired specification. See Esx.Settings.Clusters.Vms.Solutions.DeploymentInfo.lifecycle_hook.
• BLOCKED: The system is blocked from reaching the desired specification. For example, this can occur if Esx.Settings.Clusters.Vms.RemediationPolicy.SEQUENTIAL is set and another deployment is in ISSUE status.

Warning: this constant is part of a new feature in development. It may be changed at any time and may not have all supported functionality implemented.

• OBSOLETE_SPEC: The current desired specification of the solution is newer than the applied. This state should take precedence over: - IN_PROGRESS
  • ISSUE
  • IN_LIFECYCLE_HOOK

This enumeration was added in vSphere API 9.0.0.0.