Feature request, timeout/sleep in configuration jobs

We would like to see an option in the Configuration jobs where we could pause the job for a while as some commands cannot be run instantly

For example if we convert an addressed TM/LB vServer to TM/CS vServer in the following steps:

1. Delete the original LB vServer holding IP address 123.123.123.123

2. Create CS vServer for IP address 123.123.123.123

3. Create non-addressed LB vServer, CS actions/policies and bind them to the CS) This sort of job fails as the the LB vServer still reserves the IP address when the CS vServer is trying to be created.

So if we could have something like:

1. Delete the original LB vServer holding IP address 123.123.123.123

2. Sleep/pause for n seconds

3. Create CS vServer for IP address 123.123.123.123

4. Create non-addressed LB vServer, CS actions/policies and bind them to the CS) This way we could run these conversions more reliable.

Alternatively we can split these in two jobs, but then we would need to enter variables twice in to the wizards.

Related:

  • No Related Posts

Leave a Reply