From Fedora Project Wiki
(initial writeup)
 
No edit summary
Line 3: Line 3:
== Summary ==
== Summary ==


Package DIET an open source middleware for High Performance Computing.
This feature brings DIET an open source middleware for High Performance Computing to Fedora 17


== Owner ==
== Owner ==
Line 13: Line 13:
== Current status ==
== Current status ==
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Last updated: 2012-01-15
* Last updated: 2012-01-18
* Percentage of completion: 50%
* Percentage of completion: 50%
** All packages have been made and submitted to review
** All packages have been tested and certified functional by both upstream maintainers and end-users




== Detailed Description ==
== Detailed Description ==
DIET is a grid toolkit originally developped by INRIA and now co-maintained with SysFera a company
DIET is a grid toolkit originally developped by INRIA and now co-maintained with SysFera a company
vishnu is a collection of DIET services co-developped by SysFera and EDF (energy company)
vishnu is a collection of DIET services co-developped by SysFera and EDF (A French major energy company)


omniORB is available under GPLv2/LGPLv2.1 (binaries/libraries)
omniORB is available under GPLv2/LGPLv2.1 (binaries/libraries)
Line 36: Line 38:


== How To Test ==
== How To Test ==
* Ensure that packages install properly
* Ensure that a DIET hierarchy can be launched and start submitting computational requests  
* Ensure that a DIET hierarchy can be launched and start submitting computational requests  
* Collect feedback from Fedora & DIET communities
* Collect feedback from Fedora & DIET communities
Line 49: Line 52:


== Release Notes ==
== Release Notes ==
DIET
DIET is a middleware designed for High Performance Computing in heterogeneous and distributed environments (workstations, clusters, grids, clouds). It implements OGF Grid RPC standard
that allows building distributed computational and service orientated infrastructure.
 


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/DIET]]
* See [[Talk:Features/DIET]]

Revision as of 17:00, 18 January 2012

Feature: DIET

Summary

This feature brings DIET an open source middleware for High Performance Computing to Fedora 17

Owner


Current status

  • Targeted release: Fedora 17
  • Last updated: 2012-01-18
  • Percentage of completion: 50%
    • All packages have been made and submitted to review
    • All packages have been tested and certified functional by both upstream maintainers and end-users


Detailed Description

DIET is a grid toolkit originally developped by INRIA and now co-maintained with SysFera a company vishnu is a collection of DIET services co-developped by SysFera and EDF (A French major energy company)

omniORB is available under GPLv2/LGPLv2.1 (binaries/libraries) DIET/vishnu under the CeCILL-A (a GPLv2 like license -fully compliant-, written to complies with French laws and compatible with international treaties ratified by France)

Benefit to Fedora

Fedora will take some benefit to offer a grid toolkit both easy and scalable as DIET. Since DIET requires omniORB4, Fedora will also gain industrial-grade CORBA 2.6 implementation for C++ and Python.


Scope

Required steps are:

  1. omniORB package
  2. DIET package
  3. vishnu package
  4. optional: python-omniORB package

How To Test

  • Ensure that packages install properly
  • Ensure that a DIET hierarchy can be launched and start submitting computational requests
  • Collect feedback from Fedora & DIET communities

Contingency Plan

None necessary. All packages have been built and tested for a long time, since i'm one of the upstream maintainer, i'll help fixing and backporting issues between upstream and Fedora.

Documentation

Release Notes

DIET is a middleware designed for High Performance Computing in heterogeneous and distributed environments (workstations, clusters, grids, clouds). It implements OGF Grid RPC standard that allows building distributed computational and service orientated infrastructure.


Comments and Discussion