Commits on Feb 15, 2017

1. constraintenforcer: Trigger task restarts when appropriate …

   The constraint enforcer currently sets task desired state to "shutdown"
   directly, which means the orchestrator will consider these tasks already
   processed, and won't trigger restarts. While this is appropriate for
   global services, replicated services should keep the desired number of
   replicas running, so each task shut down by the constraint enforcer
   should be restarted somewhere else.
   
   This changes the constraint enforcer to trigger a task shutdown by
   updating the actual state rather than desired state. This will cause the
   orchestrator to restart the task when necessary. It's not a perfect
   solution, because it bends rules about field ownership, and may cause
   the replacement task to start before the old one stops. However, it's a
   good compromise solution for this problem that doesn't require absorbing
   the constraint enforcer into each orchestrator (which wouldn't fit the
   model well), or adding a third type of state to every task.
   
   Also, update the global orchestrator to only restart a task when the
   node still meets the constraints.
   
   Signed-off-by: Aaron Lehmann <[email protected]>

   

   aaronlehmann committed Feb 15, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for 69fcc19
   • Browse repository at this point

   Copy the full SHA

   69fcc19 View commit details

   Browse the repository at this point in the history