Grass Valley SiteConfig v.2.1 - Manual (Page 70)

Understanding software deployment concepts
About deployment groups
Deployment groups contain a set of devices that receive the software contained in a software package.
Each device within the system can only belong to one deployment group. In order to deploy software
to devices using SiteConfig, you must add one or more deployment groups to the "All Deployment
Groups" node. Once you create a deployment group, you must then choose one or more devices to
belong to that group based on criteria you determine. Some examples of different ways you can
create deployment groups are -
• Devices of the same type. For example, a group of all K2 Media Servers in a K2 SAN
• Devices that might need to have the same versions of a package deployed. For example, all K2
Media Clients on a K2 SAN
• Devices that have software deployed from the same product family. For example, all Aurora
devices
• If you have several packages that are compatible with each other, you can create a deployment
group of all devices that must be upgraded together to maintain compatibility
• You can also create a deployment groups based on how you manage the sequence of software
deployment. For example, you can create a group for your servers so that they can be upgraded
first with software packages, then a separate group for clients so that you can add the client
software packages and upgrade separately.
• You can create a deployment group to test a particular version of a software package on a set of
devices.
Once you create a deployment group, you then add software packages to the group. SiteConfig
identifies all devices within that group to which packages are deployed. This identification is based
on the roles specified for the device in SiteConfig and the roles specified in the packages.
The Default deployment group is a special group for devices. This deployment group allows
SiteConfig to automatically carry out software deployment operations on devices that do not belong
to any other deployment group. When you initiate a Check Software operation, SiteConfig matches
software packages in the package store with software on devices. If a device that does not belong
to a deployment group has a match, SiteConfig automatically places the device in the Default
deployment group. In addition, you can add managed packages and deploy software to devices in
the Default group. SiteConfig generates appropriate deployment tasks for devices in this group when
you initiate the Check Software operation and when you add packages to the Default group. However,
SiteConfig does not allow you to add devices to this group. This is because you should set up your
own deployment groups based on your own logical grouping of devices within your system.
About managed software and tasks
Managed software is software that can be installed, uninstalled, and reinstalled by SiteConfig. A
managed package is a *
.cab file that contains one or more installers ( *.msi files) for managed
software that can be deployed to a device. It also contains a description of the roles deployed by the
installer and types of devices that can have the software deployed to them. In order to see what a
managed package contains, you can select any package listed within the Managed Packages area in
70 SiteConfig 2.1 User Manual 11 October 2011
Working with software deployment