pe.p.run (Sun N1 Service Provisioning System 5.1 Command-Line Interface Reference Manual)

Sun N1 Service Provisioning System 5.1 Command-Line Interface Reference Manual

`pe.p.run`

This command runs a plan. If there are plan prompt variables, it interactively queries the user for responses.

When you run a composite plan through the CLI, you must specify a set of targets, component versions, and variable sets for each subplan. See Appendix A, Input Types for further description of the syntax.

Table 10–8 Arguments and Result for the pe.p.run Command


Argument/Result		Syntax	Description
PID	[R]	ExecutionPlanID	The ID of the execution plan to run
tar	[R]	HostIDArrayArray	Individual hosts or host sets on which to run the plan and each of its subplans, ordered according to subplan prompts
comp	[O/R]	StringArrayArray	Component versions to install as a part of the plan and subplans. Versions are ordered according to component selectors within subplan prompts. Each referenced component must be represented in this list. Use the component version number, or "+" for default, "#" for recommended, and "-" for latest. Do not specify when there are no component versions.
vs	[O/R]	StringArrayArray	Variable settings to use with each selected component version. Use variable settings name, or "+" for default. Do not specify when there are no variable settings.
po	[O]	Boolean	True if only preflight should be run
pdp	[O]	Boolean	True if detailed preflight should be run; default false.
hr1	[O]	Integer	Limit number of hosts running at the same time; default set by server config file.
pto	[R]	TimeInterval	The maximum plan execution time
nto	[R]	TimeInterval	The maximum native call execution time
f	[O]	ReaderWrapper	Plan variables can be passed with a file or standard input; default is standard input
result		TaskID	The ID of the plan run

Example 10–1 Running a Plan With a Single Subplan, Component, and Variable Set

This example demonstrates a simple plan being run on one host.

Plan name: /test/test1
Host targeted by plan: masterserver
Variable set name: nors
Maximum time for plan execution: 30 minutes
Maximum time for native call execution: 10 minutes
Component versions to be used: default

For a single component and variable set, you do not need to surround the value with quotation marks.

./cr_cli -cmd pe.p.run -PID NM:/test/test1 -tar H:NM:masterserver  \
-vs nors -pto 30 -nto 10 -comp + -u admin -p admin

Example 10–2 Running a Plan With More Than One SubPlan, Component, and Variable Set

This example demonstrates a composite plan with two subplans.

subplan1
	install compA
	install compB
subplan2
	install compC
	install compD

Each subplan is run on a different host and uses two different variable sets for each referenced component.

Plan name: /test/test2
Hosts targeted by plan: masterserver and host2
Variable set names for subplan 1: nors and tmc
Variable set names for subplan 2: varset1 and varset2
Maximum time for execution: 30 minutes
Maximum time for native call execution: 10 minutes
Component versions to be used: default

./cr_cli -cmd pe.p.run -PID NM:/test/test2  \
-tar "H:NM:masterserver;H:NM:host2" -vs "nors,tmc;varset1,varset2" \
-pto 30 -nto 10 -comp "+,+;+,+" -u admin -p admin