GabrielBrascher edited a comment on pull request #4363: URL: https://github.com/apache/cloudstack/pull/4363#issuecomment-715511318
@ravening your PR covers a different scenario, very similar though. From what I understand, this PR avoids a problematic host to get back from down to Enabled. I don't see any problem in merging this one, but here follows a small summary on what #4111 does: In summary, it presents an API command to manually fence a problematic host. The command declares a host as degraded moving it from Alert or Disconnected to "Degraded" state. All VMs that were running and had HA enabled will be started on another host, VMs with HA disabled will triansit from "Running" state (obviously they are not running, but CloudStack does not know that) to Stopped. In summary, this implementation (#4363) is a simple way of avoiding a problematic host to get back and does not require admins to take action. The other PR (#4111) requires admins to execute an API command when they know a Disconnected/Alert host is down and has no running VMs. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
