CHAPTER 31

Deferring Deployment of Service Profile Updates
Thischapter includes the followingsections:
•DeferredDeployment of ServiceProfiles, page 469
•ConfiguringSchedules, page 472
•ConfiguringMaintenance Policies, page 482
•ManagingPending Activities, page 484

Deferred Deployment of Service Profiles

Somemodifications to a service profile or to an updating service profile template can be disruptive and require
areboot of the server. You can, however, configure deferred deployment to control when those disruptive
configurationchanges are implemented. For example, you can choose to deploy the service profile changes
immediatelyor have them deployed during a specified maintenance window. You can also choose whether
ornot a service profile deployment requires explicit user acknowledgement.
Deferreddeployment is available for all configuration changes that occur through the association of a service
profilewith a server. These configuration changes can be prompted by a change to a service profile, to a policy
thatis included in a service profile, or to an updating service profile template. For example, you can defer the
upgradeand activationof firmware through host firmware packages and management firmware packages,
suchas server BIOS, RAID controller, host HBA, and network adapters. However, you cannot defer the direct
deploymentof firmware images for components that do not use either of the firmware packages, such as Cisco
UCSManager, fabricinterconnects, and I/Omodules.
Deferreddeployment is not available for the following actions which require the reboot of a server:
• Initial association of a service profile with a server
• Final disassociation of a service profile from a server,without associating the service profile with a
differentserver
• Decommissioning a server
• Reacknowledging a server
• Resetting a server
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 469