Project

General

Profile

Actions

User story #8247

closed

Changing hostname or policy server of one node force regeneration of all rules on the node

Added by François ARMAND almost 8 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
2
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

When the hostname or policyserver id of a node, all rules on the node get updated, forcing all nodes with these rules to have their promise regenerated.

The idea seems to be that "we can't know where the variables were used, so let pessimistic (but correct) and force update everywhere".

I'm pretty sure that:
- we could check if really, a rule was using them
- only update theses rules

Because in the real life, node properties are very rarelly used in user directives. So in general, that change only matter for system rules (and likelly only one of them).
It is tampered by the fact that node properties change rarely, but nonetheless, it seems to be a major optimisation to have.

On a higher level, it's stupid that a local change to a node force update EVERYWHERE, because expected reports are by rule and not node.

So: make more fine grained check about what rules are impacted by node properties change.


Related issues 2 (0 open2 closed)

Related to Rudder - User story #8248: Without config changes, two promise generation may lead to differently ordered value in promisesRejectedFrançois ARMANDActions
Related to Rudder - Bug #5316: If policy server hostname changes, the generated promises never take into account the new valueRejectedActions
Actions #1

Updated by François ARMAND almost 8 years ago

  • Related to User story #8248: Without config changes, two promise generation may lead to differently ordered value in promises added
Actions #2

Updated by François ARMAND almost 8 years ago

  • Related to Bug #5316: If policy server hostname changes, the generated promises never take into account the new value added
Actions #3

Updated by François ARMAND almost 8 years ago

  • Status changed from In progress to Rejected

As explained, marking that one as duplicate of #1411

Actions #4

Updated by François ARMAND almost 8 years ago

  • Is duplicate of Bug #1411: Node (hostname,policyserver,...) modification should trigger promises regeneration added
Actions #5

Updated by François ARMAND almost 8 years ago

  • Status changed from Rejected to New

My bad, the one to close is #8046

Actions #6

Updated by François ARMAND almost 8 years ago

  • Is duplicate of deleted (Bug #1411: Node (hostname,policyserver,...) modification should trigger promises regeneration)
Actions #7

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #8

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #9

Updated by Jonathan CLARKE over 7 years ago

  • Subject changed from Changing hostname or policy server of one node force update of all rules on the node to Changing hostname or policy server of one node force regeneration of all rules on the node
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #17

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #18

Updated by Benoît PECCATTE almost 7 years ago

  • Tracker changed from Bug to User story

Requalifying as user story since everything is working properly, it's just that it could be better

Actions #19

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #20

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #21

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #22

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #23

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #24

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #25

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #26

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #27

Updated by François ARMAND about 6 years ago

  • Status changed from New to Rejected

This is not the case anymore in 4.1 and above: we do calculate preciselly for each node if its configuration changed, and only regenerate policies if it is the case.

Actions

Also available in: Atom PDF