Skip to end of metadata
Go to start of metadata

Taskable Resources

Resources Categories:

  • Information Resources (managed by the Data Management subsystem)
  • Taskable Resources (managed by the CEI subsystem)

A Taskable Resource is defined as a special category of resource that can be scheduled, executed, monitored and controlled. Each taskable resource has an agent that can control the resource. There are special realizations of taskable resources that all share the common elements.

Properties:

  • Can be started and stopped.  Started/stopped may have specific connotations such as deployed/termination, registered/unregistered.
  • Are monitorable.
  • Can be sent a control message.

Realizations/Subtypes:

  • Process (with subtypes task-process and service-process)
  • Operational Unit
  • HA Service

The following categorization of taskable resources exist:

  • Process
    • Task process
    • Service process
  • Operational Unit
    • Execution Engine
      • Capability Container
    • Complex Operational Unit
  • HA Service
    • A set of operational units that together provide a higher level service (complex operational unit)
    • A set of operational units that form an EPU (complex operational unit that is providing an infrastructure component but is managed nonetheless)
    • Application Service
    • Agent

Figure 1 shows these categories of taskable resources and their dependencies. All taskable resources are managed by the CEI.

Figure 1. Taskable Resource Types and Dependencies (OV-2)

Management Activities

The following list defines the high level management activities for taskable resources, as performed by the CEI

  • Planning
  • Provisioning
  • Controlling
  • Fault Monitoring and Compensation
  • Registration 

Figure 2 shows a decomposition of the Common Execution Infrastructure services. The core element is the Computation Planner, which receives Service Agreement Proposals from other services in the OOI that require computation. These Service Agreement Proposals contain the computation processing request as well as the exact conditions under which the plan should be executed. The Computation Planner enters a negotiation and agreement process with the requester. Upon agreement, the Computation Planner determines a Processing Plan and initiates the processing by triggering the Provisioner. The Provisioner brings actual Operational Units into being by interfacing with the specific host execution environment. The Computation Controller is the entity responsible for enacting the processing plan within the boundaries of the plan and the service agreement. It provides status about scheduled and ongoing computations to the Exchange for routing to the service requester. A Fault Monitor and Compensator is an independent entity monitoring any ongoing process and providing Fault Analysis information to the service requester.

Figure 2. Common Execution Infrastructure Services for Taskable Resource Management (OV-2)

Figure 3 shows a sequence diagram of how an operational unit gets provisioned through an interplay of Computation Planner, Provisioner and Controller and the newly provisioned Operational Unit.

Figure 3. Provisioning an Operational Unit (OV-6)

Labels

read-cei read-cei Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.