User's Manual
Table Of Contents
- Contents
- About This Guide
- Chapter 1
- Active System Manager Overview
- Chapter 2
- Getting Started
- Chapter 3
- Account Management
- Chapter 4
- User Profile Management
- Managing Security Functions
- Managing Groups
- Defining Permissions
- Modifying Permissions
- Managing Authentication Repositories
- Chapter 5
- Inventory Management
- Understanding Resource Modeling
- Building a Standard Active System Manager Inventory
- Configuring Discovery Setup
- Running Discovery
- Using Resource Types
- Using Resource Instances
- Building Resource Instances
- Modifying Core Properties for Resource Instances
- Modifying Resource Instance Resource Availability Dates
- Modifying Resource Instance Interfaces
- Displaying the Resource Availability Calendar View
- Deleting Resource Instances
- Setting Inventory Parameter Values
- Resolving Resource Dependencies
- Using Resource Interface Types
- Linking Resources
- Importing Inventory
- Importing Connectivity
- Exporting Connectivity
- Managing Resource Pools
- Managing Maintenance Windows
- Managing Virtual Resources
- Chapter 6
- Firmware Management
- Creating Active System Manager Software Repositories
- Updating Dell Chassis Firmware from the Operations Center
- Updating Dell Server Firmware
- Updating Dell Blade/Rack Servers Firmware from the Operation Center
- Updating Dell Blade/Rack Servers Firmware from an Active Session
- Updating Dell Blade/Rack Servers Firmware Using the Attach Server Profile Virtual Operation
- Updating Dell Blade/Rack Servers Firmware through an Orchestration
- Updating Dell Blade/Rack Servers Firmware Using the Attach Server Profile Custom Operation
- Minimum Firmware Versions for Active System Manager Components
- Chapter 7
- Server Template and Profiles
- Creating a Server Template
- Editing a Server Template
- Adding or Editing BIOS Information on a Server Template
- Adding or Editing RAID Information on a Server Template
- Adding or Editing Firmware Settings on a Server Template
- Adding or Editing Networks Settings on a Server Template
- Naming Conventions when using Orchestrations
- Server Profiles
- Chapter 8
- Using Inventory
- Chapter 9
- Repository Management
- Chapter 10
- Network Management
- Chapter 11
- Template Management
- Template Types
- Working with Templates
- Creating New Templates
- Saving Templates
- Changing Template Ownership and Permissions
- Opening Templates
- Closing Templates
- Deleting Templates
- Managing Template History Details
- Filtering Templates
- Validating Templates
- Importing Templates
- Exporting Templates
- Attaching a Template Image
- Scheduling Templates
- Archiving Templates using the Templates View
- Restoring Archived Templates
- Updating Templates using the Template Editor
- Viewing and Modifying Template Properties
- Adding Resource Types
- Setting Resource Type Properties for Scheduling
- Deleting Resource Types
- Adding Resource Types Based on Manufacturer Only
- Adding Resource Instances
- Modifying Resource Properties
- Deleting Resource Instances
- Defining Provisioning Policies
- Supporting Layer 2 Switching
- Using Annotations
- Updating Templates using the Link Editor
- Associating an Orchestration Workflow with Templates
- Chapter 12
- Session Management
- Introducing the Sessions Perspective
- Working with Running Sessions
- Scheduling a Session Using Templates
- Creating an Instant Session
- Opening Sessions
- Opening the Session Editor
- Using the Sessions Calendar
- Viewing Session Properties
- Editing Default Session Properties
- Assigning and Changing Session Ownership
- Canceling Sessions
- Deleting Sessions
- Purging Sessions
- Rescheduling Sessions
- Managing Session Links
- Handling Link Preemption
- Managing Session Resources
- Associating Scripts to Sessions
- Archiving Sessions
- Supporting Layer 2 Switching
- Saving Sessions
- Configuring Session Notifications and Reminders
- Starting and Stopping ASAP Rescheduling
- Managing Virtual Resources
- Chapter 13
- Orchestration Management
- Chapter 14
- Working with Test and Script Execution
- Chapter 15
- Reports
- Chapter 16
- Settings
- Chapter 17
- Dashboard
Understanding Orchestration
Orchestration Management 13-3
Orchestration Types
The Active System Manager software facilitates the template owner with the ability to specify the
Orchestration on the basis of three different reservation states where Orchestrations can be executed.
Table 13-1 lists and describes the various Orchestration types based on reservation states.
Table 13-1 Orchestration Types
Orchestration Type Description
Setup The Setup Orchestrations can be defined per template, and each template can
contain a maximum of one Setup Orchestration. When a template with a Setup
Orchestration is scheduled, and when the session attains a Setting Up
reservation state, the Active System Manager software execution service
implements the Setup Orchestration automatically. The custom operations
defined in the Setup Orchestration steps run one after the other; thus, avoiding
manual intervention.
During a Setup Orchestration, the following steps effect in sequence:
1. The devices are powered on.
2. The device connectivity is checked.
3. Resource-level scripts are executed.
4. Reservation scripts are executed.
5. The Setup Orchestration is executed.
Note: Setup Orchestrations are executed after the generation of reservation
scripts.
On-demand The On-Demand Orchestration enables the ability to initiate an Orchestration
execution in a running Active System Manager session, as needed.
On-Demand Orchestration executes one at a time in the running session. Before
doing so, the Active System Manager software validates the Orchestration for any
missing or removed device in the template. For more details, see the “Executing
Orchestration” section on page 13-16.
Teardown The Teardown Orchestration can be defined per template where each Template
can contain a maximum of one Teardown Orchestration. When a template with a
Teardown sequencing is scheduled and goes into a Clean Up state, the Active
System Manager execution service implements the Teardown Orchestration as
per the custom operations defined in the Orchestration steps.
During a Teardown Orchestration, the following steps effect in sequence:
1. Teardown Orchestration is executed.
2. Reservation Teardown scripts are executed (default or user-defined, as
available).
3. Resource-level Teardown scripts are executed.
4. Connected devices are released.
5. On devices are powered off.
The template owner has the ability to specify Orchestration on the basis of
reservation states for the custom Orchestration constructs, using a drag-and-drop
method.
Note On creation, all Orchestrations are of the On-Demand Orchestration type. However, you can easily
change them into a Setup Orchestration or a Teardown Orchestration, and vice-versa, in the
Orchestration view.