Service Activation and Automation

Hmm, not sure if this is what you meant, but it sparked another thought. If only the services that are active will pass the health check, why not just have all nodes configured in each pool. Only the ones with the service active will actually pass the health check, and thus be sent traffic.

 

 

Yes, ultimately, even a very basic HTML "GET" health check will validate the service on each port, so standard health checks (albeit on specific ports) will work. I still need to provide some automation, but I think the F5 side will essentially just automatically enable/disable the nodes based on which ones are passing/failing health checks.

 

 

Not sure why this didn't occur to me, but thanks for the catalyst thought. Now I just need to find a way to provide automation around enabling/disabling services on the nodes, and upgrading/adding/removing services when new products/customers are configured and old ones removed. I think that is much easier if I don't approach it from the perspective of having the F5 itself provide the automation.

 

 

- ZJ