2012.12 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 Month 14 by Beneficiary and Task.

It is part of Monthly Activity Report.

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

CNR Activities

CNR has been involved in the following activities:

  • Troubleshooting of ticket #977 regarding a problem with the deployment of web applications on a selected node.
  • Troubleshooting of ticket #762 regarding a problem cleaning the GHN state in case that a deployment goes wrong.


None to report.


The deployer now removes software dependencies that have been installed during software deployment when the deployment of one of the packages goes wrong (#762).

FAO Activities

FAO has been involved in the following activities:

  • development of version 1.0.0 of common-scope-maps, a simple resource bundle that contains all known scope maps, across infrastructures. The component serves as a direct dependency of common-scope and remains otherwise invisible to clients further upstream (#943).
    • The component is ready for release in gCube 2.12.
  • further development of version 1.1.0 of common-scope (#1068):
    • scope maps are now versioned and when multiple maps for the same scope are discovered on the classpath then the newest version is chosen. This configuration mechanism supports a modularisation strategy whereby scope maps can be conveniently embedded in common-scope-maps whilst remaining overridable through local configuration, without motivating a new release of common-scope-maps;
    • scope maps can now be successfully resolved in VRE scope (bug fix);
    • scopes can be conveniently consumed as ScopeBean objects by those selected components that do not treat scopes as opaque strings (e.g. ic-client);
    • prepared the component for release in gCube 2.12.
  • further development of version 1.0.0 of common-gcore-stubs:
    • eliminated at(string), instanceAt(string), instanceAt(EndpointReference) methods of StubFactory. Refactored for at(URI) and at(EndpointReference) with the latter working on address-only references.
    • prepared the component for release in gCube 2.12.
  • further development of version 1.0.0 of common-gcore-resources:
    • fixed publication of EndpointReferences in ServiceInstances.
    • prepared the component for release in gCube 2.12.
  • further development of version 1.0.0 of discovery-client (#1069):
    • added equals() and hashcode() to QueryBoxes;
    • initialisation parameters in QueryTemplate are copied to avoid side-effect (bug fix);
    • extended QueryTemplate with appendParameter(), hasParameter(), and parameter();
    • refactored XQuery to in terms of extended QueryTemplate API
    • init-time namespaces are no longer accidentally overridden (bug fix);
    • prepared the component for release in gCube 2.12.
  • development of version 2.0.0 of my-container (#978):
    • @Reference annotation for injection of service instances;
    • @Scope annotation on classes and methods for transparent scope setting;
    • MyContainer#setEndpoint() for injection of mock service implementations;
    • refactoring of MyContainer#endpoint() methods to MyContainer#address() methods with URI return type;
    • prepared the component for release in gCube 2.12.
  • further development of version 1.6.0 of gcf:
    • prepared the component for release in gCube 2.12.
  • further development of the Wiki documentation for the following components:
    • discovery-client
    • ic-client (co-documented);
    • common-gcore-stubs;
    • the presentation of the Featherweight Stack;


None to report.


None to report.

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

E-IIS Activities

IMarine portal (Liferay) has been integrated with Shibboleth Service Provider (via CASShib): it has been deployed in the Test Infrastructure provided by ENG and now is publicly available. We've successfully tested the web browser SSO feature. The deployment and testing of SOA3 connector (server side) in the Test Infrastructure has been completed (ticket #341). SOA3 Authentication Module (ticket #381) has been deployed in the Test Infrastructure.


None to report.


None to report.

T8.3 Workflow Management Facilities

NKUA Activities

During the month of December, the design process of the Map-Reduce / Master-Worker model abstraction (#939) materialization has been completed. A translation layer on top of workflow engine will be introduced.

According to ticket (#936) we continued the testing phase of the PE2ng Execution Engine in the Ecosystem scope. The aim of the test operation is to evaluate the Execution Engine under a demanding task, exploiting the full capabilities of the production nodes. However, the procedure is progressing gradually, due to some issues, related to the hosting nodes, that emerged during the testing operation.

Moreover, we implemented a new interface for node filtering in the node selection mechanism of the Execution Engine (#843). Through the interface, new criteria can be applied at runtime and proper nodes are chosen at each time of execution.

Finally, we updated the execution nodes to produce more extensive and detailed logs and Fixed minor bug on the Workflow Engine (#1082).


none


none

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

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

CNR 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

NKUA 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

Retrieved from "http://wiki.i-marine.eu/index.php/2012.12_WP8:_iMarine_Data_e-Infrastructure_Enabling_Technology_Development_Monthly_Activity_By_Task_and_Beneficiary"
Personal tools