May 2013 - Triton-commits - mailman3.cels.anl.gov

branch, master, updated. 343c0ba881185f78c2e6dc4978546db60beea86d
by noreply＠mcs.anl.gov 26 May '13

26 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 343c0ba881185f78c2e6dc4978546db60beea86d (commit) from 407b0ad3e96c93853813f8c2cb7b140abda35173 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 343c0ba881185f78c2e6dc4978546db60beea86d Author: cengiz <cengiz.k(a)uconn.edu> Date: Sun May 26 10:01:41 2013 -0400 Removed punch ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/proposed_model.tex | 13 +++---------- 1 files changed, 3 insertions(+), 10 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/proposed_model.tex b/papers/asg-osd/sections/proposed_model.tex index 0d4f0e7..be71654 100644 --- a/papers/asg-osd/sections/proposed_model.tex +++ b/papers/asg-osd/sections/proposed_model.tex @@ -88,8 +88,9 @@ The conditional flag can take a combination of four different values. \end{itemize} A successful write operation returns the size of the written data and the -newly assigned version number. - +newly assigned version number. It is also possible to do a write operation +with zero-length data. + \subsubsection{read} \textit{read} operation retrieves data from a sequential range of records. The @@ -128,14 +129,6 @@ conditional flag can take a combination of three different values. A successful read operation returns the number of the records read in addition to the version number of these records. -\subsubsection{punch} - -\textit{punch} operation removes data from the specified range of records. It -behaves almost the same with the write operation; it is basically a write with -zero-length data. Punch has the same input and output arguments with the write -operation and it can only be applied to a range of records. Objects and -containers do not support punch operation. - \subsubsection{reset} \textit{reset} operation returns an entity (container, object, fork or record) hooks/post-receive --

1 0

branch, master, updated. 407b0ad3e96c93853813f8c2cb7b140abda35173
by noreply＠mcs.anl.gov 26 May '13

26 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 407b0ad3e96c93853813f8c2cb7b140abda35173 (commit) from 7163a6c8b2406c32e6e8b6ec342e20b3fd69c6b0 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 407b0ad3e96c93853813f8c2cb7b140abda35173 Author: cengiz <cengiz.k(a)uconn.edu> Date: Sun May 26 09:35:49 2013 -0400 Added DAOS citation ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/paper.bib | 8 ++++++++ papers/asg-osd/sections/relatedwork.tex | 3 +-- 2 files changed, 9 insertions(+), 2 deletions(-) Diff of changes: diff --git a/papers/asg-osd/paper.bib b/papers/asg-osd/paper.bib index 6e93a3d..aaf1dfe 100644 --- a/papers/asg-osd/paper.bib +++ b/papers/asg-osd/paper.bib @@ -618,3 +618,11 @@ title = {{Design of an Intelligent Object-based Storage device}}, journal={2009-06-13). http://www. scribd. com/doc/2187280/NTFS-Documentation}, year={2004} } + +@inproceedings{daos, + author = {Lombardi, Johann and Zhen, Liang}, + title = {{DAOS Changes to Lustre}}, + publisher = {{Presented by Intel High Performance Data Division}}, + month = {April}, + year = {2013} +} diff --git a/papers/asg-osd/sections/relatedwork.tex b/papers/asg-osd/sections/relatedwork.tex index 3d31ccc..9bc08d5 100644 --- a/papers/asg-osd/sections/relatedwork.tex +++ b/papers/asg-osd/sections/relatedwork.tex @@ -1,4 +1,3 @@ -\todo{cite DAOS work from Lustre} Network-Attached Secure Disk (NASD)~\cite{gibson:storage} is the primary study on object-based storage and it led to specifications of standards~\cite{osd-3} for object-based storage. @@ -22,7 +21,7 @@ Panasas File System~\cite{Welch08scalableperformance} is built on object-based s OSD wire protocol of Panasas uses the operations from the OSD standard~\cite{osd-3} to enable byte-oriented access to data, to manipulate attributes and to create or delete objects. %Panasas clients use iSCSI/OSD protocol to access the object-based storage devices. -Lustre~\cite{lustre-web} is a distributed file system based on object-based storage. Object Storage +Lustre~\cite{lustre-web, daos} is a distributed file system based on object-based storage. Object Storage Server (OSS) in Lustre is responsible for providing access to file data stored in objects on Object Storage Targets (OSTs). %Lustre has two types of servers; Metadata Server (MDS) and Object Storage Server (OSS). Actual metadata is hooks/post-receive --

1 0

branch, master, updated. 7163a6c8b2406c32e6e8b6ec342e20b3fd69c6b0
by noreply＠mcs.anl.gov 21 May '13

21 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 7163a6c8b2406c32e6e8b6ec342e20b3fd69c6b0 (commit) from 44651583ed8aee0b2efd4348fb3b3c1c5bb6e1e8 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 7163a6c8b2406c32e6e8b6ec342e20b3fd69c6b0 Author: Phil Carns <carns(a)mcs.anl.gov> Date: Tue May 21 16:31:36 2013 -0500 reminder to cite DAOS ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/relatedwork.tex | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/relatedwork.tex b/papers/asg-osd/sections/relatedwork.tex index 7a6f5ae..3d31ccc 100644 --- a/papers/asg-osd/sections/relatedwork.tex +++ b/papers/asg-osd/sections/relatedwork.tex @@ -1,3 +1,4 @@ +\todo{cite DAOS work from Lustre} Network-Attached Secure Disk (NASD)~\cite{gibson:storage} is the primary study on object-based storage and it led to specifications of standards~\cite{osd-3} for object-based storage. hooks/post-receive --

1 0

branch, master, updated. 44651583ed8aee0b2efd4348fb3b3c1c5bb6e1e8
by noreply＠mcs.anl.gov 17 May '13

17 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 44651583ed8aee0b2efd4348fb3b3c1c5bb6e1e8 (commit) from 6f02000a79de3881526a8458b97e4c92ddd458d6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 44651583ed8aee0b2efd4348fb3b3c1c5bb6e1e8 Author: Phil Carns <carns(a)mcs.anl.gov> Date: Fri May 17 15:27:35 2013 -0400 presentations from 2013-05 meeting ----------------------------------------------------------------------- Summary of changes: .../130509 Clemson SSM v1.5.ppt | Bin 0 -> 1923072 bytes .../project-meeting-2013-05/ASG_Benafsh.pptx | Bin 0 -> 752999 bytes presentations/project-meeting-2013-05/ASGrrb.pptx | Bin 0 -> 961524 bytes .../project-meeting-2013-05/Additional Slides.pptx | Bin 0 -> 93520 bytes .../LWDLS_by_Zhiwei_Sun_UAB.pdf | Bin 0 -> 1471337 bytes .../project-meeting-2013-05/Quad_Chart_Clemson.ppt | Bin 0 -> 183296 bytes .../Sandia_Slides_Dr_Shen.pptx | Bin 0 -> 1270300 bytes .../Sandia_Slides_Guoxin.pptx | Bin 0 -> 593055 bytes .../project-meeting-2013-05/pt_asg_animation.pptx | Bin 0 -> 353946 bytes .../quadchart_Shen_Clemson University.pptx | Bin 0 -> 265233 bytes .../project-meeting-2013-05/sandia-converted.pptx | Bin 0 -> 198040 bytes .../tamu-quadchart-converted.pptx | Bin 0 -> 205035 bytes .../project-meeting-2013-05/tamu-quadchart.pdf | Bin 0 -> 282380 bytes .../triton-quadchart.pptx | Bin 538803 -> 538803 bytes .../uab-quadchart-v1.2.pptx | Bin 0 -> 236774 bytes 15 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 presentations/project-meeting-2013-05/130509 Clemson SSM v1.5.ppt create mode 100644 presentations/project-meeting-2013-05/ASG_Benafsh.pptx create mode 100644 presentations/project-meeting-2013-05/ASGrrb.pptx create mode 100644 presentations/project-meeting-2013-05/Additional Slides.pptx create mode 100644 presentations/project-meeting-2013-05/LWDLS_by_Zhiwei_Sun_UAB.pdf create mode 100644 presentations/project-meeting-2013-05/Quad_Chart_Clemson.ppt create mode 100644 presentations/project-meeting-2013-05/Sandia_Slides_Dr_Shen.pptx create mode 100644 presentations/project-meeting-2013-05/Sandia_Slides_Guoxin.pptx create mode 100644 presentations/project-meeting-2013-05/pt_asg_animation.pptx create mode 100644 presentations/project-meeting-2013-05/quadchart_Shen_Clemson University.pptx create mode 100755 presentations/project-meeting-2013-05/sandia-converted.pptx create mode 100644 presentations/project-meeting-2013-05/tamu-quadchart-converted.pptx create mode 100644 presentations/project-meeting-2013-05/tamu-quadchart.pdf copy presentations/{ => project-meeting-2013-05}/triton-quadchart.pptx (100%) create mode 100644 presentations/project-meeting-2013-05/uab-quadchart-v1.2.pptx Diff of changes: diff --git a/presentations/project-meeting-2013-05/130509 Clemson SSM v1.5.ppt b/presentations/project-meeting-2013-05/130509 Clemson SSM v1.5.ppt new file mode 100644 index 0000000..ed655b6 Binary files /dev/null and b/presentations/project-meeting-2013-05/130509 Clemson SSM v1.5.ppt differ diff --git a/presentations/project-meeting-2013-05/ASG_Benafsh.pptx b/presentations/project-meeting-2013-05/ASG_Benafsh.pptx new file mode 100644 index 0000000..40fae1e Binary files /dev/null and b/presentations/project-meeting-2013-05/ASG_Benafsh.pptx differ diff --git a/presentations/project-meeting-2013-05/ASGrrb.pptx b/presentations/project-meeting-2013-05/ASGrrb.pptx new file mode 100644 index 0000000..b873553 Binary files /dev/null and b/presentations/project-meeting-2013-05/ASGrrb.pptx differ diff --git a/presentations/project-meeting-2013-05/Additional Slides.pptx b/presentations/project-meeting-2013-05/Additional Slides.pptx new file mode 100644 index 0000000..01bdf35 Binary files /dev/null and b/presentations/project-meeting-2013-05/Additional Slides.pptx differ diff --git a/presentations/project-meeting-2013-05/LWDLS_by_Zhiwei_Sun_UAB.pdf b/presentations/project-meeting-2013-05/LWDLS_by_Zhiwei_Sun_UAB.pdf new file mode 100644 index 0000000..5da0a62 Binary files /dev/null and b/presentations/project-meeting-2013-05/LWDLS_by_Zhiwei_Sun_UAB.pdf differ diff --git a/presentations/project-meeting-2013-05/Quad_Chart_Clemson.ppt b/presentations/project-meeting-2013-05/Quad_Chart_Clemson.ppt new file mode 100644 index 0000000..7cc3cbf Binary files /dev/null and b/presentations/project-meeting-2013-05/Quad_Chart_Clemson.ppt differ diff --git a/presentations/project-meeting-2013-05/Sandia_Slides_Dr_Shen.pptx b/presentations/project-meeting-2013-05/Sandia_Slides_Dr_Shen.pptx new file mode 100644 index 0000000..013d289 Binary files /dev/null and b/presentations/project-meeting-2013-05/Sandia_Slides_Dr_Shen.pptx differ diff --git a/presentations/project-meeting-2013-05/Sandia_Slides_Guoxin.pptx b/presentations/project-meeting-2013-05/Sandia_Slides_Guoxin.pptx new file mode 100644 index 0000000..b64d001 Binary files /dev/null and b/presentations/project-meeting-2013-05/Sandia_Slides_Guoxin.pptx differ diff --git a/presentations/project-meeting-2013-05/pt_asg_animation.pptx b/presentations/project-meeting-2013-05/pt_asg_animation.pptx new file mode 100644 index 0000000..2035c71 Binary files /dev/null and b/presentations/project-meeting-2013-05/pt_asg_animation.pptx differ diff --git a/presentations/project-meeting-2013-05/quadchart_Shen_Clemson University.pptx b/presentations/project-meeting-2013-05/quadchart_Shen_Clemson University.pptx new file mode 100644 index 0000000..b33ba14 Binary files /dev/null and b/presentations/project-meeting-2013-05/quadchart_Shen_Clemson University.pptx differ diff --git a/presentations/project-meeting-2013-05/sandia-converted.pptx b/presentations/project-meeting-2013-05/sandia-converted.pptx new file mode 100755 index 0000000..6c49ccc Binary files /dev/null and b/presentations/project-meeting-2013-05/sandia-converted.pptx differ diff --git a/presentations/project-meeting-2013-05/tamu-quadchart-converted.pptx b/presentations/project-meeting-2013-05/tamu-quadchart-converted.pptx new file mode 100644 index 0000000..1745035 Binary files /dev/null and b/presentations/project-meeting-2013-05/tamu-quadchart-converted.pptx differ diff --git a/presentations/project-meeting-2013-05/tamu-quadchart.pdf b/presentations/project-meeting-2013-05/tamu-quadchart.pdf new file mode 100644 index 0000000..feb9941 Binary files /dev/null and b/presentations/project-meeting-2013-05/tamu-quadchart.pdf differ diff --git a/presentations/project-meeting-2013-05/uab-quadchart-v1.2.pptx b/presentations/project-meeting-2013-05/uab-quadchart-v1.2.pptx new file mode 100644 index 0000000..3d2bb3f Binary files /dev/null and b/presentations/project-meeting-2013-05/uab-quadchart-v1.2.pptx differ hooks/post-receive --

1 0

branch, master, updated. 6f02000a79de3881526a8458b97e4c92ddd458d6
by noreply＠mcs.anl.gov 17 May '13

17 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 6f02000a79de3881526a8458b97e4c92ddd458d6 (commit) from 430b46fef0258c52b2cc3d77ff935682a77a9a1d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 6f02000a79de3881526a8458b97e4c92ddd458d6 Author: Dries Kimpe <dkimpe(a)mcs.anl.gov> Date: Fri May 17 14:18:32 2013 -0500 Directory for project meeting ----------------------------------------------------------------------- Summary of changes: .../triton-yearlymeeting-2013-05.pptx | Bin 1360346 -> 1360346 bytes 1 files changed, 0 insertions(+), 0 deletions(-) rename presentations/{ => project-meeting-2013-05}/triton-yearlymeeting-2013-05.pptx (100%) Diff of changes: hooks/post-receive --

1 0

branch, master, updated. 430b46fef0258c52b2cc3d77ff935682a77a9a1d
by noreply＠mcs.anl.gov 16 May '13

16 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 430b46fef0258c52b2cc3d77ff935682a77a9a1d (commit) from 53aa5590c3ab46578e6a7884d8f2d9e9c1d217dd (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 430b46fef0258c52b2cc3d77ff935682a77a9a1d Author: cengiz <cengiz.k(a)uconn.edu> Date: Thu May 16 20:35:34 2013 -0400 Some more minor updates to the conclusion ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/conclusion.tex | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/conclusion.tex b/papers/asg-osd/sections/conclusion.tex index d3d0695..904f0c2 100644 --- a/papers/asg-osd/sections/conclusion.tex +++ b/papers/asg-osd/sections/conclusion.tex @@ -1,6 +1,6 @@ In this paper, we presented a new object-based storage model, ASG, introduced its architecture and primitives and described couple of use cases that can be based on this model. As the use cases clearly show, ASG storage -model is flexible and can be a starting point to build complex storage +model is flexible and can act as a starting point to build complex storage applications. Features supported by ASG storage model makes it possible to support requirements of common data models. hooks/post-receive --

1 0

branch, master, updated. 53aa5590c3ab46578e6a7884d8f2d9e9c1d217dd
by noreply＠mcs.anl.gov 16 May '13

16 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 53aa5590c3ab46578e6a7884d8f2d9e9c1d217dd (commit) from 3851008bf6d0b35cf488c766e6f1e8bcdbd453a5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 53aa5590c3ab46578e6a7884d8f2d9e9c1d217dd Author: cengiz <cengiz.k(a)uconn.edu> Date: Thu May 16 20:29:56 2013 -0400 Modified conclusion *Made sure there is no sentence talking about 'modifying' ASG model ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/conclusion.tex | 9 +++------ 1 files changed, 3 insertions(+), 6 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/conclusion.tex b/papers/asg-osd/sections/conclusion.tex index d90c2a9..d3d0695 100644 --- a/papers/asg-osd/sections/conclusion.tex +++ b/papers/asg-osd/sections/conclusion.tex @@ -1,9 +1,6 @@ -In this paper, we have introduced a new object-based storage model, ASG, +In this paper, we presented a new object-based storage model, ASG, introduced its architecture and primitives and described couple of use cases that can be based on this model. As the use cases clearly show, ASG storage model is flexible and can be a starting point to build complex storage -systems. Features supported by ASG storage model makes it possible to support -requirements of common data models. We also believe there is room for -potential development of ASG storage model in future work. ASG storage model -can be further developed and enriched to support other common data models not -mentioned in this paper; such as snapshots and dynamic namespaces. +applications. Features supported by ASG storage model makes it possible to support +requirements of common data models. hooks/post-receive --

1 0

branch, master, updated. 3851008bf6d0b35cf488c766e6f1e8bcdbd453a5
by noreply＠mcs.anl.gov 16 May '13

16 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via 3851008bf6d0b35cf488c766e6f1e8bcdbd453a5 (commit) from e8fdc3701ef3de292c448d96585b908d13630a6b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 3851008bf6d0b35cf488c766e6f1e8bcdbd453a5 Author: cengiz <cengiz.k(a)uconn.edu> Date: Thu May 16 19:56:28 2013 -0400 Minor changes to the introduction ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/introduction.tex | 28 ++++++++++++++-------------- 1 files changed, 14 insertions(+), 14 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/introduction.tex b/papers/asg-osd/sections/introduction.tex index 3d98b19..8353b21 100644 --- a/papers/asg-osd/sections/introduction.tex +++ b/papers/asg-osd/sections/introduction.tex @@ -1,20 +1,19 @@ %\textit{why did object-based storage model come out?} Storage technology has improved rapidly over time, particularly in terms of -storage density, but storage throughput has not kept pace with advances in -computational performance. This has trend has led to increased demand for +storage density; but storage throughput has not kept pace with advances in +computational performance. This trend has led to increased demand for large-scale storage systems that aggregate and coordinate many storage devices, in turn driving the need for better abstractions to manage those storage devices. Object-based storage~\cite{1222722, osd-3} has become the -most popular underlying model for -referencing and accessing data distributed over large numbers of storage -devices in these systems. +most popular underlying model for referencing and accessing data distributed +over large numbers of storage devices in these systems. An \textit{object} is an ordered logical collection of bytes with a numerical -identifier. Objects consist of data, attributes, and device managed metadata +identifier. Objects consist of data, attributes and device managed metadata; such as security information~\cite{1222722, Welch08scalableperformance}. Objects have variable sizes and they can be used to store any kind of data. The object storage model abstracts away a variety -of resource-specific management tasks such as block allocation, space -management, and various forms of atomicity. However, it still allows +of resource-specific management tasks; such as block allocation, space +management and various forms of atomicity. However, it still allows considerable flexibility for a variety of higher level data models to be built atop it. Although object models were originally envisioned as a device level interface~\cite{osd-3}, today's large-scale storage systems more commonly @@ -42,7 +41,7 @@ existing object-based storage models are typically tailored to a particular use case or data model, making them difficult to reuse in other contexts. This situation also makes it difficult to share a common storage pool for different big data, cloud -storage, or HPC storage tasks, increasing management overhead and adding +storage or HPC storage tasks, increasing management overhead and adding complexity to the task of storage provisioning for facilities with diverse storage needs.\todo{should we have some simple figure showing the various data models sharing a unified storage pool?} @@ -50,12 +49,13 @@ data models sharing a unified storage pool?} In order to address this problem, we first begin by identifying some of the most popular large-scale data models in use today. The following list divides them into five categories with representative examples: +\todo{should we add citations for each example?} \begin{itemize} \item \textbf{Parallel file systems}: Lustre, GPFS, Panasas, PVFS, Ceph \item \textbf{Cloud object storage}: Amazon S3, Swift, Rados Gateway \item \textbf{MapReduce}: Google File System (GFS), Hadoop HDFS -\item \textbf{Key/Value Stores}: Dynamo, Redis, Hyperdex, Cassandra +\item \textbf{Key/Value stores}: Dynamo, Redis, Hyperdex, Cassandra \item \textbf{NOSQL}: BigQuery, MongoDB, CouchDB \todo{NOSQL is really broad when you get down to it. The things I'm listing here are really document-oriented or non-sql column stores. Maybe we should narrow this @@ -65,7 +65,7 @@ oriented non-sql examples in here somewhere though...} Note that these data models aren't necessarily mutually exclusive. For example, key/value stores are often considered to be a subset of the NOSQL -storage taxonomy, and many parallel file systems have been extended to support +storage taxonomy and many parallel file systems have been extended to support MapReduce workloads. We will refer to these classifications in the remainder of the paper for clarity, however, in order to simplify the discussion of use cases and requirements that are shared across groups of storage @@ -80,7 +80,7 @@ specialized already...} \resizebox{\columnwidth}{!}{ \begin{tabular}{c|c|c|c|c|c|c|} \cline{2-7} & \multicolumn{6}{c|}{\textbf{Requirements}} \\\cline{2-7} -& \rotatebox{90}{Concurrent Write Access} & \rotatebox{90}{Synchronization primitives} & \rotatebox{90}{Atomicity} & \rotatebox{90}{Layout Control} & \rotatebox{90}{Record Oriented Access} & \rotatebox{90}{Data Affinity} \\\hline +& \rotatebox{90}{Concurrent Write Access} & \rotatebox{90}{Synchronization Primitives} & \rotatebox{90}{Atomicity} & \rotatebox{90}{Layout Control} & \rotatebox{90}{Record Oriented Access} & \rotatebox{90}{Data Affinity} \\\hline \multicolumn{1}{|c|}{Parallel File System} & \cmark & \cmark & \cmark & & & \\\hline \multicolumn{1}{|c|}{Cloud Object Storage} & & & \cmark & & & \\\hline \multicolumn{1}{|c|}{Mapreduce} & & & & \cmark & & \\\hline @@ -95,13 +95,13 @@ specialized already...} Table~\ref{tbl:reqs} breaks down the large-scale storage data models in terms of core functionality requirements that differentiate them. Note that that all five data models share the common requirements of -scalability, high performance, fault tolerance, and concurrent read access, +scalability, high performance, fault tolerance and concurrent read access, which are not shown in the table. \todo{Spell out exactly what the requirements mean, some of these are not obvious.} \textcolor{red}{Temporary notes on requirements: layout control means ability to control or discover where data is placed in order to perform computation near the data, while data affinity means ability to -group related data together to improve spacial locality.} +group related data together to improve spatial locality.} \todo{somewhere note that there are underlying semantic differences between these models as well (eg. how you might want replication protocols to work), but those can be accomodated below the API we are proposing.} hooks/post-receive --

1 0

branch, master, updated. e8fdc3701ef3de292c448d96585b908d13630a6b
by noreply＠mcs.anl.gov 16 May '13

16 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via e8fdc3701ef3de292c448d96585b908d13630a6b (commit) from ba12e1b7bec33f2a1fbc1104c82618ef7ba04c59 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e8fdc3701ef3de292c448d96585b908d13630a6b Author: Dries Kimpe <dkimpe(a)mcs.anl.gov> Date: Thu May 16 16:02:49 2013 -0500 Made cleaner version of conditional algorithm fig ----------------------------------------------------------------------- Summary of changes: .../pdsw2012-conditional/conditional-2.pdf | Bin 0 -> 28226 bytes .../pdsw2012-conditional/conditional-2.png | Bin 0 -> 3610 bytes .../pdsw2012-conditional/conditional-2.svgz | Bin 0 -> 5387 bytes 3 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 presentations/pdsw2012-conditional/conditional-2.pdf create mode 100644 presentations/pdsw2012-conditional/conditional-2.png create mode 100644 presentations/pdsw2012-conditional/conditional-2.svgz Diff of changes: diff --git a/presentations/pdsw2012-conditional/conditional-2.pdf b/presentations/pdsw2012-conditional/conditional-2.pdf new file mode 100644 index 0000000..b34dca5 Binary files /dev/null and b/presentations/pdsw2012-conditional/conditional-2.pdf differ diff --git a/presentations/pdsw2012-conditional/conditional-2.png b/presentations/pdsw2012-conditional/conditional-2.png new file mode 100644 index 0000000..35f8499 Binary files /dev/null and b/presentations/pdsw2012-conditional/conditional-2.png differ diff --git a/presentations/pdsw2012-conditional/conditional-2.svgz b/presentations/pdsw2012-conditional/conditional-2.svgz new file mode 100644 index 0000000..b20429f Binary files /dev/null and b/presentations/pdsw2012-conditional/conditional-2.svgz differ hooks/post-receive --

1 0

branch, master, updated. ba12e1b7bec33f2a1fbc1104c82618ef7ba04c59
by noreply＠mcs.anl.gov 16 May '13

16 May '13

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "". The branch, master has been updated via ba12e1b7bec33f2a1fbc1104c82618ef7ba04c59 (commit) from b3de0ee358fb365fbb5cd12025bc8732c8e617a4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit ba12e1b7bec33f2a1fbc1104c82618ef7ba04c59 Author: cengiz <cengiz.k(a)uconn.edu> Date: Thu May 16 03:03:05 2013 -0400 Minor spelling changes to abstract *Third use case is ok imho ----------------------------------------------------------------------- Summary of changes: papers/asg-osd/sections/abstract.tex | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) Diff of changes: diff --git a/papers/asg-osd/sections/abstract.tex b/papers/asg-osd/sections/abstract.tex index e5775ef..9c1d5db 100644 --- a/papers/asg-osd/sections/abstract.tex +++ b/papers/asg-osd/sections/abstract.tex @@ -7,15 +7,15 @@ resources. Although many large-scale storage systems share common goals of performance, scalability and fault tolerance, their underlying object storage models are typically tailored to specific use cases and semantics, making it difficult to reuse them in other environments and leading to -unecessary fragmentation of data center storage facilities. In this paper +unnecessary fragmentation of data center storage facilities. In this paper we propose a new distributed object-based storage model that seeks to -unify the common underlying primitives for big data, cloud storage, +unify the common underlying primitives for big data, cloud storage and HPC storage. We investigate five popular categories of data models from these environments and determine the unique requirements that distinguish them. We then identify key features from previous object storage systems that address these requirements and explore how they can be unified effectively without sacrificing usability. We validate the -effectiveness of our approach with by evaluataing how the API could be +effectiveness of our approach by evaluating how the API could be used in the construction of three diverse but representative use cases: -a POSIX file system name space, a column-store NOSQL database, and a +a POSIX file system name space, a column-store NOSQL database and a \todo{is this third use case right?} data set with concurrent writers. hooks/post-receive --

1 0