Skip to end of metadata
Go to start of metadata
Purpose of this document
This page describes the deliverables from the Common Execution Infrastructure subsystem during Release 1 Iteration 2, structured by component.

The Common Execution Infrastructure subsystem provides an execution environment for system and user processes that enables reliable execution and scales to demand.

The Common Execution Infrastructure subsystem contains three components.

Execution Engine Catalog & Repository

This component maintains references to registered execution sites and virtual compute node configuration packages. An important responsibility of this component is to provide the tools necessary for bringing those configurations 'to life' as instantiated compute nodes, also known as 'contextualization'.

Status

  • CIDEVCEI-63 - Added two new REST operations to the context broker to make it easier to integrate client adapter into Python capability container.  See documentation.
  • CIDEVCEI-62 - Initial VM image with container (COI/CEI collaboration).

Next actions

  • Enhance VM work from this iteration to keep up with the progress in the EPU components.
  • Make the context agent (runs inside VMs) more robust in the face of a lack of networking access (should try to repeat contextualization for a while to reduce errors when the lack of networking access is just transient).

Jira Issues

(login required to see this, otherwise you will probably see "jiraissues: Error on line 1")

jiraissues: Unable to determine if sort should be enabled.


Elastic Computing Services

This component provides scheduling, provisioning, and monitoring services to maintain a balanced deployment of virtual compute nodes at one site.

Status

  • CIDEVCEI-61 - Evaluated Nimbus/VMware integration costs.  Unsure where this is going in the future.

Next actions

  • Find out what VMware requirements/plans are.

Jira Issues

(login required to see this, otherwise you will probably see "jiraissues: Error on line 1")

jiraissues: Unable to determine if sort should be enabled.

Resource Management Services

This component establishes global and standard models for the operational management (monitor & control) of stateful and taskable resources. It is the point of integration with the COI.

Status

  • CIDEVCEI-65 - Codified the CEI design here.
  • CIDEVCEI-66 - Documented CEI API designs, exact message contents, and more here.
  • CIDEVCEI-67 - This relies on previous bullet, expected to have more time for beginning to code more than the provisioning API (see next bullet) but still began a bit on code scaffolding, learning Magnet, etc.
  • CIDEVCEI-64 - Implemented an API that internal to the EPU's "Provisioner" component, it coordinates IaaS and Context Broker activities.

Next actions

  • Code initial feature-full version of Provisioner.
  • Code initial feature-full version of EPU Controller.
  • Code/integrate initial feature-full version of EPU Worker.
  • Code initial feature-full version of Sensor Aggregator.
  • Code initial feature-full version of EPU controller decision engine.
  • Code initial version of bootstrap program.

Jira Issues

(login required to see this, otherwise you will probably see "jiraissues: Error on line 1")

jiraissues: Unable to determine if sort should be enabled.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.