2012.02 WP8: iMarine Data e-Infrastructure Enabling Technology Development Monthly Activity By Task and Beneficiary

From IMarine Wiki

Jump to: navigation, search

Contents

This WP7 Activity Report described the activities performed in February 2012 by Beneficiary and Task.

It is part of February 2012 Activity Report.

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

A major outcome of the task was the production of the milestone MS33. Such milestone wraps up and gives external visibility to the work done so far on the evolution of the foundation technologies. The milestone was quite a defining point in the task, because it gave the opportunity to draw a line and prepare the ground for the next implementation steps on the foundation technologies.

CNR Activities

During the reporting period, CNR led the production of MS33 by coordinating the involved partners and preparing most of the contributions.

On the implementation side, the work of the common-utils-encryption library has been finalized and released. Following early feedback received, the schema of the Runtime Resource defined in common-resources has changed to support arbitrary properties optionally encrypted. On top of this work, in conjunction with T6.3, a new portlet has been designed and developed to allow VOVirtual Organization; /VRE managers to publish in the IS their own resources and configure in such a way the service instances available on their respective scopes.

Following a long discussion between T8.1 and T7.1 on the gCube mavenization, the gCube components will not be any longer stored in a custom repository but in more standard Maven Repositories. As a consequence, a new service, named Software Gateway, has been designed to interface a cluster of Maven Repositories. The Software Gateway will have the following distinguishing characteristics:

  • grant access to the software stored in recognized Maven Repository for deployment purposes
  • be a single point of configuration of a cluster of Maven Repositories in the whole infrastructure (hence, will avoid to configure each gHN for accessing to the recognized Maven repositories)
  • minimize the impact of the new physical storage (Maven) on the other enabling layer services
  • serve as mediator from the gCube coordinates (service name, class, version, package name, package version) to the Maven coordinates (groudID,artifactID,version>
  • enabling services aiming at communicating with the registered Maven Repositories must talk with the Software Gateway
  • external services may communicate directly with the Maven Repositories
  • publication of service profiles in the Information System
  • be scope-agnostic (all the software available in the maven repository must be visible to all the clients)

Differently from the Software Repository, the Software Gateway will not play the role of main distribution channel of the gCube software (Maven Repositories will serve as such).

The implementation of the Software Gateway in on the way and it is expected to be completed by the end of March.


New requirements on Runtime Resource called for a little redesign and implementation on common-resources


  • Milestone MS33
  • common-utils-encryption 1.0 released as part of gCube 2.8.0
  • common-resources 1.4 released as part of gCube 2.8.0
  • Software Gateway's design and early prototyping
  • Software Gateway's interface definition

FAO Activities

FAO has worked towards reducing the deployment and dependency requirements for clients of gCube services. In doing so, FAO is addressing a requirement for minimality raised by the work on Java clients in WP11.

The current requirements require the installation of the same 40+MB distribution used for services, even though only a fraction of the configuration and libraries is actually required by clients. Besides issues of size, the existing approach cannot be reconciled with build technologies that offer dependency management services, primarily Maven.

FAO has thus produced:

  • a minimal distribution of a few kb, ghn-client-distro, which pairs with ghn-core-runtime and a handful of runtime libraries to exhaust all the required client dependencies.
this alone simplifies significantly the installation and maintenance requirements for legacy clients based on Ant build technology.
  • a set of infrastructure-specific libraries (ghn-client-runtime-dev, ghn-client-runtime-d4s) which dispense Maven clients from downloading and installing the client distribution.
The libraries embed client distributions pre-configured for clients that work in the corresponding infrastructures as well as bootstrapping mechanisms (either programmatic or based on Java instrumentation agents), which trigger the installation of the embedded distributions. Using Maven's transitive dependency resolution mechanisms, clients can declare a single dependency in their POMs and obtain the required closure of dependencies as well as a transparent installation of the client distribution.

The approach has been tested with queries to the IS, calls to arbitrary gCube services, and even for subscriptions/notifications.

The distribution and the libraries are available in our Maven repositories and will be soon configured for integration in Etics.

A design note that identifies problems and outlines the solutions can be found here.


None to report.


New client distribution and runtime libraries.

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

E-IIS Activities

The activities of the month have been focused on the design of an advanced and flexible Policy Oriented Security Module. This module will represent a strong improvement of the previous D4Science Authorization module. In particular it aims at providing:

  • support for dynamic user attributes, such as the number of accesses to a resource
  • support for context attributes, e.g. date and time
  • improvements of the existing Policy Definition and Management Module


None


None

T8.3 Workflow Management Facilities

NKUA Activities

NKUA had a conference call with CNR in order to understand the needs for parallelization of the algorithms invlolved in iMarine scientific scenarios and to understand what the needs are for evolving PE2ng and its model of resources and operation.

As a first step towards achieving the goal for algorithm parallelization, NKUA is investigating the RainyCloud approach which is used currently in Aquamaps and will develop a PE2ng adaptor for the latter.

NKUA is also examining algorithms and data in order to make proposals on the topic and to form requirements for the abstractions of computational models which will be offered by PE2ng.

In parallel, NKUA will assist CNR in getting familiarized and using PE2ng.


None


  • Agreement on future evolutions of the PE2ng at project level

FAO Activities

Nothing to report


None


None

T8.4 Resource Model

FAO Activities

FAO produced a first draft of the new Resource Model. The focus at this time was on the software resource modeling that will form the basis for defining the next implementation steps in T8.1 and T8.2.


None


None

CNR Activities

CNR contributed to the first draft of the new Resource Model (edited by FAO) with discussions, feedback and writing.


None


None

NKUA Activities

Nothing to report


None


None

Personal tools