2.2 Provisioning Actions and History

The following information is included in this section:

2.2.1 What are Provisioning Actions?

The provisioning operations you perform in PlateSpin Orchestrate are recorded as “actions.” For example, in the PlateSpin Orchestrate Development Client main menu:

  • A VM Host Discovery action is initiated if you select Provision > Discover VM Hosts and Repositories and then you select a provisioning adapter in the Discover VM Hosts and Repositories dialog box.

  • A VM Discovery action is initiated if you select Provision > Discover VM Images and then you select a provisioning adapter in the Discover VM Images dialog box. An action is specified for each Repository you specify.

  • A Migrate action is initiated when you perform the migration of a Virtual Machine (VM).

2.2.2 How Actions Are Displayed in the Development Client

Depending on the Grid object you select, an Action History tab is displayed in several views of the Orchestrate Development Client.

Action History in Monitor Views of the Development Client

You can see the Action History tab in the VM Hosts monitor view if you select a migrating VM:

Figure 2-1 VM Hosts Actions

Two action-specific menu selections are available if you right-click an action in the action history table:

  • Show Log opens the provision log for the VM

  • Cancel Action cancels the selected active action

The action history table is updated at the same time the polling view is updated.

NOTE:The format of action history table is similar in the Provisioner monitor view and in the Users monitor view.

If the Include Audit Database check box is selected in this view, the action status is not polled. Click the refresh icon to fetch and display fresh data.

NOTE:The Orchestrate Server must be connected to an audit database for the Include Audit Database check box to be available. This behavior is the same in the Job monitor view.

Action History in Admin Views of the Development Client

Action history is displayed in other Grid object admin views of the Development Client:

  • User object

  • Resource object

  • Repository object

The following illustration shows an example of action history in the Repository admin view:

Figure 2-2 Repository Action History

The table below defines some of the column names and the values that can populate those columns in the action history table:

Table 2-1 Action History Table Columns

Column Name

Purpose

Action ID

A unique integer value used to identify the action.

Parent Action ID

If a value is displayed, the action is a child of this parent, identified with a unique integer value.

Action Name

Specific to the action being invoked.

Target ID

The identifying string of the object where the action is to occur.

Status

Displays the status of this action (specific to the action being invoked). Possible values in this column include:

  • Started

  • In Progress

  • Success

  • Failed

  • Canceled