glad to see scale out/in made it back into vRA 7 🙂
if I use the action scale-out/in on a deployment it automatically adds/removes machines in the deployment (works fine). But how can I provide this information (scale direction, which machine will be added etc) to my orchestrator workflow, so I can configure my load balancer (i use my own workflows for netscaler/Restful as there are no plugins available). Currently I don't have NSX.
See the graphic here (F5, Apache!!!!)
from: vRealize Automation 7.1 - What's New - VMware Cloud Management
I would tie this to machine provisioning/deprovisioning events rather than the scale out action itself. That way it is pretty straightforward to pass the relevant information.
Any machines added or removed with scale out will still trigger the event broker states.
I would tie this to machine provisioning/deprovisioning events rather than the scale out action itself. That way it is pretty straightforward to pass the relevant information.
Any machines added or removed with scale out will still trigger the event broker states.
Thanks Grant,
that's exactly how we did it before 7.1 (there was no scale so we had additional blueprints). So we'll do the same in 7.1 now (at least all machines are now under a single deployment).
I was just hoping we could kinda use the on-demand LB (whichg is NSX only) or create an object that could handle the events.
Machine provisioning and destroy seems to be the only option currently if we're not using NSX
Kalli