iRule for Priority Group Activation... with a twist
Hey guys, I have odd scenario. I have an application that requires an primary/secondary setup for pool members. Easy enough, I could use priority group activation, right? Here's the twist: when the failover occurs, the available member for the pool must REMAIN on the secondary until the application owners have re-synced their application, and we coordinate a reset of everything. I know... don't get me started talking about how bad of a design this is... but it is what it is. So, even if the primary server begins to pass health checks, I need the traffic to remain on the secondary server until some coordinated time when they have reset their app and we can direct traffic back to the primary.
I found a post where Hoolio suggested this iRule for a failover scenario:when HTTP_REQUEST {
Check if the VS default pool has any active members
if {[active_members $default_pool]}{
pool $default_pool
} else {
pool sorry_pool
}
}
This should be easily modified for what I need... I need a way to ensure that I fall out of the loop when the members of $default_pool are <1, and then a way to reset everything when the app guys are ready to set everything back to the primary. Any suggestions? Thanks in advance, as always.