Project Deliverable #657

D6.1 : Blue Economy VRE Specification [6]

Added by Franco Zoppi about 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:Jan 01, 2016
Priority:NormalDue date:Feb 29, 2016
Assignee:George Kakaletris% Done:

100%

Category:-
Sprint:WP06
Dissemination Level:PU Editor:George Kakaletris
Lead beneficiary:4 - UOA Reviewer:Leonardo Candela
Deliverable Type:OTHER
Milestones:
Duration: 42

Description

This deliverable presents the requirements, the specifications and the design of the solution that assembles the Blue Economy VREs.


Related issues

Related to BlueBRIDGE - Project WP #654: WP6 - Supporting Blue Economy: VREs Development [Months: ... Closed Oct 01, 2015 Feb 28, 2018
Related to BlueBRIDGE - Task #2776: Update Blue Economy VRE specifications Closed Mar 21, 2016 Sep 30, 2016

History

#1 Updated by Leonardo Candela almost 4 years ago

  • Assignee set to George Kakaletris

#2 Updated by George Kakaletris almost 4 years ago

  • Related to Project WP #654: WP6 - Supporting Blue Economy: VREs Development [Months: 1-30] added

#3 Updated by Leonardo Candela over 3 years ago

  • Editor set to George Kakaletris

#4 Updated by Leonardo Candela over 3 years ago

  • Reviewer set to Leonardo Candela

#5 Updated by George Kakaletris over 3 years ago

The deliverable is partitioned in two areas as there are two VREs

Sub-TOC per VRE partition:

Use Cases

  • One subsection per major use case

Users

  • User Classes
  • Process of registration

VRE Design

  • Services / interactions

Resources

Data Sets

  • Nature / Policies

Nodes

  • Types / Sizing / Policies

Services

  • Commons / VRE Specific
  • Names / Types / Policies

Models

  • Names / Types / Policies

Wiki page where deliverable will be hosted: https://support.d4science.org/projects/bluebridge/wiki/D_6_1

#6 Updated by George Kakaletris over 3 years ago

  • Status changed from New to In Progress

Submission to reviewer for review.

Deliverable description document is uploaded on Workspace: https://goo.gl/c6atZ4

#7 Updated by Leonardo Candela over 3 years ago

  • Status changed from In Progress to Sent to Reviewer

#8 Updated by Leonardo Candela over 3 years ago

  • Status changed from Sent to Reviewer to Under Revision

#9 Updated by Leonardo Candela over 3 years ago

  • % Done changed from 0 to 50
  • Status changed from Under Revision to Reviewed

Please find here a revised version of the document https://goo.gl/0zUMSp

Re the Wiki (the actual deliverable) I have the following major comments:

  • On https://support.d4science.org/projects/bluebridge/wiki/VRE_6_1_Specification

    • In VRE Design I do not see any reuse of gCube stuffs / existing services apart from the Workspace. What about the Statistical Manager for the R algorithms?
    • I suggest to carefully check this part and improve it, i.e. make it better integrated with the rest;
    • It is not clear to me how the Datasets (in particular the external ones) are expected to enter into the scene. Ideally, they should be integrated by relying on WP10 services and systematically accessing their datasets;
    • Re the Internal Datasets I assume it is planned to use the workspace, is this correct? Is there any need to “share” such datasets? Is there any need to support the discovery of such datasets? Please, suggest what is the service that is acting as the “repository” of these datasets;
    • Nodes and Services sections should be reconsidered. This description sounds completely “agnostic” wrt gCube / D4Science. What are expected to store the DB that are mentioned there?
    • What are the “products” this VRE is going to enact and release? Are we able to better define them? Are we able to identify suitable metadata? Are we able to identify a suitable repository for them?
  • On https://support.d4science.org/projects/bluebridge/wiki/VRE_6_2_Specification

    • The architecture of this VRE is completely different than that of the VRE #1, however it suffers from similar issues, namely the lack of real connection with the rest of gCube/D4Science solution stack;
    • We should reconsider the proposed “platform” and try to make it a bit more coupled with the “hosting infrastructure”;

To conclude, above comments suggest that the “technical” specification of both VREs (that should be the core part of this deliverable) is not satisfactory. I would suggest to not delay the production of the deliverable (we have time to adjust the Wiki). However, it is quite urged to have a technical discussion aiming at reinforcing the integration of VREs resulting from WP6 with the rest.

#10 Updated by George Kakaletris over 3 years ago

Updates have been uploaded by the contributors and the deliverable is ready for submission.

Further updates will be planned for April 2016, as in ticket #2776.

#11 Updated by George Kakaletris over 3 years ago

  • Related to Task #2776: Update Blue Economy VRE specifications added

#12 Updated by George Kakaletris over 3 years ago

  • Status changed from Reviewed to Feedback Processed

The new document is now at https://goo.gl/IYpN3Q. All reviewer comments and corrections on the document were accepted as significantly improving the quality of the document.

One comment has been addressed as follows: although access to the wiki is controlled, the deliverable itself is public, that is there are no restrictions in disseminating its content. As the reviewer observes, for technical reasons anonymous public access is not provided by the infrastructure, thus registration is required, however this does not change the legal aspect of public deliverable content.

#13 Updated by Leonardo Candela over 3 years ago

  • % Done changed from 50 to 90
  • Status changed from Feedback Processed to Reviewer Approval

A slightly revised version of the document is available at https://goo.gl/PPzcWx

The Wiki pages implementing the actual deliverable are detailed and informative.

I propose to approve and submit the deliverable as it is now yet I recommend to further discuss the technicalities underlying the proposal to make a larger / more in depth integration with/exploitation of existing gCube / D4Science facilities. I see a number of opportunities, namely StatMan for data analytics (rather than Rserve for VRE#1), the workspace for managing files and results. StatMan maintains rich metadata on each process it executes including a provenance record in PROV-O.

I didn't analysed in detail the RDB schema underlying VRE#1 yet some aspects seem questionable, e.g.

  • I see a number of occurrences of a field 'aa' I do ignore what it is (a better name should be identified),
  • in the Site table I see a series of attributes 'Period'+month+'A/B' is this really OK? What is it? It is just an INT?

#14 Updated by Leonardo Candela over 3 years ago

  • Status changed from Reviewer Approval to Sent to QAO

#15 Updated by Leonardo Candela over 3 years ago

  • Status changed from Sent to QAO to QAO Approval

The document is fine from the QAO perspective. Please find below the document to be submitted

#16 Updated by Leonardo Candela over 3 years ago

  • Status changed from QAO Approval to Sent to Mgmt for Approval

A post asking PSC members to approve the deliverable was published. The deliverable will be tacitly approved by the PSC if no comments are raised by April 4th

#17 Updated by Leonardo Candela over 3 years ago

  • Status changed from Sent to Mgmt for Approval to Mgmt Body Approval

#18 Updated by Leonardo Candela over 3 years ago

  • Status changed from Mgmt Body Approval to Closed

#19 Updated by Pasquale Pagano over 3 years ago

  • % Done changed from 90 to 100

Also available in: Atom PDF