Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - NETWORK DISCOVERY DATABASE STRUCTURE, Руководство системного администратора

Страница: 182 / 374

182 ZENworks 10 Configuration Management System Administration Reference
n
ov
do
cx (e
n)
16
Ap
ril 20
10
20.2 Creating Deployment Stages
Deployment stages are optional; however, stages allow you to deploy an update one step at a time,
such as to a test group first, then to your managed devices.
If a failure occurs during the update
process, the process is halted. E-mail notifications can let you know when each stage has completed.
The following sections contain more information:
Š
Section 20.2.1, “Understanding Stages,” on page 182
Š
Section 20.2.2, “Creating and Populating a Deployment Stage,” on page 184
Š
Section 20.2.3, “Modifying the Stage Timeout,” on page 185
Š
Section 20.2.4, “Modifying Staging Behavior,” on page 186
Š
Section 20.2.5, “Modifying Reboot Behavior,” on page 187
Š
Section 20.2.6, “Modifying the Membership of a Deployment Stage,” on page 187
Š
Section 20.2.7, “Renaming a Deployment Stage,” on page 188
Š
Section 20.2.8, “Deleting a Deployment Stage,” on page 189
Š
Section 20.2.9, “Rearranging the Order in Which Stages Start,” on page 189
20.2.1 Understanding Stages
You can do the following with stages:
Š
Set them up for different devices or groups, such as for a test group, specific devices or device
groups, or all managed devices in the zone.
Š
Modify an existing stage’s membership.
Š Change the order in which the stages run.
Š
Rename and delete stages.
Š Specify the default timeout for a stage. When the timeout value is reached, the stage’s
deployment stops and an e-mail message is sent , if e-mail notification is configured. You can
cancel the deployment, or you can clear the error to restart the stage and reset the timeout. Or,
you can ignore all pending devices to trigger a stage progression (either automatic, or wait for
administrator action based on the setting).
Š
Specify the reboot behavior when devices complete the update: prompt a reboot, force a reboot,
or suppress rebooting.
Š
Specify how the update process is to advance through the stages:
Š
Automatically, with or without notification
Š
One stage at a time with notification when each stage is completed
Š
Bypass the configured stages and immediately apply the update to all devices
There are many reasons for creating deployment stages:
Š
Testing the update on certain devices before deploying it to your production environment
Š Including all Primary Servers in one stage so they can be updated at the same time.