Programmatically change order of machines in rolling deployment
We have a windows service (that is apart of a Windows Cluster) deployed through Octopus Deploy. To continue to have high availability of this service during deployment, we use a parent rolling deployment step, with two child steps. The first child step checks to see if the current node Octopus Deploy is deploying to is the owner of a Windows cluster group, if so, move it to the next available node. The next (last) child step deploys the windows service associated to that cluster group (which is now no longer active on this node).
This works great, but it would be awesome if I can tell Octopus Deploy which machines to deploy to first, to provide the least amount of "failovers" (moving cluster group to a different node).
i.e. I can have all non-owner nodes of the cluster group to be deployed to first, before the active owner node. This ensures of only having to failover (move) the cluster group once.