Elements Modified By Introduction of the lockHost Step (What's New in the Sun N1 Service Provisioning System 5.2 Update 2 Release)

What's New in the Sun N1 Service Provisioning System 5.2 Update 2 Release

Elements Modified By Introduction of the `lockHost` Step

With the introduction of the lockHost step, several elements described in the Sun N1 Service Provisioning System 5.2 XML Schema Reference Guide gain a new attribute: the requireLocking attribute. The requireLocking attribute is designed to safeguard a component against use in an unlocked environment.

Existing Element (Child of)	New Attribute	Description
`installSteps` (`installList`) `uninstallSteps` (`uninstallList`) `control` (`controlList`)	requireLocking	An optional attribute indicating if the component `install`, `uninstall`, or`control` block can be used in an unlocked plan. The default value is `TRUE`. Plans using use this component block must lock the host for the duration of the component installation, uninstallation, control or snapshot operations. Locking can be achieved by implicit plan locking or by explicit locking with the `lockHost` step.

Existing Element (Child of)

New Attribute

Description

installSteps (installList)
uninstallSteps (uninstallList)
control (controlList)

requireLocking

An optional attribute indicating if the component install, uninstall, orcontrol block can be used in an unlocked plan.

The default value is TRUE.

Plans using use this component block must lock the host for the duration of the component installation, uninstallation, control or snapshot operations.

Locking can be achieved by implicit plan locking or by explicit locking with the lockHost step.