[Saga-devel] saga-projects SVN commit 910: /papers/clouds/
amerzky at cct.lsu.edu
amerzky at cct.lsu.edu
Thu Jan 29 05:50:09 CST 2009
User: amerzky
Date: 2009/01/29 05:50 AM
Added:
/papers/clouds/
saga-figure02.pdf
Modified:
/papers/clouds/
saga_cloud_interop.tex, saga_data_intensive.bib
Log:
Uhm, post submission fixes are almost useless, right? Anyway:
fixed some references, and moved spacings around. Shantenu,
I hope I added the correct image, from the data_intensiv paper?
Best, Andre
File Changes:
Directory: /papers/clouds/
==========================
File [added]: saga-figure02.pdf
Delta lines: +0 -0
===================================================================
(Binary files differ)
Property changes on: papers/clouds/saga-figure02.pdf
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
File [modified]: saga_cloud_interop.tex
Delta lines: +12 -12
===================================================================
--- papers/clouds/saga_cloud_interop.tex 2009-01-29 08:59:04 UTC (rev 909)
+++ papers/clouds/saga_cloud_interop.tex 2009-01-29 11:49:46 UTC (rev 910)
@@ -237,20 +237,20 @@
problem instance}. Specifically, our approach is to take
\sagamapreduce and to use the {\it same} implementation of
\sagamapreduce to solve the same instance of the word counting
-problem, by using different worker distribution configurations overs
+problem, by using different worker distributions over
Clouds and Grid systems, and thereby also test for interoperability
between different flavours of Clouds as well as between Clouds and
Grids.
Interoperability amongst Clouds and Grids can be achieved at different
-levels. For example, service-level interoperability amongt Grids has
+levels. For example, service-level interoperability amongst Grids has
been demonstrated by the OGF-GIN group; application-level
interoperability (ALI) remains a harder goal to achieve. Clouds
provide services at different levels (Iaas, PaaS, SaaS); standard
interfaces to these different levels do not exist. Though there is
little business motivation for Cloud providers to define, implement
and support new/standard interfaces, there is a case to be made that
-applications would benefit from multiple Cloud interoperability. We
+applications would benefit from Cloud interoperability. We
argue that by addressing interoperability at the application-level
this can be easily achieved. % But first we provide some features of
ALI arises when, say other than compiling on a different or new
@@ -370,7 +370,7 @@
\includegraphics[scale=0.5]{saga-figure02.pdf}
\caption{In addition to the programmer's interface,
the other important components of the landscape are the SAGA engine,
- and functional adaptors.} \vspace{-2em}
+ and functional adaptors.} \vspace{-3em}
\label{saga_figure}
\end{figure}
@@ -561,13 +561,13 @@
adaptor).
The security credentials used by the internal ssh job service
-instance are derived from the security credentials used to create or
-access the VM instance; upon VM instance creation, an AWS keypair is
+instance are derived from the credentials used to create
+the VM instance; upon VM instance creation, an AWS keypair is
used to authenticate the user against her 'cloud account'. That
keypair is automatically registered at the new VM instance to allow
for remote ssh access. The aws context adaptor collects both the
public and private AWS keys\footnote{The public key needs to be
- collected from the remote instance}, creates a respective ssh
+ collected from the remote instance.}, creates a respective ssh
context, and thus allows the ssh adaptors to perform job and file
based SAGA operations on the VM instance.
@@ -619,7 +619,7 @@
j.wait ();
} // break contact to GRAM
\end{mycode}
- \caption{\label{gramjob}Job launch via Gram }
+ \caption{\label{gramjob}Job launch on a Grid via Gram\vspace*{-2em}}
\end{center}
\upp
\end{figure}
@@ -640,7 +640,7 @@
j.wait ();
} // shut down VM instance
\end{mycode}
- \caption{\label{vmjob} Job launch via VM}
+ \caption{\label{vmjob} Job launch on a VM via ssh\vspace*{-2em}}
\end{center}
\upp
\end{figure}
@@ -1203,7 +1203,7 @@
\caption{Performance data for different configurations of worker placements. The master places the workers on either Clouds or on the TeraGrid (QueenBee). The configurations -- separated by horizontal lines, are classified as either having all workers on EC2, all workers on the TeraGrid and finally workers divided between the TeraGrid and EC2. Unless otherwise explicitly indicated
by a number in parenthesis, every worker is assigned to a unique VM. In the
final set of rows, the number in parenthesis indicates the number of VMs used. It is interesting to note the significant spawning times, and its dependence on the number of VM, which typically increase with the number of VMs. $T_{spawn}$ does not include instantiation of the VM.}
-\label{stuff}
+\label{stuff-1}
\upp
\upp
\end{table}
@@ -1239,8 +1239,8 @@
on TeraGrid, Eucalyptus-Cloud and EC2. The first set of data
establishes Cloud-Cloud interoperability. The second set
(rows 5- 11) represent interoperability between Grids-Clouds (EC2).
- The experimental conditions and measurements are similar to Table 1.}
-\label{stuff}
+ The experimental conditions and measurements are similar to Table 1.\vspace*{-1em}}
+\label{stuff-2}
\upp
\upp
\end{table}
File [modified]: saga_data_intensive.bib
Delta lines: +14 -5
===================================================================
--- papers/clouds/saga_data_intensive.bib 2009-01-29 08:59:04 UTC (rev 909)
+++ papers/clouds/saga_data_intensive.bib 2009-01-29 11:49:46 UTC (rev 910)
@@ -26,13 +26,12 @@
@inproceedings{mapreduce-paper,
Address = {Berkeley, CA, USA},
Author = {Jeffrey Dean and Sanjay Ghemawat},
- Booktitle = {OSDI'04: Proceedings of the 6th conference on Symposium on Opearting Sys
-tems Design \& Implementation},
+ Booktitle = {OSDI'04: Proceedings of the 6th conference on Symposium on Operating Systems Design \& Implementation},
Date-Added = {2008-02-23 20:47:01 -0600},
Date-Modified = {2008-05-12 23:43:10 +0200},
Location = {San Francisco, CA},
Pages = {137--150},
- OPT Publisher = {USENIX Association},
+ Publisher = {USENIX Association},
Title = {{MapReduce: Simplified Data Processing on Large Clusters}},
Year = {2004}}
@@ -6765,8 +6764,18 @@
url = {http://www.gridbus.org/papers/hpcc2008_keynote_cloudcomputing.pdf}}
- at misc{eucalyptus, note = {Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems (EUCALYPTUS), http://eucalyptus.cs.ucsb.edu/}}
+ at misc{eucalyptus_url, note = {Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems (EUCALYPTUS), http://eucalyptus.cs.ucsb.edu/}}
+
+ at article{eucalyptus,
+ title = {{The Eucalyptus Open-source Cloud-computing System}},
+ author = {Daniel Nurmi {\it et al}},
+ booktitle = {{Cloud Computing and Its Applications}},
+ address = {{Chicago, Illinois}},
+ month = {October},
+ year = 2008
+}
+
@misc{nimbus, note = {NIMBUS http://workspace.globus.org/}}
@@ -6785,4 +6794,4 @@
@misc{montagecloud, note = {The Cost of Doing Science on the Cloud: The Montage
Example, Ewa Deelman et al, Proceedings of SC08, Austin, Texas, draft available at
-\url{http://pegasus.isi.edu/publications/2008/deelman_sc08_corrected.pdf}}}
\ No newline at end of file
+\url{http://pegasus.isi.edu/publications/2008/deelman_sc08_corrected.pdf}}}
More information about the saga-devel
mailing list