Bug 1031784

Description of problem:

When creating groups - organizing very large inventories of hundreds of nodes, as an admin user you're often faced with grouping of servers into "management group", like Development, QA, Staging, Prod and even within Prod there may be parallel environments with hundreds of hosts each. 

When creating groups to reflect this, you're faced with creating groups of sub-services, such as SOA services, web services etc. for each of the super-seeding groups. To do this, using the UI you have no help. Out of 1000 platforms, you again and again have to remember the hosts that are part of the over-arching group you're working with Even worse, if more systems are added to that over-arching group you have a lot of editing to do. In many cases, the service/item name does not even reflect the hostname making it very hard to differentiate between them for selection.

WHAT IS NEEDED

Creating dynamic groups where group membership of the parent can be specified as a condition. 

When creating compatible groups, be able to restrict the number of items listed as items from another existing group. So if creating a group of SOA ESB services, it would only show the ESB services that can be found in a specific parent group.