User story #4505
closed
Allow exclusion and composition of groups to gain more flexibility in Nodes targeted by a Rule
Description
As of Rudder 2.9, you can only select Groups to target from a Rule.
The result is that all Nodes from those groups will be targetted by that Rule. (union of all nodes from these groups)
This is nice and easy to use but it can get very complicated
- When you want to exclude some nodes from a group, you need to create a very complicated group ( exclusion of Nodes )
- You want to apply a Rule on Nodes that checks both criteria, you need also to create a specific group (intersection of nodes)
To answer this, we need to change how we apply a Rule to a group a nodes by adding more flexibilty and composition.
Here is our plan to solve it completely;
- Add backend for that behavior #4506
- Modify current Rules screen to integrate Rule composition #4507
- Add count of matching nodes under the boxes
- Add "(double down arrow) Advanced options" link under green and red boxes, that "rolls down" a greyed out section that has just one option originally, "Combine these groups by < > Union < > Intersection"
- Add -> arrows to the left of green and red boxes so you can select groups in the tree, then click the ->
Some other ideas can come with this ( organisation of page, list of Nodes ....) but they will come in another issue.
To complete this, at least steap 1, 2 and 3 needs to be completed
Updated by Jonathan CLARKE almost 11 years ago
Vincent MEMBRÉ wrote:
Here is our plan to solve it completely;
- Add backend for that behavior #4506
- Modify current Rules screen to integrate Rule composition #4507
- Add count of matching nodes under the boxes
- Add "(double down arrow) Advanced options" link under green and red boxes, that "rolls down" a greyed out section that has just one option originally, "Combine these groups by < > Union < > Intersection"
- Add -> arrows to the left of green and red boxes so you can select groups in the tree, then click the ->
Some other ideas can come with this ( organisation of page, list of Nodes ....) but they will come in another issue.
To complete this, at least steap 1, 2 and 3 needs to be completed
Vincent, this user story will only address 1, 2 and 3 therefore (minimum = scope of the user story). Please create other tickets for 4 and 5 and the other ideas, and they will be prioritized accordingly.
Updated by Jonathan CLARKE almost 11 years ago
While working on this, please fully check functionality and appearance on the major browsers (Firefox, Chrome, IE and Opera).
Updated by Vincent MEMBRÉ almost 11 years ago
- Status changed from 13 to Pending release
Updated by Vincent MEMBRÉ almost 11 years ago
- Subject changed from Allow exclusion and composition of groups to gain more flexibility in Nodes targetted by a Rule to Allow exclusion and composition of groups to gain more flexibility in Nodes targeted by a Rule
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.0~beta1, which was released today.
Check out:
The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000084.html
The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Nicolas CHARLES over 9 years ago
- Related to Bug #7108: Rules are not serialized correctly anymore added