2012.11 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 November 2012 by Beneficiary and Task.

It is part of Monthly Activity Report.

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

CNR Activities

CNR contributed to the new FeatherWeight Stack (FWS) by implementing the required support to abstract on the gCube Resource Model. In particular, a new Micro-library (#847) contains an object-based implementation of the gCube Resource Model, i.e. a set of classes that represent known resource types. The model includes the following top-level resource classes:

  • Software,
  • GCoreEndpoint,
  • ServiceEndpoint,
  • ServiceInstance,
  • HostingNode,
  • GenericResource.

More details are avaiable at: Common-gcore-resources


Nothing to Report


FAO Activities

FAO has led a collaboration with CNR towards the development of the WP8-layer a new client stack for legacy gCore service, the Featherweight Stack (#853). The stack has a minimal footprint in terms of code, dependencies, and overall usage requirements. Most noticeably it has not dependency on the gCore stack used service-side.

The WP8 layer of the Featherweight Stack includes four components, all of which are now ready to release and fully documented:

  • common-gcore-stubs: interacts with the JAX-WS runtime embedded in the Java 1.6 or later to synthesise dynamic JAX-WS proxies for remote gCore services from JAX-WS-annotated Java interfaces and JAXB-annotated I/O stubs (when required). Instruct the proxies to generate scoped gCube calls (#854)
  • common-gcore-resources: implements the gCube resource model through JAXB annotated classes (#847), as reported in CNR activities
  • discovery-client: defines a gCore-independent and IC-independent framework for query formulation and submission (#855)
  • ic-client: customises the query formulation and submission mechanisms of discovery-client to the IC (#856)

Details on motivations and components are available here: https://gcube.wiki.gcube-system.org/gcube/index.php/Featherweight_Stack.

FAO has also worked on gcf, deprecating the use of legacy scope facilities throughout, and on common-scope, simplifying the structure of scopemaps and adding ScopedTasks over Runnables and Callables. Details are available here: https://gcube.wiki.gcube-system.org/gcube/index.php/Scope_Handling:_from_gCore_to_common-scope


None to report.


  • common-gcore-stubs (#854)
  • common-gcore-resources (#847)
  • discovery-client (#855)
  • ic-client (#856)

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

E-IIS Activities

During the last month we've worked on the integration of the gCube Portal (Liferay) with an Identity Provider (Shibboleth IdP) to enable the web browser SSO. The integration has been completed and tested on the E-IIS testbed.

In particular:

  • we've installed and configured the Shibboleth Identity Provider, according to the ticket #337.
  • we've installed and configured the Shibboleth Service Provider, according to the ticket #338.
  • we've installed and configured CASShib: Liferay doesn't come with out-of-the-box compatibility with Shibboleth but it does come with explicit support for CAS. CASShib sort of acts as an adapter so you can use Shibboleth to provide the authentication and then pass it to Liferay as if it were coming in the format for CAS. Finally, we've configured the CAS authentication in the gCube Portal so as to enable the web browser SSO.

There is a how-to here that explains the requirements and the steps to integrate Liferay with Shibboleth.

We're working to make the current deployment in the testing infrastructure publicly available ASAP, so that we can test it more extensively.


None to report.


None to report.

T8.3 Workflow Management Facilities

NKUA Activities

During last month, an evaluation procedure of the PE2ng performance (#936) has emerged, as a consequence of the PE2ng enhancements (#263) that have taken place. The outcome of the evaluation should agree with the results from a previous evaluation that had taken place in development resources, and further investigate other aspects of the Execution computational capabilities.

Moreover, various PE2ng enhancements (#884) have been taken under investigation, expanding workflow capabilities in long terms. As a result, we are introducing filtering in the node selection of the hosting nodes (#843), that execution will be held at. Also, effort is being made towards PE2ng compliance to MapReduce / Master-Worker (#939) parallel Execution model abstractions.


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

Personal tools