H3C Technologies H3C Intelligent Management Center - Manual (Page 492)

478
Defining specific services
Defining the software deployment service
1. xxxxxx_Image_Deploy_Builder.xml file format:
<?xml version="1.0"?>
<definition> <!—note 1>
<action name="deploy_image"> <!—note 2>
<step> <!—note 3>
<command name="deploy_image" description="download image through TFTP"/>
<!—note 4>
</step>
</action>
<action name="set_device_boot"> <!—note 5>
<step> <!—note 6>
<command name="get_board_number" description="Get board number which current
image is located through CLI"> <!—note 7>
<result name="board_number"> <!—note 8>
<parser parserName="CleanupParser" parserRet="board_number"
parserScript="cleanupBoardNumber"/> <!—note 9>
</result>
</command>
</step>
<step>
<properties>
<!—note 10>
<property name="board" refer="board_number"/> <!—note 11>
</properties>
<command name="set_device_boot" description="set OS boot order through CLI"/>
</step>
</action>
<action name="delete_image"> <!—note 12>
<step>
<command name="delete_image" description="delete specified image"/>
</step>
</action>
</definition>
Note 1: Action definition label in fixed format.
Note 2: Action name. All the following software deployment steps are performed based on this name.
Note 3: Step. Each action can have multiple steps, which are executed in turn.
Note 4: Commands required for this step. Define all commands in the xxxxxx_Builder_Script.xml file.
Each step can consist of multiple commands, which are executed until one of the commands is executed
successfully. For example, if you set to download configuration files through TFTP and display
configuration files at the CLI, and the first command is successfully executed, the second command is not
executed.
Note 5: Action name, which is used to define the set_device_boot action.
Note 6: Get the board number.