Completion Types

1. Completion Types • Current Values • restartRequired • restartOccurs • logoffRequired • Issue • Need to differentiate between a restart that is required to continue, i.e. must be restarted before anything else can be done and a restart that can happen at any time prior to using the software installed. This differentiation is needed in CL2 when consumers of aggregations need to understand if they must restart in the middle of the deployment or can wait until all content units are deployed. • Proposal • Remove • restartRequired • Add • restartRequiredtoContinue - The restart is needed to complete the processing of the artifact, e.g. Locked file processing. • restartRequiredtoUse - The resource created as a result of this content unit can not be started without a restart, e.g. Windows registry entries

2. Requirements • Current • The combination of operation attribute on Requirement and the state attribute on ResourceConstraints defined in Requirement is used to determine when a requirement applies and for how long. • Valid operation values are: create, update, undo, configure, verifyConfiguration, verifyResults, repair, delete, install (which means create or update), uninstall (which means undo or delete) and none. • When operation is set to anything but none, it means the requirement must be met before processing the artifact that corresponds with the operation. • When operation is set to none, then there is no need to meet the requirement before processing any of the artifacts defined by the content element. • Valid values for state are: installed, usable, and none. • When state is set to installed, the requirement must be met in order to consider the deployed software installed at any point in time. • When state is set to usable, the requirement must be met in order to consider the deployed software usable at any point in time. • When state is set to none, then the requirement only applies during processing of the artifact associated with the specified operation. • Issue • The semantics are subtle and hard to follow. For example, to say that a requirement applies only during the install operation - which you might want to do for a requirement for temp space used only during artifact processing - you have to change state in each resource constraint to "none" in every constraint defined in a Requirement whose operation is set to "create", "update" or "install". • Not all combinations are valid • A value of none for both operation and state is invalid. • A value of anything but create, update or install for operation combined with a value of installed for state is probably not valid. • A value of anything but create, update, install or configure for operation combined with a value of usable for state is probably not valid. • Proposal • Remove state attribute and just add additional values to operation for this purpose. • Add the following enumeration value: • Use – this means that the requirement must be fulfilled in order to use the resource that will be created by this content unit, e.g. exec the program • installAndUse – this is the operation that support the requirements needed before install and must be maintained to use the software deployed. • Should be the default • Remove: • the delete enumeration value. Duplicate of uninstall • The none enumeration value. Not applicable with the state attribute removed.