[Saga-devel] saga-projects SVN commit 867: /papers/clouds/

[sjha at cct.lsu.edu]

User: sjha
Date: 2009/01/24 01:07 PM

Modified:
 /papers/clouds/
  saga_cloud_interop.tex

Log:
 minor changes..

File Changes:

Directory: /papers/clouds/
==========================

File [modified]: saga_cloud_interop.tex
Delta lines: +31 -48
===================================================================
--- papers/clouds/saga_cloud_interop.tex	2009-01-24 18:46:33 UTC (rev 866)
+++ papers/clouds/saga_cloud_interop.tex	2009-01-24 19:07:53 UTC (rev 867)
@@ -82,23 +82,24 @@
 \begin{abstract}
 %  The landscape of computing is getting Cloudy.
   SAGA is a high-level programming interface which provides the
-  ability to create distributed applications in an infrastructure
-  independent way.  In an earlier paper, we discussed how we have
-  developed MapReduce using SAGA, and how a SAGA-based MapReduce
-  provided i) infrastructure independence and ii) could be used to
-  utilize distributed infrastructure. In this paper, we use a
-  SAGA-based implementation of MapReduce, and demonstrate its
-  interoperability across Clouds and Grids.  We discuss how a range of
-  {\it cloud adapters} have been developed for SAGA.  The major
-  contribution of this paper is the demonstration -- possibly the
-  first ever, of interoperability between different Clouds and Grids,
-  without any changes to the application. Interestingly it is not the
-  case that our application uses different Clouds and Grids at
-  different instances of time, but that \sagamapreduce uses multiple,
-  different, heterogenous infrastracture concurrently and for the same
-  application. We do not focus on performance, but the
-  proof-of-concept and the illustrate the importance and power of
-  application-level interoperabilty.
+  ability to develop distributed applications in an infrastructure
+  independent way. In an earlier paper, we discussed how SAGA was used
+  to develop a version of MapReduce which was, infrastructure
+  independent and, had the ability to control the relative placement
+  of compute and data placement whilst utilizing distributed
+  infrastructure. In this paper, we use a SAGA-based implementation of
+  MapReduce, and demonstrate its interoperability across Clouds and
+  Grids.  We discuss how a range of {\it cloud adapters} have been
+  developed for SAGA.  The major contribution of this paper is the
+  demonstration -- possibly the first ever, of interoperability
+  between different Clouds and Grids, without any changes to the
+  application. Interestingly \sagamapreduce uses multiple, different,
+  heterogenous infrastructure concurrently and for the same
+  application, and not different Clouds and Grids at different
+  instances of time.  We do not focus on performance, but a
+  proof-of-concept of application-level interoperabilty and work to
+  illustrate the importance and power of application-level
+  interoperabilty.
 \end{abstract}
 
 \section{Introduction} {\textcolor{blue} {SJ}}
@@ -243,17 +244,16 @@
 
 \subsubsection*{Why Interoperability:}
 \begin{itemize}
-\item Intellectual curiosity, what programming challenges does this 
-  bring about?
-\item Infrastructure independent programming
-\item Here we discuss homgenous workers, but workers (tasks) can be
-  heterogenous and thus may have greater data-compute affinity or
-  data-data affinity, which makes it more prudent to map to Cloud than
-  regular grid environments (or vice-versa). What about complex
-  dependency and inter-relationship between sub-tasks.
-
-\item Economic Models of computing, influence programming models and require
-explicity  (already discussed)
+% \item Intellectual curiosity, what programming challenges does this 
+%   bring about?
+% \item Infrastructure independent programming
+% \item Here we discuss homgenous workers, but workers (tasks) can be
+%   heterogenous and thus may have greater data-compute affinity or
+%   data-data affinity, which makes it more prudent to map to Cloud than
+%   regular grid environments (or vice-versa). What about complex
+%   dependency and inter-relationship between sub-tasks.
+\item Economic Models of computing, influence programming models and
+  require explicity (already discussed)
 \end{itemize}
 
 \subsubsection*{Grid vs Cloud Interoperabiltiy}
@@ -273,21 +273,6 @@
   interoperabiltiy the differences are minor and inconsequential.
 \end{itemize}
 
-
-\subsection{Clouds: An Emerging Distributed Infrastructure}
-{\textcolor{blue} {KS}}
-
-In our opinion the primary distinguishing feature of Grids and
-Clouds  is...
-
-\subsection{Amazon EC2:} 
-
-\subsection{Eucalyptus}
-
-
-GumboCloud, ECP etc
-
-
 \section{SAGA}  {\textcolor{blue} {SJ}}
 
 
@@ -335,14 +320,12 @@
   common considerations such as when to move the data to the machine
   or when to process it locally.}
 
+\subsection{SAGA: An interface to Clouds and Grids}{\bf AM}
+
 \subsection{Maybe  a subsection or a paragraph on the role of Adaptors} {\textcolor{blue} {KS}}
+%Forward reference the section on the role of adaptors.. 
 
 
-
-Forward reference the section on the role of adaptors.. 
-
-\subsection{SAGA: An interface to Clouds and Grids}{\bf AM}
-
 \section{Interfacing SAGA to Clouds: The role of Adaptors}
 
 As alluded to, there is a proliferation of Clouds and Cloud-like