Tasks

• Design and model development
  • Model for operational node life-cycle
  • Design node resource agent
  • Design process resource agent
  • Design block resource agent
  • Design provisioner interactions for block agent
  • Design scheduler interactions for block agent
  • Design controller/supervisor interactions for block agent
  • Concept model for Elastic Processing Unit (EPU) that drives elastic scaling and provides high availability
• Implementation and integration
  • Node resource agent and OS integration
  • Process resource agent and OS process integration
  • Block resource agent
  • Provisioner interactions/integration and block agent: Provisioning of AMI instances via messaging
  • Scheduler interactions/integration and block agent
  • Controller/supervisor interactions/integration and block agent
• Load and performance testing of message broker cluster
  • Create benchmark framework
  • Create load and performance tests

Architecture

The OV2 diagram below shows the main operational nodes inside and outside the Cloud Provisioning Environment (CPE) and their dependencies (needlines). This picture shows responsibilities and dependencies. The main entities are Scheduler, Provisioner, Controller, Fault Monitor.

Explanation:

• The Scheduler is the planner and decision maker. It subscribes to processing requests of a specific type: Provision operational units. Based on an understanding of system constraints, policy rules, available resources and other context, it determines a Processing Plan.
• The Controller/Supervisor has executes the Processing Plan. It represents a smart executive of the plan and has competency to adapt the plan if needed within bounds. It makes sure the plan gets executed and controls the resource. Plan execution might involve delegating parts of the plan to entities within its control (from the resource to subordinate schedulers/controllers).
• The Provisioner is the factory of the Operational Unit resource. It is under the control of the Controller/Supervisor.
• The Fault Monitor is observing the Control of the resource by the Controller/Supervisor. It detects failures and suggests mitigation actions to the Controller/Supervisor.

Types of resource control:

• Direct command: The Controller provides a sequence specific commands to the resource
• Delegation of plan: The Controller provides a resource specific plan and supervises the execution of the plan.
• Execution of preloaded plan: The Controller triggers the execution of preloaded plans within the resource

Core resource life cycle states:

• Startup: The initial state of a resource when coming to life before the first contact with its environment.
• Uninitialized: The resource has registered with its creator (the factory) and the immediate execution environment.
• Initialized: All steps have been successfully complete to initialize the resource, and notification has been sent to the creator. Initialization includes contextualization and also initialization of required resources, if applicable.
• Operational: Resource capabilities are available to the system.
• Paused: Resource capabilities are not available to the system but the operational state is preserved.

Basic Understanding

• A deployable type is an assembly plan (configuration specification). Bringing an operational unit to being can follow two main pathways: (a) Provide a virtual machine image to be deployed, (b) use a base image and assemble using a config management system