This topic walks you through the process of organizing servers into a dynamic groups using a BMC BladeLogic Server Automation (BSA) feature called smart groups. It includes the following sections:
The following video demonstrates the process of creating smart groups and nested smart groups.
Smart groups are groups for which you define membership conditions based on object properties. You can create smart groups for most types of objects in BMC Server Automation, including servers, jobs, and depot objects. For example, you can define a condition saying a smart group contains all servers with an operating system of Windows.
Defining a dynamic collection of servers can be extremely useful. For example, you can define one group of servers with active RSCD agents running Windows 2008 and another group running Windows 2008 R2. Then you could use these groups as dynamic targets when you deploy patches for each of those operating system versions.You can also create nested smart groups, but only for server groups. By nesting smart groups, you can define hierarchies based on object properties. For example, if you create a parent smart group that contains Windows servers, you can create two child smart groups for Windows servers that have Windows 2008 and Windows 2008 R2. You can further organize those servers using other server characteristics. The walkthrough described below defines geographic locations for servers. For a demonstration of the 8.7 functionality, see How to organize assets with nested smart groups.
Make sure you have the BSA Console installed on your workstation, and that you've got the appropriate level of permissions to create smart groups.
For this walkthrough, you log on as BLAdmin, the default superuser for BSA. Note that in live deployments, BMC recommends that you grant access based on roles with a narrower set of permissions.
This walkthrough demonstrates how to create a smart group that contains all Windows servers with an agent that is running.
|Step||Example screen (click to enlarge)|
In the Servers folder, select the location where you want to create a smart group, right-click, and select New > Server Smart Group.
A dialog opens that lets you define the rules for membership in the smart group.
For Name, enter a name for the smart group. In this case, we call the smart group Windows. Optionally, enter a description.
In the bottom half of the dialog, there is a row that represents a rule for smart group membership. Using that row, take the following actions:
Create another rule by taking the following actions:
|5||Click Finish. A smart group named Windows appears. If you expand it, the smart group shows all servers with a Windows operating system and a function RSCD agent.|
This walkthrough demonstrates how to create multiple levels of nested server smart groups. First we create nested smart groups for Windows 2008 and Windows 2008 R2. Then we create another level of nesting for the geographic location of each server.
|Step||Example screen (click to enlarge)|
Create a nested smart group for Windows 2008 by selecting the Windows smart group we created above. Then take the following actions:
Create another nested smart group for Windows 2008 R2 by selecting the Windows smart group. Then take the following actions:
|3||Expand the two smart groups you just created. You can see how the Windows smart group contains 7 servers. The two smart groups you just created contain 3 and 4 servers, which are subsets of the servers contained in the Windows smart group.|
Create a nested smart group that sorts servers by geographic location by taking the following actions:
Create another nested smart group that sorts servers by geographic location.
|6||Expand the two smart groups you just created. You can see how the Windows 2008 R2 smart group contains 4 servers. The two smart groups you just created contain 3 servers and 1 server, respectively. They are subsets of the servers contained in the Windows 2008 R2 smart group.|
You have now learned how to set up the rules necessary for using smart groups.You also learned how to use smart group functionality to create dynamic hierarchies of servers, called nested smart groups.
Now that you know how to create smart groups, you can move on to provisioning servers with BSA.