2012.10 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 October 2012 by Beneficiary and Task.

It is part of Monthly Activity Report.

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

CNR Activities

Following the deployment of Resource Manager 2.0 in the production environment, a set of minor issues have been spotted and then fixed. Specifically, the incident ticket #479 led to a new minor release of the service. CNR also provided continuous support to the integration of gCube 2.10 helping to identify solutions for several failures on deployment and undeployment operations due to other service's misconfiguration or wrong behaviors.

The Deployer 2.4.0 released in gCube 2.10 was further modified to fix the issue reported in ticket #720. This required a different and more appropriate way to manage the undeployment of packages included in the gHN-distribution.

New minor release of SoftwareGateway 1.1.0 has been released in gCube 2.11: a minor issue has been fixed. The issue is reported in ticket #802.

A set of T8.1 components were moved under different responsibilities and effort was spent to transfer knowledge among T8.1's members.


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


  • resource-manager-service 2.0.1 release
  • SoftwareGateway 1.1.1 release

FAO Activities

FAO has been involved in the following activities:

  • FAO has implemented ghn-client-runtime<code> 2.0.0 and <code>ghn-client-notification 1.0.0, two components that enable clients to invoke gCube services under a fully embedded and optimised gHN stack. While ghn-client-runtime 1.0.0 achieved similar results, ghn-client-runtime 2.0.0 is designed to serve as a runtime dependency, rather than a test tool. For this, it has been released in gCube 2.11 as a gCube component. ghn-client-runtime 2.0.0 also optimises the required stack, greatly reducing the size of the embedded stack (before, the stack was defined by ghn-core-runtime, which was created for service-side use, hence includes components that are not needed client-side). Further, support for notifications has been modularised in ghn-client-notification, which has become optional. This eliminates further the size of the client runtime stack in the common case in which clients do not make use of notifications. Finally, and most importantly, ghn-client-runtime 2.0.0 has a single distribution which is suitable for all infrastructure in which the system is deployed (e.g. testing vs. production), in contrast with the previous version that required per-infrastructure distributions. This is important, as it allows clients to avoid a similar multi-distribution for different environments.


  • The ability for ghn-client-runtime 2.0.0 to go cross-infrastructure has been supported by a change in gCF that allows clients to make calls in any scope for which a service map is available, rather than just those for which the gHN has been configured. This important change has been released in gCube 2.11 as gCf 1.5.1.


  • The stack brought along by ghn-client-runtime 2.0.0 is no longer provided by a single uber-jar, but by many individual Maven dependencies on WSCore 4.0.4 components. This allows selective exclusions of artefacts client-side. Since many of these legacy components are not available in Maven central, FAO has deployed them in our gcube-externals Nexus repository, in agreement with WP7.


  • In the broader context of integration issues within WP9, FAO has presented at the 3rd TCom an architecture for the HTTP URI resolution of data which is otherwise accessible through ad-hoc SOAP interfaces in the data management layer of the system. Following the meeting, FAO has engaged with a discussion with relevant partners, such as CNR and Athens. As a result FAO has implemented the entire architecture and released in gCube 2.11 a set of components that fall in the scope of WP8, WP9, and WP11. Among these, common-uri is a WP8 component that provides cross-service support for minting HTTP URI without hard-coded dependencies on given authorities (servers) and without explicit dependencies on scope. common -uri has been developed in full generality, and it support a number of URI protocols, a number of URI formats, and a number of URI authority resolution strategies that should accommodate evolutionary requirements within the system. common has been released in gCube 2.11 with version 1.0.0.


  • FAO has applied a fix to maven-service-plugin which did not include the main service artefact to the full GAR used for manual deployment purposes in infrastructure operations. This was an addition that FAO released in maven-service-plugin 1.1.0.


  • FAO continues to support the Mavenization of the build and integration infrastructure. In particular:
    • the development of a gCube BOM component that will control the version of direct and indirect component dependencies and alert developers well ahead of production of clashes with library versions included in the distribution. This is an activity that otherwise is lead by CERN.
    • the resolution of the problem that outdated POMs for components that are included in new releases without changes. The problem is known as the 'Fossil POMs', as it manifests in released components with POMs that point to dependencies that are older than those with which components have integrated. FAO has identified the problem and proposed a solution in terms of 'system-releases', i.e. the generation of release versions that augment component versions with system versions. This eliminates the problem (as well as introducing a number of advantages in terms of tracking and dissemination), but it requires the interpolation of service profiles with Maven variables (details out of scope here). FAO ha proved that this is possible also for gCube services (not only library), exemplifying the solution for the Tree Manager service. The rolllout of this solution is now under consideration in collaboration with ENG and CERN.


  • FAO has introduced in common-scope 1.1.0 facilities to transparently reconcile thread pools with scope propagation requirements. In particular, common-scope 1.1.0 lets client bind Runnable and Callable tasks to the current scope prior to submission to ExecutorServices


The deployment of REST services within the architecture is, to date, limited to Virtual Platforms. The tools available for this have been proved to assume 3rd-party services, rather than full gCube components released with the rest of system. FAO has opened a ticket about these limitations (https://issue.imarine.research-infrastructures.eu/ticket/804) and a discussion with CNR has followed on ways to go beyond the initial design assumption of deployment tools.


None to report.

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

E-IIS Activities

  • ENG took part to Third TCOM meeting in Rome presenting the last achievements about gCube development.
  • The development of the most of GCube Security Handler has been completed: some minor integration issues versus gCore framework remains to be resolved.
  • A proposal of integration strategy for gCF and Clients is work in progress and will be presented to the involved partners after Y1 review


None


None

T8.3 Workflow Management Facilities

NKUA Activities

During last month, a first round of tests has taken place in order to evaluate the performance of PE2ng according to ticket #263. Those tests are based on scripts and data for launching Aquamaps. This evaluation, is composed by two parts. The first part, evaluates the performance of PE2ng when transfer invocations are necessary in order each execution node to acquire all files. The second part aims to examine the total execution time, when each node already has all necessary files and thus, no transfer invocations happen at all. This evaluation phase will continue, examining performance for more demanding jobs, while trying to increase exploitation of all available infrastructure resources.

Few bugs have been fixed in Node selection policies that depend on the sequence of the recently selected nodes, like LRU and MRU. Timestamps have better precisions, while all nodes are used before using tie breaks.

Also, WorkflowSearchAdaptor has been refactored to use the slf4j logging facade in order to facilitate the configuration of loggers at deployment time.


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