2012.06 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 June 2012 by Beneficiary and Task.

It is part of the June Monthly Report.

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

CNR Activities

The biggest area of work for T8.1 in June was the Virtual Research Environment management. The task was almost completely devoted to design and implement a new approach for creating VREs driven by functionality instead of services.

Firstly, following the availability of the gCube mavenization tools provided by T7.1, VREModeler and Resource Manager services (the two services involved in the VRE management) have been mavenized to fully exploit the new possibilities offered by the introduction of Maven in gCube.

Within VREModeler, the new functionality driven procedure has been designed and is currently under development. The integration with the new version of ResourceManager Service is started ticket #529).

The work on Resource Manager was along three main directions:

  • capability of managing multiple scopes in the same instance (ticket #348)
  • capability of deploying/undeploying single gCube software packaging, web applications, plugins (ticket #410)
  • future possibility of package upgrading (ticket #554)

According to #348, the Resource Manager interface has been completely refactored and reorganized in three portTypes (Resource Binding, Reporting, Scope Controller). Deployer service has been also changed to exploit this new interface. Moreover, the internal state of the service has changed to model software and dependencies and their respective relationships. This allows to manage single packages and, in the (near) future, to upgrade the deployed software. The work on Resource Manager is still ongoing and will be completed by the end of July.

The SoftwareGateway service has been modified about policies for dependencies resolution (ticket #421). Other minor integration and resolution conflicts with the new GHN version 3.3.0 were solved.

Finally, T8.1 solved several integration tickets reported by WP7 allowing to close gCube 2.9.0.


Resource Manager able to manage multiple scopes has delayed in favor of a better integration with future capabilities of the service. Globally, these features won't be in delay, but just released all together.


  • Resource Manager service able to handle multiple scopes
  • New Resource Manager public interface
  • Design of deployment/undeployment features for Plugins, WebApplications, Libraries and single gCube packages

FAO Activities

None to report.


None to report.


None to report.

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

E-IIS Activities

The Policy Management library, completed before the modification of the workplan, has been published on Etics. A version of the UserManagement library, providing CRUD operations on users records stored in an LDAP directory, has been developed and it is also on Etics. The development activities on the REST interfaces of the Authentication module and the User Management Module have been started just before the TCOM. The activities of study, possible improvement and integration of Shibboleth Identity Provider have been started too.


None to report.


  • Policy Management library is ready to be released
  • LDAP User Management library is ready to be released

T8.3 Workflow Management Facilities

NKUA Activities

NKUA has been working in enriching the hosting node information supported by the corresponding entity and adaptors within the node selection library which is part of org.gcube.execution.MadgikCommons in order to prepare the ground for the integration of PE2ng with Resource Registry. The Resource Registry repository provider for gCube is also being adapted to support this information.

Moreover, having the needs expressed by CNR during the 2nd TCOM meeting in mind, the incorporation of a queueing mechanism as a layer operating on top of the Execution Engine is being designed while its interrelation with the computational models which will be introduced in the near future is being investigated.

Finally, the Workflow adaptor implementing the execution layer of the gCube Search System (org.gcube.execution.WorkflowSearchAdaptor) has been made more flexible by modularizing the data source wrappers which implement the logic of web service invocations. Wrappers for the gCube environment are intended to remain within the software artifact of the adaptor for distribution purposes.


None to report.


None to report.

FAO Activities

None to report.


None to report.


None to report.

T8.4 Resource Model

FAO and CNR had a conference call to organize the work around the formalization of the new Resource Model and the talk to be given at the 2nd TCOM held in June.

FAO Activities

FAO has worked on D8.4 and completed the work on the new resource model to the degree required for D8.4. Moreover, FAO chaired a session at the TCOM to introduce the Interface and Function Layers.


None to report.


CNR Activities

CNR worked on the definition of XML bindings for the public facets of the new resource model. Those definitions were reported in the Interface Registry of the model.

CNR contributed to the preparation of the slides for the T8.4 session at the TCOM.


None to report.


None to report.

NKUA Activities

NKUA has studied the results of the work of other members of the consortium contributed to the evolution of the resource model with comments provided in face to face meeting during the Rhodes' TCom.

Furthermore NKUA is validating / driving concerns on the resource model against / from the resource model abstraction offered by the Resource Registry Component that supports (mainly) Search and PE2ng Services. Especially during this period the revisiting of PE2ng resource model/ resource tracking mechanism was done with the T8.4 progress in mind.


None to report.


None to report.

Personal tools