Actions
User story #14333
open
Remote run should optionnaly honor splay time in async mode
Added by François ARMAND almost 6 years ago. Updated about 4 years ago.
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
Fix check:
Regression:
Description
On a big infra, asking for a remote run trigger the run every where at once. We should honore splay time on nodes for remote run in async mode. Or even better: we should had an option to ask to the node to honore it.
Updated by François ARMAND almost 6 years ago
- Related to Bug #14330: By default, no group are supervised and new group are not supervised added
Updated by François ARMAND almost 6 years ago
- Related to deleted (Bug #14330: By default, no group are supervised and new group are not supervised )
Updated by François ARMAND almost 6 years ago
- Related to Bug #14331: Trigger agent update and run after policy server has finished policy generation added
Updated by Benoît PECCATTE almost 6 years ago
Complying with a splay time means waiting for it, ie not running remote run.
Updated by François ARMAND over 5 years ago
- Target version changed from 5.0.7 to 5.0.9
Updated by Benoît PECCATTE over 5 years ago
- Subject changed from Remote run should honore splay time to Remote run should honor splay time
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 52
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.9 to 5.0.10
- Priority changed from 52 to 51
Updated by François ARMAND over 5 years ago
- Subject changed from Remote run should honor splay time to Remote run should optionnaly honor splay time in async mode
- Priority changed from 51 to 50
Updated by François ARMAND over 5 years ago
I'm setting to "major" because for the given use case (ie big infra), it may really be disruptive.
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
- Priority changed from 50 to 49
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 49 to 47
Updated by Alexis Mousset about 5 years ago
- Tracker changed from Bug to User story
- Severity deleted (
Major - prevents use of part of Rudder | no simple workaround) - Priority deleted (
47)
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset almost 5 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by Benoît PECCATTE over 4 years ago
- Target version changed from 5.0.18 to 6.2.0~beta1
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.2.0~beta1 to 6.2.0~rc1
Updated by François ARMAND about 4 years ago
- Target version deleted (
6.2.0~rc1)
Actions