2013.04 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 April 2013 by Beneficiary and Task.

It is part of April 2013 Monthly Activity Report.

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

CNR Activities

  • Update Deployer-service version from 2.4.1 to 2.4.1.1. An integration issue has been solved (#1621).
  • Added documentation on common-encryption library (#1445).
  • Started to address and issue affecting the software gateway with profile declaring service versions greater than 1.0.0. Added a constraint on service version. (#1654). This feature is goint to be released in the next release
  • Prepared components for release in gCube 2.14 (#1612):
    • org.gcube.vre-management.deployer.2-4-1-1
    • org.gcube.vre-management.deployer-stubs.2-4-1-1
    • org.gcube.vre-management.deployer-testsuite.2-4-1-1


None to report.


None to report.

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

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

E-IIS Activities

The activity of installation (#1422) on the development infrastructure and deployment of the new secure VOVirtual Organization; #1505 has been started. This activities include the first steps of client integration. In parallel the test deployment of SOA3 in the test infrastructure #81 continued: in this environment some test on the new Authorization module has been performed. The most of the activities concerning the implementation and documentation of SOA3 Authorization Module have been completed, in particular:

  • The Authorization Module (#336)
  • Policy Management Interfaces (#335)
  • The Authorization Connector (#339)

The other activities related to s2s authentication and authorization will be finished in the very first days of May:

  • Service2Service authentication (1630)
  • Policy Management Portlet (#378)
  • Policy definition guide (#340)


Regarding the resource accounting activities:

  • The data-model definition, for the four resource types, has been completed, according to the tickets #1515, #1516, #1517, #1518.
  • The common-accounting-model library will contain the resource accounting data-model. A page to collect all the information related to this library (even on the decisions that we achieved on the data-model definition) has been created on the gCube wiki and is available here.
  • The common-accounting-lib library will be used to publish/consume resource accounting information by the services/accounting sub-system. The progress on this activity will be reported through the ticket #1582.
  • The progress on the accounting documentation status will be tracked through the ticket #1699.
  • The Resource Accounting portlet implementation has been started and the progress on this activity will be reported through the ticket #1631.
  • Finally, a master task (ticket #1633) to report all the activities related to the development of the Resource Accounting solution has been created.


None


None

T8.3 Workflow Management Facilities

NKUA Activities

The component that parses gCube services' WSDL files to create request SOAP envelopes is now operational. Using the extended JDL language (gJDL) we are now able to describe DAGs of web services as well, which are then executed through PE2ng. Sample executions of parallel and sequential web service operations have been tested (#1276).

The implementation of Map/Reduce supporting PE2ng operators has been completed (#1265). Now, a new workflow adaptor will be developed in order to exploit those operators, constructing Map/Reduce job workflows.

According to ticket (#1317), the evaluation of PE2ng in the UMD infrastructure continues gradually, due to some issues regarding the job submittion.

Moreover, the resource registry has been enhanced to offer a new operation, called reset (#1596). This operation, enables an automatic reset of the resource registry, avoiding needless restarts of a container. Lastly, it has also been refactored to use the Storage Manager instead of Content Manager (#1559).


none


The following components were released in gCube 2.14.0 with minor changes:

  • org.gcube.execution.GCubeEnvironmentProvider.1-5-1
  • org.gcube.execution.ResourceRegistry.1-3-4
  • org.gcube.execution.ResourceRegistry_NODEPS.1-3-4
  • org.gcube.execution.RRGCubeBridge.1-4-2
  • org.gcube.execution.WorkflowSearchAdaptor.1-2-1

FAO Activities

The beneficiary should report here a summary of the activities performed in the reporting period


The beneficiary should report here major issues faced in the reporting period and the identified corrective actions, if any.


The beneficiary should report here a bullet list highlighting the main achievements of the reporting period

T8.4 Resource Model

Complete (the Task was active from M1 to M8)

Personal tools