Table of Contents
Oracle VM makes strong use of a job operation framework that supports a flexible approach to the configuration of physical and virtual objects. Oracle VM Manager maintains an accurate and consistent view of the virtualization environment while users perform separate and simultaneous jobs. A configuration change on any individual object type within Oracle VM Manager is considered to be a job. Since Oracle VM allows for incredibly granular configuration of each object type within the environment, some configuration changes may affect more than one object type within Oracle VM Manager. This means that some configuration actions, such as the creation of a clustered server pool, may consist of many consecutive jobs, as each different object and the relationships between them are created, updated or removed within the Oracle VM Manager database.
Therefore an operation may consist of multiple jobs. This behavior is distinct from the behavior of jobs within Oracle VM prior to version 3.3.x, where whole operations were often treated as a single job. Examples of operations that translate to a number of different jobs are presented in Table 8.1, “Job Example”.
Table 8.1 Job Example
Operation | Jobs |
|---|---|
Create clustered server pool | Create server pool |
Create Cluster Heartbeat Device | |
Create Cluster | |
Create virtual machine [a] | Create Virtual Machine |
Add Virtual Machine to Server Pool | |
Create Virtual Disk | |
Add Virtual Disk to Virtual Machine | |
Create VNIC on Virtual Machine | |
[a] The number of jobs for this action may vary depending on the configuration steps that you perform. The example provided here is merely indicative of how a number of jobs can be triggered by performing a single operation.
A job begins when you make any change in Oracle VM Manager. Each change you make appears in the Job Summary pane on the Jobs tab as a discrete operation. Job operations can be comparatively minor actions, such as renaming a virtual machine. Operations may also have a wider scope, such as the creation of a new network or storage device. Performing any of these actions changes the configuration of Oracle VM Manager. When a new job is started, information about the job is displayed in the Job Summary pane at the bottom of the management pane to show the job's progress.
Furthermore, some jobs may be triggered internally within Oracle VM Manager by particular events, as a result of internally set recurring job operations, or as child jobs that are triggered as a subset of larger job operations initiated by a user. There is no distinction between a job resulting from a user action or from an internal event within Oracle VM Manager.
A single job can contain one or many individual operations. When a job is in progress, a yellow lock appears to the left of the resources included in the job in the Oracle VM Manager Web Interface.
Unlike previous releases, Oracle VM Manager 3.3 handles jobs asynchronously. This means that when an operation using the Oracle VM Manager Web Interface or Oracle VM Manager Command Line Interface triggers one or more jobs, an error may not be returned immediately if a job fails. It is important to monitor job progress when you perform an operation to check that all jobs complete successfully.
The following sections describe jobs, and how resources are locked and released at the start and conclusion of each job, and how to manage jobs.