Rudder

I'm not sure if I understand what you mean. I will provide a user case. Let's take the groups I mentioned above: Ubuntu Servers, Ubuntu 10 Servers, Ubuntu 12 Servers.

We use different configurations on Ubuntu 10 Servers and Ubuntu 12 Servers, like software repositories. However, most configurations are suitable for both Ubuntu 10 and Ubuntu 12 Servers.

At the moment I can do two things to accomplish this. Or I create three separate groups, Ubuntu Servers, Ubuntu 10 Servers, Ubuntu 12 Servers, based on regexp. Or I just create two separate groups, Ubuntu 10 Servers, Ubuntu 12 Servers, and bind those two groups to one directive.

It would be nice if I was able to create two groups, Ubuntu 10 Servers, Ubuntu 12 Servers, based on regexp. And then make an Ubuntu Servers group which contains both groups.

Vincent MEMBRÉ wrote:

So you need a way to create a super group which reference other groups?

Maybe we can handle that by making the group categories as rule target.

The category would targets all nodes contained in its childs.

That would fit well in the webapp, and should be easy to understand.

What do you think about that ?

I'll pitch in here and say I think this would work, yes. This also has the additional benefit that categories and groups are already represented hierarchically which is a useful visualization for groups/subgroups.

Another way would be to add query criteria like "is member of".

What is the status of this ticket? Can someone look at it?

I agree with the categories being targets in rules. That would make a lot of sense, and would make things easier.

Something related to that topic, even if not what is wanted here: #4505 "Allow exclusion and composition of groups to gain more flexibility in Nodes targetted by a Rule"

Would be still nice to have this. CFEngine can do it actually.

Yes Very nice. I'm think add in the Filter of dynamic Group choice : Rudder Group Name (== / !=).

With this feature, response of make group intersection on applied rule can have solution.