2012.08 WP8: iMarine Data e-Infrastructure Enabling Technology Development Monthly Activity By Task and Beneficiary

From IMarine Wiki

Jump to: navigation, search

Contents

This WP8 Activity Report described the activities performed in August 2012 by Beneficiary and Task.

It is part of August 2012 Monthly Activity Report.

T8.1 iMarine Data e-Infrastructure Enabling-technology Development

CNR Activities

As designed editor, CNR coordinated the production of deliverable D8.2 describing the novelties and evolution of the software produced by WP8 from M7 (May ’12) to M10 (Aug.'12). Specifically, the deliverable reported on the software released as part of gCube 2.9.1 and the forthcoming gCube 2.10.0.

The work on the new Resource Manager 2.0 continued at the beginning of August. Part of the testing phase has been successfully performed and several fixes applied. The RM2.0 stubs have been finalized and released so the numerous clients of the service had chance to change their implementation to comply with the new interface.

The release of maven-dependency-plugins 2.5 (beginning of August, reported in ticket #460) forced a major revision of the approach to software dependency resolution taken in the Software Gateway service. In fact, this plugin was interfaced by third-party external software previously exploited, but now no longer supported by its creators. As a consequence, the communication layer between Software Gateway and Maven (our dependency management system) was broken and had to be re-implemented. A new layer was designed and developed to directly interface Software Gateway with Maven. Lesser dependencies and software layers are now involved in the communication and a better abstraction over Maven has been reached, both allowing maintaining compatibility with its future evolution.

Still on the Software Gateway, the policies for registering new software have been modified according to ticket #575.


The unexpected work on the new integration of Maven 3 with the SoftwareGateway has delayed the testing phase of Resource Manager 2.0. Tests will be completed in the first 2 weeks of September.


  • software-gateway 1.1.0 release
  • software-gateway's developer and administration guides updated
  • design and implementation of a new communication layer between Software Gateway and Maven 3
  • resource-manager-stubs 2.0.0 release
  • deliverable D8.2

FAO Activities

FAO has worked towards the release of common-scope 1.0.0 and gCore 1.5.0 in gCube 2.10.0. common-scope provides core API to handle scope propagation in component's runtime as well as scope map handling. gCF 1.5.0 adds facilities for error management and propagation over the network.


None to report.


  • common-scope 1.0.0 release
  • gcf 1.5.0 release

T8.2 iMarine Data e-Infrastructure Policy-oriented Security Facilities

E-IIS Activities

ENG has contributed on D8.2 regarding the description of the components to be released with the next version of gCube.

The development of SOA3 Id-Federation module is in progress. In particular:

  • Shibboleth IdP has been integrated as the Identity Provider of the whole framework
  • a SAML Consumer is currently in advanced stages of development: it will be integrated with Shibboleth SP


None to report


None to report

T8.3 Workflow Management Facilities

NKUA Activities

A queue based scheduling facility for PE2ng has been developed. The implementation includes a queue-based scheduling component which will act as a front-end to Execution Engine. Execution plans are analyzed and then added up to the queue. The queueing mechanism examines every queued plan for requirements satisfaction, and if so, it is assigned to the execution engine, otherwise, it can be passed by a certain number of times. When the maximum number of postpones per execution plan is reached, no more plans are executed until the waiting plan on queue head gets committed.

This facility also exploits the information describing the state of the infrastructure, deciding to forward or queue up incoming tasks. This task requires an Execution node monitoring mechanism. This mechanism is based on JMS, where a monitor/consumer is subscribed on a load topic while each execution engine is subscribed as a producer on the same topic reporting the utilization of that execution engine.

Work has been done on the transition of the corresponding released components from ant to maven. This procedure includes many library components and two services. Also, all released components have been refactored to use the slf4j logging facade in order to facilitate the configuration of loggers at deployment time.

Future effort will be focused on release integration of the related components.


In order to communicate the load information among others, a JMS notification mechanism was used instead of the enhancement of Resource Registry as designed. The latter mechanism will be definitely used when it gets finally implemented.


The following components have been transformed to maven:

  • MadgikNotificationHandling
  • NotificationHandling
  • JMSEnvironmentProvider
  • GCubeEnvironmentProvider
  • EnvironmentProvider
  • InformationSystem
  • WorkflowEngine
  • WorkflowEngineService
  • ExecutionEngine
  • ExecutionEngineService
  • QueueableExecutionEngine

FAO Activities

None to report.


None to report.


None to report.

T8.4 Resource Model

FAO Activities

None to report.


None to report.


None to report.

CNR Activities

None to report.


None to report.


None to report.

NKUA Activities

None to report.


None to report.


None to report.

Personal tools