WP5: The LarKC Platform Implementation

Contents

WP5: The LarKC Platform Implementation

1. Presentations

Kick-off meeting, Innsbruck, April 2008

Kick-off meeting, Innsbruck, 16 April 2008

Stuttgart meeting, 13-15 October 2008

Suttgart meeting, WP5 plenary presentation, 13 October 2008

2. Meetings

2.1. Dial-in details for teleconferences

For audio, we will use powwownow. The telephone number for your country can be found here: http://www.powwownow.es/p/5/en/

The PIN to use is: 919489

For most meetings we will use a collaborative tool for sharing desktops, sharing files and chat functionality. This can be accessed here: http://webconf.vc.dfn.de/larkcdev/

2.2. Minutes

3. Workshops

4. Deliverables - At a Glance

Deliverable	Description	Leader	Due	Status
D5.5.1	Definition of validation goals for the prototyping phase (paper)(deliverable)	Onto	M2	Submitted 01.07.2008
D5.6.1	LarKC Development Environment Available	HLRS	M3	Submitted 30.06.2008
D5.1	Summary of parallelisation and control approaches and their exemplary application for selected algorithms or applications	HLRS	M6
D5.2.1	Rapid prototype of the LarKC	CycEur	M10	Uploaded on gForge on 26.12.2008
D5.3.1	Requirements Analysis and report on lessons learned during prototyping	CycEur	M12	Postponed to M14. Submitted 02.06.2009
D5.5.2	Validation goals and metrics for the LarKC platform	Onto	M15	Resubmitted on 31.08.2009 with implemented reviewer comments
D5.3.2	Overall LarKC architecture and design v1	HLRS	M18	Submitted on 30.09.2009
D5.4.1	Initial release of the LarKC platform	HLRS	M24	Postponed to M25, Submitted on 26.04.2010
D5.5.3	Report on platform validation and recommendation for next version	Onto	M28	Submitted on 29.07.2009
D5.4.2	Second release of the LarKC platform	HLRS	M33	Submitted on 30.12.2010
D5.3.3	Final LarKC architecture and design	HLRS	M36
D5.5.4	Report on platform validation and recommendation for the final version	Onto	M36
D5.4.3	Final release of the LarKC platform	HLRS	M42

5. Licence Requirements

This statement summarizes the decisions taken by the consortium and documented in [http://svn.larkc.eu/wp9/D9.4/ Deliverable 9.4.:

The LarKC Platform and its source code will be released under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0.html).

LarKC plugins, and other code produced by the LarKC consortium may be released under any license which does not have the effect of imposing any copyleft requirement whatsoever on code to which it is linked, connected, or otherwise associated. For the purposes of clarity, "copyleft requirement" here signifies a requirement to license such associated code under a license identical or similar to the license asserting the copyleft requirement. Licenses that are acceptable for release of code produced for the LarKC project include, but are not limited to: the Apache License Version 2.0, the BSD License, the MIT License, the LGPL and the Creative Commons Attribution License without the Share Alike feature. Licenses that are unacceptable for release of code produced for the LarKC project include, but are not limited to: any version of the GNU General Public License (GPL)

Reading D9.4 will reiterate the point that the only acceptable license for code that is required for the operation of the platform is Apache 2.0. This choice was carefully made, and was designed to minimise the likelihood that organisational policies would prevent coders from working with the platform code. The cost of this, which we have chosen to pay, is that there are some potentially useful packages that we can't use to build the platform. A wider variety of licences (including LGPL but NOT GPL) may be used for plugins and other non-platform code. Note that this doesn't prevent third parties from producing plugins using e.g. GPL, but it does mean that the LarKC project will never distribute such plugins.

6. Work in Progress

6.1. Bibliography

Bibliography of WP5 relevant material, including material on semantic descriptions of Quality of Service.
Parallelism in Java
An Overview about Semantic Technologies which are related to semantic annotaion, especially to semantic annotation of Web Services Semantic Techjologies
Specification of initial QoS Aspects of the LarKC platform QoS Aspects

6.2. Parallelization and Distribution SotA

Submitted deliverable, due M6: ''D5.1 Summary of parallelization and control approaches and their exemplary application for selected algorithms or applications''
This report lists the different techniques to be considered when designing the LarKC Collider Platform. It intends to be a guidance to help the architects and developers to choose the most appropriate solution. The platform will be dewigned and developed as a combination of different parallelization and resources distribution techniques.
The analysis of some example algorithms is being performed in order to optimize the outcome of our Applied parallelization workshop, July 8th, Amsterdam

6.3. Parallelization, Distribution and Remote Execution tasks

6.4. Within Plug-in Parallelization tasks in progress

Although this is not a WP5-only task (but a cross-WP issue), we would like to share the status here
http://wiki.larkc.eu/LarkcProject/WP5/WithinPluginParallelization

6.5. Rapid Prototype

The Report on platform release will be a short report showing the time line leading up to the newly planned first public release (M14). Currently we have the Minimal shopping list for that release which we drew up in the ad-hoc WP5 meeting we had during the kick-off meeting in Innsbruck.
The LarKC Plug-in API is undergoing a period of rapid evolution based on the results of WP5 workshop meetings and teleconferences. The current status of this work and links to information leading up to the current status can be found here.
General discussion of the continuing evolution of the LarKC plug-in API
Discussion of programming models to realise 'anytime' behaviour
LarKC Data Layer API is a specification page to comment the Data Layer API in the first LarKC prototype
Getting started guide
Material on ORDI datamodel
Making Baby Larkc work with the new data model: here
Overview about the components (plugins + pipelines) of the trunk directory. Please visit this page to check if every required information of your component is available and documented: LarkcComponentsCompleteness

6.6. Urban Baby LarKC Support

Urban Baby LarKC Demo support contains discussions and work being done in collaboration with WP6 for the support of the Urban Baby LarKC Demo

6.7. Requirements and Architecture

Early prototype of a Software Requirements Specification for the LarKC Platform.
This document is intended as a basis for discussion leading to a better mutual understanding of the goals of WP5.
Some of its contents might become part of D5.3.1 Requirements Analysis and report on lessons learned during prototyping.
Some Open questions regarding architecture and sw requirements are still to be answered.
A discussion on which support should be offered by the LarKC platform (and conversely, which work should be left to the plugin-writers and pipeline-configurators); response from Barry where he proposes building LarKC in steps
Analysis of the LarKC Code: Parallelization / Distribution Analysis
Version of the Architecture, after Architecture Workshop and further email discussions: Architecture_discussion.ppt
Latest LarKC Architecture: Overall LarKC architecture and design v1, submitted 30.09.2009

6.8. Performance and Scalability assessment

6.9. The LarKC Development Environment

The LarKC Development Environment: GForge SVN
The LarKC Development Environment has been migrated to: https://sourceforge.net/projects/larkc/
The LarKC Collaborative Development Environment - LarKC@SourceForge.net

6.10. LarKC Release Procedure

Release Packaging and Testing
?Release Documentation and Announcement

6.11. ClassLoader issues

working version of ?ClassLoader issues and OSGI: Java ClassLoader and OSGI

6.12. Data Layer

Implications of MemoryBasedArchitectures for LarKC (by Naso)
Link to W3C wiki on large triple stores http://esw.w3.org/topic/LargeTripleStores

6.13. Workflow Support Services

Initial ideas of the Flow Controller
More elaborated discussion after the Stuttgart Platform Workshop: Conclusion Report “An Outsider’s Summary”

6.14. Feature Requests and feedback

6.15. Other topics

Using JEE technology to deploy plugins in servlet containers
Towards distributed scalable (high-throughput) reasoning: MapReduce
Managing Plug-in state
Candidate for Platorm Documentation, Release V1.0: LarKC_WP5_D5_4_1_V0_10.pdf
Logging in the LarKC Platform and Plug-ins

6.16. Planning next steps ...

Plans for the period following the Stuttgart plenary: ?WP5Months6to10
Where are we going to be in M10/12/14 (Jan´09/March´09/May´09)?
Where are we going to be in M24/33/42 (March´10/Dec´10/Sept´11)?

7. All Work Package 5 Contents

See navigation menu (below right)