Difference: VOSpace30Spec (1 vs. 5)

Revision 52018-05-24 - BrianMajor

 
META TOPICPARENT name="VOSpaceHome"
VOSpace home page
Changed:
<
<

Discussion page for the VOSpace 3.0

>
>

Discussion page for the VOSpace 2.2 / 3.0

  This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Storage systems for implementing VOSpace

  • File System
  • File System & Relational Database
  • WebDAV (IPAC)
  • OwnCloud ? (INAF)
  • OpenStack Swift (JHU/NASA)
  • Leverage existing Archival distributed storage (CADC)

Notes / Ideas

  • In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level, or should this be considered orthogonal?
  • Custom views: views that clients create and use to do work/data reduction at the physical storage location.
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace? A number of articles on Astronomy and Computing
<--  
-->

Revision 42014-10-11 - BrianMajor

 
META TOPICPARENT name="VOSpaceHome"
VOSpace home page

Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Storage systems for implementing VOSpace

  • File System
  • File System & Relational Database
  • WebDAV (IPAC)
  • OwnCloud ? (INAF)
Changed:
<
<
>
>
 
  • Leverage existing Archival distributed storage (CADC)

Notes / Ideas

  • In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level, or should this be considered orthogonal?
  • Custom views: views that clients create and use to do work/data reduction at the physical storage location.
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace? A number of articles on Astronomy and Computing
<--  
-->

Revision 32014-10-10 - BrianMajor

 
META TOPICPARENT name="VOSpaceHome"
VOSpace home page

Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Added:
>
>

Storage systems for implementing VOSpace

  • File System
  • File System & Relational Database
  • WebDAV (IPAC)
  • OwnCloud ? (INAF)
  • OpenStack Swift (Caltech/NASA)
  • Leverage existing Archival distributed storage (CADC)
 

Notes / Ideas

  • In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
Changed:
<
<
  • Should VOSpace should have it's own registry extension, VoSpaceRegEx?
>
>
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level, or should this be considered orthogonal?
Deleted:
<
<
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level?
 
  • Custom views: views that clients create and use to do work/data reduction at the physical storage location.
Changed:
<
<
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace?
>
>
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace? A number of articles on Astronomy and Computing
Deleted:
<
<
  • From Marcos: OwnCloud as the storage layer under VOSpace?
 
<--  
-->

Revision 22014-10-10 - BrianMajor

 
META TOPICPARENT name="VOSpaceHome"
VOSpace home page

Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Notes / Ideas

  • In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
  • Should VOSpace should have it's own registry extension, VoSpaceRegEx?
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level?
  • Custom views: views that clients create and use to do work/data reduction at the physical storage location.
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace?
Added:
>
>
  • From Marcos: OwnCloud as the storage layer under VOSpace?
 
<--  
-->

Revision 12014-10-05 - BrianMajor

 
META TOPICPARENT name="VOSpaceHome"
VOSpace home page

Discussion page for the VOSpace 3.0

This is a discussion page for future enhancements and changes to VOSpace 2.1

Please edit this page directly to add comments or specification changes and additions.

Notes / Ideas

  • In the transfer object, the 'direction' can conflict with the protocol URI. For example, the direction can be 'pullFromVoSpace' and the protocol can be 'HTTP-PUT'. This could be cleaned up to remove error cases.
  • Should VOSpace should have it's own registry extension, VoSpaceRegEx?
  • Section 4, Access Control: Version 3.0 should state access control policies at the Node level?
  • Custom views: views that clients create and use to do work/data reduction at the physical storage location.
  • JPEG2000 Interactive Protocol (JPIP) and VOSpace?
<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback