REDDnet Application Integration Working Group - Revision history

Sheldonp at 18:56, 20 August 2007

2007-08-20T18:56:50Z

New page

== Work Plan ==

General Plan of work, etc. to be outlined here?

== Applications ==

=== [[AmericaView]] ===

=== [[CMS]] ===

=== [[Library of Congress]] ===

=== [[Local Vanderbilt]] ===

Sheldonp at 15:37, 16 August 2007

2007-08-16T15:37:06Z

New page

== Work Plan ==

General Plan of work, etc. to be outlined here?

== Applications ==

=== [[AmericaView]] ===

=== [[CMS]] ===

=== [[Library of Congress]] ===

=== [[Local Vanderbilt]] ===

Sheldonp: /* Applications */

2007-02-28T15:46:48Z

Applications

← Older revision		Revision as of 10:46, 28 February 2007
Line 7:		Line 7:
	=== [[AmericaView]] ===		=== [[AmericaView]] ===

	=== ~~ATLAS~~ ===		=== [[CMS]] ===

	* TBD (McKee)		=== [[Library of Congress]] ===

	=== ~~CMS ===~~		=== [[Local Vanderbilt]] ===

	* xrootd integration into L-Store, to allow CMS analysis to use REDDnet storage (Engh)

	* The SRM L-Store interface should allow CMS to use REDDnet storage for CMS production running (MC, reconstruction, analysis). This possibility needs to be further explored and developed with Ian Fisk, Brian Bockelman (Cavanaugh, Engh)

	~~=== Library of Congress ===~~

	* TBD (Moore)

	~~===~~ Local Vanderbilt ===

	* Need to set up a local Vanderbilt demo/outreach project ... with Piston's group? Pheobe?

Sheldonp: /* Applications */

2007-02-28T15:45:16Z

Applications

@@ Line 5: / Line 5: @@
 == Applications ==
-[[AmericaView]]
+=== [[AmericaView]] ===
 === ATLAS ===

Sheldonp: /* Applications */

2007-02-28T15:44:33Z

Applications

← Older revision		Revision as of 10:44, 28 February 2007
Line 5:		Line 5:
	== Applications ==		== Applications ==

	[AmericaView]		[[AmericaView]]

	=== AmericaView ===		=== AmericaView ===

Sheldonp: /* Applications */

2007-02-28T15:44:13Z

Applications

← Older revision		Revision as of 10:44, 28 February 2007
Line 4:		Line 4:

	== Applications ==		== Applications ==

			[AmericaView]

	=== AmericaView ===		=== AmericaView ===

167.165.36.1: /* AmericaView */

2006-12-06T17:33:25Z

AmericaView

← Older revision		Revision as of 12:33, 6 December 2006
Line 37:		Line 37:
	The Upload Tool walks an archive data structure, identifies “deliverable units”, uploads these to REDDnet, receives an exnode, and stores the exnode for later use. This process should be merged with existing code used to generate GloVis scene lists and download GloVis browse and metadata. Requirements for the Upload Tool include:		The Upload Tool walks an archive data structure, identifies “deliverable units”, uploads these to REDDnet, receives an exnode, and stores the exnode for later use. This process should be merged with existing code used to generate GloVis scene lists and download GloVis browse and metadata. Requirements for the Upload Tool include:
	#Ability to autonomously walk a directory structure and identify which files constitute a “deliverable unit”. This should work across a variety of directory structures and file collections, although some restrictions will probably have to be imposed.		#Ability to autonomously walk a directory structure and identify which files constitute a “deliverable unit”. This should work across a variety of directory structures and file collections, although some restrictions will probably have to be imposed.
	#Integrate exnodes with existing GloVis data structure.		#Integrate exnodes with existing GloVis data structure. (This step is rendered mute becuase L-Store archives exnodes by filename.)
	#Incorporate existing browse and metadata download functionality.		#Incorporate existing browse and metadata download functionality.

	''~~Archive Responder~~''		''Download Manager''
	The Archive Responder will accept a standard GloVis scenelist, ~~retrieve the~~ appropriate ~~exnode(s) and~~ pass it to the client~~, download~~ an exnode retrieval ~~client~~ and launch the ~~client~~. Requirements include:		The Archive Responder will accept a standard GloVis scenelist, extract appropriate L-Store descriptors, pass the descrptors to the client along with an exnode retrieval tool and launch the tool. Requirements include:
	#ability to be “branded” by the hosting entity.		#ability to be “branded” by the hosting entity.
	#interaction with both a previously downloaded retrieval client and with a download on demand retrieval client.		#interaction with both a previously downloaded retrieval client and with a download on demand retrieval client.
	#very simple interface – easy to use.		#very simple interface – easy to use.
	#client TCP/IP stack tuning to improve performance (~~is this currently done in~~ the LoDN ~~client piece?~~)		#possibly incorporate client TCP/IP stack tuning to improve performance (the Current LoDN download tool does not do this.)

	'''AmericaView participation'''		'''AmericaView participation'''

192.70.161.100: /* AmericaView */

2006-11-15T15:01:30Z

AmericaView

← Older revision		Revision as of 10:01, 15 November 2006
Line 7:		Line 7:
	=== AmericaView ===		=== AmericaView ===

	'''AmericaView REDDnet ~~Implantation~~ Plan'''		'''AmericaView REDDnet Implementation Plan'''

	'''Background'''		'''Background'''

129.59.122.59 at 19:10, 9 November 2006

2006-11-09T19:10:30Z

← Older revision		Revision as of 14:10, 9 November 2006
Line 5:		Line 5:
	== Applications ==		== Applications ==

	=== ~~ATLAS~~ ===		=== AmericaView ===

	'''AmericaView REDDnet Implantation Plan'''		'''AmericaView REDDnet Implantation Plan'''

129.59.122.59 at 19:10, 9 November 2006

2006-11-09T19:10:15Z

← Older revision		Revision as of 14:10, 9 November 2006
Line 4:		Line 4:

	== Applications ==		== Applications ==

			=== ATLAS ===

	'''AmericaView REDDnet Implantation Plan'''		'''AmericaView REDDnet Implantation Plan'''