Dec. 19, 2006: Difference between revisions

From ReddNet
Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Coordinates ==
*Time: 10:30EST/9:30CST
*Conference #:510-665-5437  Meeting ID:7333
== Attending ==
== Attending ==
* Hagewood (Nevoa)
* Hunter Hagewood (Nevoa)
* Beck, Moore (UTK)
* Micah Beck, Terry Moore (UTK)
* Engh, Sheldon, Tackett (VU)
* Dan Engh, Paul Sheldon, Alan Tackett, Santiago de Ledesma (VU)
* Blackwell, ... may attend late
* Mike Coffee, Diana Gunter, Shane Jenson
* ...


== Current Agenda ==
== Current Agenda ==
Line 11: Line 14:
* Review of [http://www.reddnet.org/mwiki/index.php/Action_Plans_from_December_REDDnet_Meeting action plans for application groups from Chicago meeting]: America View, Cryo EM, CMS.
* Review of [http://www.reddnet.org/mwiki/index.php/Action_Plans_from_December_REDDnet_Meeting action plans for application groups from Chicago meeting]: America View, Cryo EM, CMS.
* Update on recent discussions with the UltraLight group (Paul, Alan)
* Update on recent discussions with the UltraLight group (Paul, Alan)
* Status of Dan's work on integrating ROOT and LN technology (Dan/Paul)
* What's happening with Modern VideoFilm (Alan)


=== Deployment and Operations ===
=== Deployment and Operations ===
Line 16: Line 21:
**Is there any update on this schedule?  A timeline of what will be deployed where and when?
**Is there any update on this schedule?  A timeline of what will be deployed where and when?
**There are demos planned for the beginning of March (AV meeting in Washington at least, maybe OSG meeting in SD as well).  
**There are demos planned for the beginning of March (AV meeting in Washington at least, maybe OSG meeting in SD as well).  
*Discussion of alternative strategy for investment in REDDnet deployment (Terry)
*Discussion of alternative strategy for investment in REDDnet deployment - The general idea is to buy more, but perhaps less well provisioned nodes, and try to deploy them to more places where application groups will fully populate the rack with storage. (Terry)


=== Technology: Hardware, Software ===
=== Technology: Hardware, Software ===
*Review of [http://www.reddnet.org/mwiki/index.php/November_21%2C_2006_L-Store_Planning_Meeting_%28VU%29#L-Store_Releases_and_Features current L-Store release schedule](Alan)
*Review of the notes from the [http://www.reddnet.org/mwiki/index.php/Informal_REDDnet_software_stack_meeting%2C_3Dec06#Notes_from_the_meeting Chicago Software meeting]


=== Organization and Funding Opportunities ===
=== Organization and Funding Opportunities ===
*[http://www.nsf.gov/pubs/2007/nsf07503/nsf07503.htm NSF SDCI] (Due. Jan. 22)
*[http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=500066 NSF STCI](Feb. 8th)-- What kind of opportunity is this (Micah)?
*[http://www.nsf.gov/pubs/2006/nsf06589/nsf06589.htm NSF PIRE] (Feb. 28th)-- Paul: Any word?


=== Events, Education, Outreach ===
=== Events, Education, Outreach ===
Line 26: Line 36:
**Are people down for both a track meeting and side meeting at the Spring Washington meeting
**Are people down for both a track meeting and side meeting at the Spring Washington meeting
***Terry will write the submissions
***Terry will write the submissions
***Can we get our funding people to come.
***Can we get our funding people to come?
**Do we want to do a demo at the TRIDENTCOM show? Since it's in Orlando, is there any chance our Ultralight colleagues would like to get together and demo with us? If so what would we show.
**Do we want to do a demo at the TRIDENTCOM show? Since it's in Orlando, is there any chance our Ultralight colleagues would like to get together and demo with us? If so what would we show.
* List of upcoming events this Spring that we know about or that we're planning for. [http://www.reddnet.org/mwiki/index.php/REDDnet_at_Work_Page#Future_.28including_those_under_consideration.29  More details] about what's planned are on the "at work" page
* List of upcoming events this Spring that we know about or that we're planning for. [http://www.reddnet.org/mwiki/index.php/REDDnet_at_Work_Page#Future_.28including_those_under_consideration.29  More details] about what's planned are on the "at work" page
Line 37: Line 47:


== Action Items ==
== Action Items ==
*Terry will get the LN wiki up and going (http://www.logisticalnetworking.org)
*Alan will share the rough spec he's going to develop for libxio before he implements
*Micah will recover and put on line the old IBP spec or, if that can't be located, do what he can to replace it.
==Some Notes on the call==
*The SFA group discussed the fact that they've set up a server and they talked with Alan and Santi on how to take the next steps. Santi and Diana are going to talk by phone to get this going.
*Discussion of software specifications for LN/REDDnet sofware
**We talked about the need to have specs for various interfaces so that different implementations can retain interoperability and people can be confident that what build on won't change out from under them.
**It's problematic because we have a schedule that we need to meet and achieving agreement on specifications can be time consuming.
**The most immediate challenge is libxio, which is lacking in various important respects, such as the ability to deal with the parity mappings that LStore does and the lack of caching.
**Parallel disucssion of need for (and current lack of) documentation and adequate comments of much of the LN code.
**Conclusions:
***Alan and the ACCRE group want to get libxio replaced as quickly as possible. So the compromise process is a) put the rough spec they will create to guide their reimplementation on-line, b) implement a new version of libxio, c) document the code d) go back to the rough spec and modify it in the light of the new codes/comments. The idea is that the spec that results at stage d) will be our initial cut at the community spec. and we'll work toward and agreed upon a community spec.
***A rough IBP spec which was once done has since been lost in the shuffle. Micah is going to try to recover that spec and put it on-line. If it can't be recovered, he'll see what he can do, working with his students, to develop something similar.
***Terry's going to get the LN wiki up and running during the holidays as the place that can hold all this specification work.
*We agreed that we wouldn't try to go for a demo at TRIDENT 2007. We're overloaded already.
*Dan Engh described what he's been doing with ROOTd and LN tools
*Alan briefly described what they're doing with Alan Hart. The goal is to have something he can evaluate by the end of January.

Latest revision as of 14:25, 19 December 2006

Coordinates

  • Time: 10:30EST/9:30CST
  • Conference #:510-665-5437 Meeting ID:7333

Attending

  • Hunter Hagewood (Nevoa)
  • Micah Beck, Terry Moore (UTK)
  • Dan Engh, Paul Sheldon, Alan Tackett, Santiago de Ledesma (VU)
  • Mike Coffee, Diana Gunter, Shane Jenson

Current Agenda

Application Communities

Deployment and Operations

  • Review of the current deployment schedule
    • Is there any update on this schedule? A timeline of what will be deployed where and when?
    • There are demos planned for the beginning of March (AV meeting in Washington at least, maybe OSG meeting in SD as well).
  • Discussion of alternative strategy for investment in REDDnet deployment - The general idea is to buy more, but perhaps less well provisioned nodes, and try to deploy them to more places where application groups will fully populate the rack with storage. (Terry)

Technology: Hardware, Software

Organization and Funding Opportunities

  • NSF SDCI (Due. Jan. 22)
  • NSF STCI(Feb. 8th)-- What kind of opportunity is this (Micah)?
  • NSF PIRE (Feb. 28th)-- Paul: Any word?

Events, Education, Outreach

Action Items

  • Terry will get the LN wiki up and going (http://www.logisticalnetworking.org)
  • Alan will share the rough spec he's going to develop for libxio before he implements
  • Micah will recover and put on line the old IBP spec or, if that can't be located, do what he can to replace it.

Some Notes on the call

  • The SFA group discussed the fact that they've set up a server and they talked with Alan and Santi on how to take the next steps. Santi and Diana are going to talk by phone to get this going.
  • Discussion of software specifications for LN/REDDnet sofware
    • We talked about the need to have specs for various interfaces so that different implementations can retain interoperability and people can be confident that what build on won't change out from under them.
    • It's problematic because we have a schedule that we need to meet and achieving agreement on specifications can be time consuming.
    • The most immediate challenge is libxio, which is lacking in various important respects, such as the ability to deal with the parity mappings that LStore does and the lack of caching.
    • Parallel disucssion of need for (and current lack of) documentation and adequate comments of much of the LN code.
    • Conclusions:
      • Alan and the ACCRE group want to get libxio replaced as quickly as possible. So the compromise process is a) put the rough spec they will create to guide their reimplementation on-line, b) implement a new version of libxio, c) document the code d) go back to the rough spec and modify it in the light of the new codes/comments. The idea is that the spec that results at stage d) will be our initial cut at the community spec. and we'll work toward and agreed upon a community spec.
      • A rough IBP spec which was once done has since been lost in the shuffle. Micah is going to try to recover that spec and put it on-line. If it can't be recovered, he'll see what he can do, working with his students, to develop something similar.
      • Terry's going to get the LN wiki up and running during the holidays as the place that can hold all this specification work.
  • We agreed that we wouldn't try to go for a demo at TRIDENT 2007. We're overloaded already.
  • Dan Engh described what he's been doing with ROOTd and LN tools
  • Alan briefly described what they're doing with Alan Hart. The goal is to have something he can evaluate by the end of January.