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' (see below).

Status

  • Developed a harness to test the contextualization broker service that coordinates dynamic configuration/security adaptation of deployable types as they are instantiated.  Thousands of simultaneous 
    clients can now be simulated at any time during the implementation to help reduce the risk of large virtual cluster launches failing to start up properly.  See README [1] and "Context broker scalability harness" [2] for more details.
  • Postponed hands-on evaluation of technologies (like e.g. rPath and CohesiveFT provide) that help with virtual appliance authoring and packaging (CIDEVCEI-37 and CIDEVCEI-38).  The "Adapter layer to Condor" task (CIDEVCEI-24) took far more time than anticipated and was deemed to have higher priority over this investigation.  This hampers the ability to design a strawman schema for execution units (CIDEVCEI-35).

[1] - http://github.com/clemesha-ooi/ctx-broker-scalability-harness

[2] - http://www.oceanobservatories.org/spaces/display/CIDev/Context+broker+scalability+harness

Next actions

  • Pick up on the postponed CIDEVCEI-37 and CIDEVCEI-38 tasks.
  • After those evaluations, will be able to add more detail to the architecture, including schemas for representing execution units.

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.

Status

  • A Java (server) <-> Python (client) REST connection was implemented. This is a secure bridge to a running Nimbus service for dynamic configurations including client 
    credential management.  See "Admin REST API" [1] for details (and CIDEVCEI-30 / CIDEVCEI-52)
  • Subtask of that work was to internally reorganize the Nimbus user system but this was deemed too costly (CIDEVCEI-53)
  • Ongoing work on the user dashboard continued (CIDEVCEI-29) , see "Nimbus Django bootstrap and admin" [2] for a list of the improvements.
  • Adapter layer to Condor progressed but took a lot longer than anticipated (it involves tight collaboration with outside team).  See "Adapter to Condor" [3] for more information.

[1] - http://www.oceanobservatories.org/spaces/display/CIDev/Admin+REST+API
[2] - http://www.oceanobservatories.org/spaces/display/CIDev/Nimbus+Django+bootstrap+and+admin
[3] - http://www.oceanobservatories.org/spaces/display/CIDev/Adapter+to+Condor

Next actions

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

Next actions

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.