Main.ActiveData History

Hide minor edits - Show changes to output

January 08, 2016, at 12:26 PM by 140.77.13.217 -
September 08, 2015, at 01:30 AM by 124.127.168.121 -
Changed line 65 from:
* ''Active Data: A Programming Model for Managing Big Data Life Cycle'' Anthony Simonet Gilles Fedak Matei Ripeanu. Technical Report. Submitted to FGCS.  [[ https://hal.inria.fr/hal-00729002 | HAL ]]
to:
* ''Active Data: A Programming Model for Managing Big Data Life Cycle'' Anthony Simonet Gilles Fedak Matei Ripeanu. Future Generation Computer Systems, 2015  [[ https://hal.inria.fr/hal-00729002 | HAL ]]
March 19, 2015, at 01:43 PM by 140.77.13.170 -
Changed lines 65-66 from:
* ''Active Data: A Programming Model for Managing Big Data Life Cycle''
Anthony Simonet Gilles Fedak Matei Ripeanu. Technical Report. Submitted to FGCS.  [[ https://hal.inria.fr/hal-00729002 | HAL ]]
to:
* ''Active Data: A Programming Model for Managing Big Data Life Cycle'' Anthony Simonet Gilles Fedak Matei Ripeanu. Technical Report. Submitted to FGCS.  [[ https://hal.inria.fr/hal-00729002 | HAL ]]
March 19, 2015, at 01:42 PM by 140.77.13.170 -
Changed line 55 from:
In collaboration with Ian Foster and Kyle Chard from Argonne National Lab/University of Chicago, we designed a Data Surveillance Framework for the Advanced Photon Source experiment.
to:
In collaboration with Kyle Chard and Ian Foster from Argonne National Lab/University of Chicago, we designed a Data Surveillance Framework for the Advanced Photon Source experiment.
March 19, 2015, at 01:40 PM by 140.77.13.170 -
Changed lines 7-11 from:
A key point is to handle the complexity of the ''''Data Life Cycle'', i.e. the various operations performed on data: transfer, archiving, replication, deletion, etc. Indeed, data-intensive applications span over a large variety of devices and e-infrastructures which implies that many systems are involved in data management and processing.


''Active Data'' is new approach to automate and improve the expressiveness of data management applications :
to:
A key point is to handle the complexity of the '''Data Life Cycle''', i.e. the various operations performed on data: transfer, archiving, replication, deletion, etc. Indeed, data-intensive applications span over a large variety of devices and e-infrastructures which implies that many systems are involved in data management and processing.


'''Active Data''' is new approach to automate and improve the expressiveness of data management applications :
Changed lines 34-36 from:
(:%frame thumb text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)

%
width=500%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
to:

%frame width=500%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
March 19, 2015, at 01:39 PM by 140.77.13.170 -
Changed line 36 from:
%width=300%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
to:
%width=500%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
March 19, 2015, at 01:39 PM by 140.77.13.170 -
Changed line 36 from:
%width=60%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
to:
%width=300%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
March 19, 2015, at 01:38 PM by 140.77.13.170 -
Changed line 34 from:
(:%frame width=600 text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
to:
(:%frame thumb text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
March 19, 2015, at 01:37 PM by 140.77.13.170 -
Changed line 34 from:
(:%frame width=60 text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
to:
(:%frame width=600 text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
March 19, 2015, at 01:36 PM by 140.77.13.170 -
Changed line 34 from:
(:%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
to:
(:%frame width=60 text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)
March 19, 2015, at 01:36 PM by 140.77.13.170 -
Changed line 36 from:
%width=60 center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%
to:
%width=60%http://graal.ens-lyon.fr/~gfedak/dlc.png | "Data Life Cycle Model"%%
March 19, 2015, at 01:34 PM by 140.77.13.170 -
Changed line 36 from:
%width=60%center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%%
to:
%width=60 center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%
March 19, 2015, at 01:32 PM by 140.77.13.170 -
Changed line 36 from:
%center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%%
to:
%width=60%center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%%
March 19, 2015, at 01:31 PM by 140.77.13.170 -
Changed lines 1-2 from:
!! Active Data : Managing Data-Life Cycle on Heterogeneous Systems and Infrastructures
to:
! Active Data :

!!
Managing Data-Life Cycle on Heterogeneous Systems and Infrastructures
Changed lines 34-35 from:
%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"
to:
(:%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model":)

%center%http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"%%
March 19, 2015, at 01:28 PM by 140.77.13.170 -
Changed lines 24-25 from:
%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"
to:
Changed lines 32-33 from:
When the DLCM evolves, the token will pass from a place to another, which ''fires a transition''. Active Data developers can attach their code to each transition in the DLCM. The '''handler code''' is then executed whenever the transition is fired. The system is distributed, thus any node in the network can publish transition and receive transition notification; this is how we can develop DLCM distributed applications.
to:
%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"


When the DLCM progresses, token will pass from a place to another, which ''fires a
transition''. Active Data developers can attach '''handler code''' to each transition in the DLCM. The handler code is then executed whenever the transition is fired. The system is distributed, thus any node in the network can publish transition and receive transition notification; this is how are developed DLCM distributed applications.
Changed line 39 from:
* Data '''Tags''' and  transition '''Guards''' are a powerful way of filtering data, conveying information across the systems and trigger handler execution only on specific data.
to:
* Data '''Tags''' and  transition '''Guards''' are a powerful way of filtering data, conveying information across the systems and triggering handler execution only on specific data.
Deleted line 57:
*
March 19, 2015, at 01:26 PM by 140.77.13.170 -
Changed lines 24-25 from:
%rframe text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"
to:
%frame text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"
Changed lines 29-32 from:
􏰂 *  Places (circles), which represent the data states. DLCM always starts with the place CREATED and finishes with the TERMINATED place.
􏰂 *  Transitions (rectangles), which represent the operations performed on the data items.
 * Tokens (black dots), which represents data items. Each token has identifiers, which allows to link the token with  the actual piece of information in the system; for instance a filename.
to:
*  Places (circles), which represent the data states. DLCM always starts with the place CREATED and finishes with the TERMINATED place.
*  Transitions (rectangles), which represent the operations performed on the data items.
* Tokens (black dots), which represents data items. Each token has identifiers, which allows to link the token with  the actual piece of information in the system; for instance a filename.
Changed lines 36-38 from:
 * DLCM '''composition''' is the mechanism by which we can assemble together  several DLCM.
 * Data '''Tags''' and  transition '''Guards''' are a powerful way of filtering data, conveying information across the systems and trigger handler execution only on specific data.
 * DLCM verification and online checking.
to:
* DLCM '''composition''' is the mechanism by which we can assemble together  several DLCM.
* Data '''Tags''' and  transition '''Guards''' are a powerful way of filtering data, conveying information across the systems and trigger handler execution only on specific data.
* DLCM verification and online checking.
March 19, 2015, at 01:24 PM by 140.77.13.170 -
Changed lines 29-31 from:
􏰂 *  Places (circles), which represent the data states. DLCM always starts with the place CREATED and finishes
􏰂 *  Transitions
(rectangles), which represent the operations performed on the data
to:
􏰂 *  Places (circles), which represent the data states. DLCM always starts with the place CREATED and finishes with the TERMINATED place.
􏰂 *  Transitions
(rectangles), which represent the operations performed on the data items.
 * Tokens (black dots), which represents data items. Each token has identifiers, which allows to link the token with  the actual piece of information in the system; for instance a filename.

When the DLCM evolves, the token will pass from a place to another, which ''fires a transition''. Active Data developers can attach their code to each transition in the DLCM. The '''handler code''' is then executed whenever the transition is fired. The system is distributed, thus any node in the network can publish transition and receive transition notification; this is how we can develop DLCM distributed applications.

In addition, Active Data proposes a set of high level features :
 * DLCM '''composition''' is the mechanism by which we can assemble together  several DLCM.
 * Data '''Tags''' and  transition '''Guards''' are a powerful way of filtering data, conveying information across the systems and trigger handler execution only on specific data.
 * DLCM verification and online checking.
 
 
March 19, 2015, at 01:10 PM by 140.77.13.170 -
Changed lines 26-30 from:
to:
The Data Life Cycle Model (DLCM) is loosely based on the Petri Nets formalism. Petri Nets have some key advantages to represent DLCM: they are graphical and easy to understand by end-users and still they are powerful tools to deal complex situations that one can find in distributed systems (synchronistic).

Thus, a DLCM is made of
􏰂 *  Places (circles), which represent the data states. DLCM always starts with the place CREATED and finishes
􏰂 *  Transitions (rectangles), which represent the operations performed on the data
March 19, 2015, at 10:32 AM by 140.77.13.170 -
Added lines 22-25:


%rframe text-align=center margin-top=5px margin-right=15px margin bottom=5px margin-left=25px% http://graal.ens-lyon.fr/~gfedak/dlc.png"Data Life Cycle Model"

March 19, 2015, at 10:24 AM by 140.77.13.170 -
Changed lines 18-20 from:


(:slideshare active-data-a-programming-model-to-manage-data-life-cycle-across-heterogeneous-systems-and-infrastructures:)
to:
(:slideshare 21991329:)
March 19, 2015, at 10:19 AM by 140.77.13.170 -
Changed lines 18-20 from:
(:slideshare 130527042012:)

to:


(:slideshare active-data-a-programming-model-to-manage-data-life-cycle-across-heterogeneous-systems-and-infrastructures:)

Changed line 54 from:
* ''MapReduce on Desktop Grids with BitDew and Active Data'' Anthony Simonet, Lu Lu, Xuanhua Shi, Bing Tang, Jose-Francisco Saray, and Gilles Fedak. In Grid5K Winter School, France, 2013. [[http://graal.ens-lyon.fr/~gfedak/thesis/mapreduce.grid5000.13.pdf | PDF ]]
to:
* ''MapReduce on Desktop Grids with BitDew and Active Data'' Anthony Simonet, Lu Lu, Xuanhua Shi, Bing Tang, Jose-Francisco Saray, and Gilles Fedak. In Grid5K Winter School, France, 2013. [[http://graal.ens-lyon.fr/~gfedak/thesis/mapreduce.grid5000.13.pdf | PDF ]]
March 19, 2015, at 10:11 AM by 140.77.13.170 -
Changed lines 18-19 from:

to:
(:slideshare 130527042012:)

Deleted line 52:
March 19, 2015, at 09:59 AM by 140.77.13.170 -
Changed lines 8-17 from:
''Active Data'' is new approach to automate and improve the expressiveness of data management applications. It consists of

*  a '''formal model''' for Data Life Cycle, based on Petri Net, that allows to describe and expose data life cycle across heterogeneous systems and infrastructures.

* a '''programming model''' allows code execution at each stage of the data life cycle: routines provided by programmers are executed when a set of events (creation, replication, transfer, deletion) happen to any data.


!!!
Source Code

to:
''Active Data'' is new approach to automate and improve the expressiveness of data management applications :

* allows to reason about data sets when there are handled by distributed and heterogeneous systems and infrastructures.

* consists of a '''formal model''' that captures the essential data life cycle stages and properties : creation, deletion, replication, derivation, transient unavailability, uniform naming, and many more 

* provides a '''programming model''' that simplify the development of data life cycle management applications. Active Data allows code execution at each stage of the data life cycle: routines provided by programmers are executed when a set of events (creation, replication, transfer, deletion) happen to any data.

* allows to legacy systems to expose their intrinsic data life cycle.



!! How Does it Work ?


!! Source Code

Deleted line 51:
March 18, 2015, at 03:08 PM by 140.77.13.170 -
March 18, 2015, at 03:06 PM by 140.77.13.170 -
Changed lines 5-7 from:
A key point is to handle the complexity of the ''Data Life Cycle'', i.e. the various operations performed on data: transfer, archiving, replication, deletion, etc. Indeed, data-intensive applications span over a large variety of devices and e-infrastructures which implies that many systems are involved in data management and processing.

to:
A key point is to handle the complexity of the ''''Data Life Cycle'', i.e. the various operations performed on data: transfer, archiving, replication, deletion, etc. Indeed, data-intensive applications span over a large variety of devices and e-infrastructures which implies that many systems are involved in data management and processing.

Changed lines 10-17 from:
*  a ''formal model'' for Data Life Cycle, based on Petri Net, that allows to describe and expose data life cycle across heterogeneous systems and infrastructures.

* a ''programming model'' allows code execution at each stage of the data life cycle: routines provided by programmers are executed when a set of events (creation, replication, transfer, deletion) happen to any data.




to:
*  a '''formal model''' for Data Life Cycle, based on Petri Net, that allows to describe and expose data life cycle across heterogeneous systems and infrastructures.

* a '''programming model''' allows code execution at each stage of the data life cycle: routines provided by programmers are executed when a set of events (creation, replication, transfer, deletion) happen to any data.


!!! Source Code

Changed lines 33-45 from:
!! Publications
to:
!! Publications


* ''Active Data: A Programming Model for Managing Big Data Life Cycle''
Anthony Simonet Gilles Fedak Matei Ripeanu. Technical Report. Submitted to FGCS.  [[ https://hal.inria.fr/hal-00729002 | HAL ]]

*  ''Active Data to Provide Smart Data Surveillance to E-Science Users'' A. Simonet, K. Chard, G. Fedak, I. Foster In Proceedings of '''EuromicroPDP'15''', Turku Finland, March 4-6, 2015  [[http://graal.ens-lyon.fr/~gfedak/thesis/active-data.euromicropdp.2015.pdf | PDF ]]

* ''Active Data: A Data-Centric Approach to Data Life-Cycle Management'' Anthony Simonet, Gilles Fedak, Matei Ripeanu and Samer Al-Kiswany. 8th Parallel Data Storage Workshop ('''PDSW'13'''), Proceedings of SC13 workshops, Denver, November, 2013 (position paper 5 pages)  [[http://graal.ens-lyon.fr/~gfedak/thesis/active-data.pdsw.2013.pdf | PDF ]]

* ''MapReduce on Desktop Grids with BitDew and Active Data'' Anthony Simonet, Lu Lu, Xuanhua Shi, Bing Tang, Jose-Francisco Saray, and Gilles Fedak. In Grid5K Winter School, France, 2013. [[http://graal.ens-lyon.fr/~gfedak/thesis/mapreduce.grid5000.13.pdf | PDF ]]

March 18, 2015, at 02:49 PM by 140.77.13.170 -
Changed lines 1-2 from:
!Active Data : Managing Data-Life Cycle on Heterogeneous Systems and Infrastructures
to:
!! Active Data : Managing Data-Life Cycle on Heterogeneous Systems and Infrastructures
Changed lines 22-25 from:
! Publications

!
Use Cases and On Going Projects
to:

!! Use Case: Data Surveillance Framework

In collaboration with Ian Foster and Kyle Chard from Argonne National Lab/University of Chicago, we designed a Data Surveillance Framework for the Advanced Photon Source experiment.

!! On going Projects
Changed lines 29-33 from:
* We designed
to:
* Asma Ben Cheick (Ph.D sutudent) and Heittem Abbes (Associate Professor Univ. Tunis) are working on using AD as a model for describing data-centric application deployment on IaaS infrastructures.
*
 

!! Publications
March 18, 2015, at 02:44 PM by 140.77.13.170 -
Changed lines 1-3 from:
Active Data is a programming model and a runtime environment to handle the management of data life cycle on heterogeneous systems and infrastructures.

[[ https://gforge.inria.fr/frs/?group_id=4190 | Download Active Data source code ]]
to:
!Active Data : Managing Data-Life Cycle on Heterogeneous Systems and Infrastructures

The Big Data challenge consists in managing, storing, analyzing and visualizing these huge and ever growing data sets to extract sense and knowledge. As the volume of data grows exponentially, the management of these data becomes more complex in proportion.

A key point is to handle the complexity of the ''Data Life Cycle'', i.e. the various operations performed on data: transfer, archiving, replication, deletion, etc. Indeed, data-intensive applications span over a large variety of devices and e-infrastructures which implies that many systems are involved in data management and processing.


''Active Data'' is new approach to automate and improve the expressiveness of data management applications. It consists of

*  a ''formal model'' for Data Life Cycle, based on Petri Net, that allows to describe and expose data life cycle across heterogeneous systems and infrastructures.

* a ''programming model'' allows code execution at each stage of the data life cycle: routines provided by programmers are executed when a set of events (creation, replication, transfer, deletion) happen to any data.





You can download the source code here

[[ https://gforge.inria.fr/frs/?group_id=4190 | Download Active Data source code ]]

! Publications

! Use Cases and On Going Projects

* Active Data is a joint work with Matei Ripeanu from UCB (Vancouver/Canada) and Samer
* We designed
October 06, 2014, at 02:33 PM by 140.77.13.170 -
Changed line 3 from:
[[Download Active Data source code | https://gforge.inria.fr/frs/?group_id=4190]]
to:
[[ https://gforge.inria.fr/frs/?group_id=4190 | Download Active Data source code ]]
October 06, 2014, at 02:32 PM by 140.77.13.170 -
Changed lines 1-3 from:
Active Data is a programming model and a runtime environment to handle the management of data life cycle on heterogeneous systems and infrastructures.
to:
Active Data is a programming model and a runtime environment to handle the management of data life cycle on heterogeneous systems and infrastructures.

[[Download Active Data source code | https://gforge.inria.fr/frs/?group_id=4190]]
April 17, 2014, at 08:09 AM by 140.77.13.170 -
Added line 1:
Active Data is a programming model and a runtime environment to handle the management of data life cycle on heterogeneous systems and infrastructures.
GlossyBlue theme adapted by David Gilbert
Powered by PmWiki