ReddNet - User contributions [en]

Documentation

2008-08-07T19:37:14Z

Rgb:

Please note that this is currently in a state of flux as I reorganize the website - Mat Binkley.

{| width="90%" align="center"
|-
|align="center" width="33%"| '''Users'''
|align="center" width="34%"| '''System Administrators'''
|align="center" width="33%"| '''Developers'''
|- valign="top"
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_display.png|80px]]
|
* [[About_REDDnet|What is REDDnet?]]
* [[REDDnet_Requirements|What software/resources do I need?]]
* [[Using_L-Store|How to use L-Store client]]
* [[Using_LoRS|How to use LoRS client]]
* [[User_Documentation|'''More...''']]
|}
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_terminal.png|80px]]
|
* [[Installing_and_configuring_IBP|Installing IBP]]
* [[Installing_and_configuring_L-Store|Installing L-Store]]
* [[Installing_and_configuring_LoRS|Installing LoRS]]
* [[SysAdmin_Documentation|'''More...''']]
|}
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_tutorials.png|80px]]
|
* [[API_IBP|IBP API]]
* [[API_L-Store|L-Store API]]
* [[API_LoRS|LoRS API]]
* [[Developer_Documentation|'''More...''']]
|}
|}

=== Online Documentation ===

* Documentation for all aspects of REDDnet needs to be completed and added or linked to this wiki. Below is the list of what needs to be developed/Core institution and person assigned to do the task
** [[Getting_started_with_L-Store | How to get started with L-Store]] - Santiago
** [[Getting_started_with_LoDN | How to get started with LoDN]] - Chris/Terry
** [[L-Store | L-Store]] - Santiago
** [https://promise.cs.utk.edu/lodn/doc/Publish.htm LoDN] - Chris/Terry
** [[IBP | IBP]] - Alan
** [[IBP Asynchronous Client API]]
** [[Standard_IO_layer | Standard IO]] - Chris
** [[Data_and_Directory_Services | Data and Directory Services]] - VU-person

=== Past Documentation ===

* [http://events.internet2.edu/2007/spring-mm/sessionDetails.cfm?session=3160&event=267 Network Storage Virtualization for Data Intensive Collaboration] Track Session at the [http://events.internet2.edu/2007/spring-mm/ Spring 2007 Internet2 Meeting] in Arlington, VA
** [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/DisplayMeeting?conferenceid=8 Agenda and Talks]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=86 Three slide summary of L-Store, IBP, and REDDnet]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=73 REDDnet NSF MRI Proposal]

* [[L-Store Usage Instructions]] - setup, uploading, downloading, and several other Lstore options explained (includes [[LoRS Instructions]])

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=84 L-Store Presentation at the University of Sao Paulo, July, 2006]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=82 L-Store Presentation at LBNL, Sept. 9, 2006]

*[[Protocol Standardization Efforts]] and development ideas

*'''The Vanderbilt/ACCRE Booth at [[SC06]] will highlight REDDnet technology''

REDDnet Management Documentation

2008-08-07T19:34:37Z

Rgb:

== Deployment Hardware Listing by Site ==

REDDnet Management Documentation

2008-08-07T19:33:31Z

Rgb: New page: == REDDnet Hardware Management Details ==

== REDDnet Hardware Management Details ==

Documentation

2008-08-07T19:32:03Z

Rgb:

Please note that this is currently in a state of flux as I reorganize the website - Mat Binkley.

{| width="90%" align="center"
|-
|align="center" width="33%"| '''Users'''
|align="center" width="34%"| '''System Administrators'''
|align="center" width="33%"| '''Developers'''
|- valign="top"
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_display.png|80px]]
|
* [[About_REDDnet|What is REDDnet?]]
* [[REDDnet_Requirements|What software/resources do I need?]]
* [[Using_L-Store|How to use L-Store client]]
* [[Using_LoRS|How to use LoRS client]]
* [[User_Documentation|'''More...''']]
|}
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_terminal.png|80px]]
|
* [[Installing_and_configuring_IBP|Installing IBP]]
* [[Installing_and_configuring_L-Store|Installing L-Store]]
* [[Installing_and_configuring_LoRS|Installing LoRS]]
* [[SysAdmin_Documentation|'''More...''']]
|}
|
{|
|- valign="top"
|[[Image:Crystal_Clear_app_tutorials.png|80px]]
|
* [[API_IBP|IBP API]]
* [[API_L-Store|L-Store API]]
* [[API_LoRS|LoRS API]]
* [[Developer_Documentation|'''More...''']]
|}
|}

=== Online Documentation ===

* Documentation for all aspects of REDDnet needs to be completed and added or linked to this wiki. Below is the list of what needs to be developed/Core institution and person assigned to do the task
** [[Getting_started_with_L-Store | How to get started with L-Store]] - Santiago
** [[Getting_started_with_LoDN | How to get started with LoDN]] - Chris/Terry
** [[L-Store | L-Store]] - Santiago
** [https://promise.cs.utk.edu/lodn/doc/Publish.htm LoDN] - Chris/Terry
** [[IBP | IBP]] - Alan
** [[IBP Asynchronous Client API]]
** [[Standard_IO_layer | Standard IO]] - Chris
** [[Data_and_Directory_Services | Data and Directory Services]] - VU-person
** [[REDDnet_Management_Documentation | REDDnet Management Documentation]] - Bobby

=== Past Documentation ===

* [http://events.internet2.edu/2007/spring-mm/sessionDetails.cfm?session=3160&event=267 Network Storage Virtualization for Data Intensive Collaboration] Track Session at the [http://events.internet2.edu/2007/spring-mm/ Spring 2007 Internet2 Meeting] in Arlington, VA
** [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/DisplayMeeting?conferenceid=8 Agenda and Talks]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=86 Three slide summary of L-Store, IBP, and REDDnet]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=73 REDDnet NSF MRI Proposal]

* [[L-Store Usage Instructions]] - setup, uploading, downloading, and several other Lstore options explained (includes [[LoRS Instructions]])

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=84 L-Store Presentation at the University of Sao Paulo, July, 2006]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=82 L-Store Presentation at LBNL, Sept. 9, 2006]

*[[Protocol Standardization Efforts]] and development ideas

*'''The Vanderbilt/ACCRE Booth at [[SC06]] will highlight REDDnet technology''

REDDnet@I2: REDDnet Activities meeting, 21April08

2008-04-16T18:07:10Z

Rgb: /* Morning: Software Development and REDDnet Operations (8:30a - 12:00p) */

==Coordinates==
'''April 28, 8:00am-5:00pm, [http://www.marriott.com/hotels/travel/wasgw-crystal-gateway-marriott/ Crystal Gateway Marriott], Washington, DC.''' This meeting is held in cooperation with the [http://events.internet2.edu/2008/spring-mm/ Spring 2008 Internet2 Member Meeting], which will be held April 21-23, 2008. The meeting will be held in the [http://www.reddnet.org/mwiki/index.php/Image:Marriott2ndFloorDiagram.png Alexandria room].
== Overview and main goals of the the meeting ==
Over the course of the next 6 to 9 months, REDDnet will become a operational infrastructure, working in pre-production (i.e. "beta) mode, but none the less supporting application communities of early adopters and experimental users. The main purpose of this meeting is to map out, discuss, and agree on the steps necessary for success in this effort. Longer term plans for essential software development, service deployment, and community support will also be explored.

The morning session, which will be restricted to the REDDnet PIs and the core LN software development community and REDDnet operations group, will focus on issues surrounding the REDDnet roll out and mid-term software and service development and deployment. In the afternoon session, we will be joined by participants and interested parties from REDDnet's application communities; the goal of the session is to listen to and understand their requirements, concerns, and questions, so that REDDnet objectives and milestones line up as well as possible with their goals. The success of REDDnet largely depends on the success of these application communities in using it.

'''[[REDDnet@I2-Apr08 meeting results]]: Agreed upon objectives, milestones, task assignments, and other notes from the meeting.'''

=Agenda=
'''Continental Breakfast (7:30am-8:30am)'''
== Morning: Software Development and REDDnet Operations (8:30a - 12:00p)==
'''8:30-8:45''': Greetings (Paul and Terry)

'''8:45-9:30''': State of REDDnet infrastructure - April08
* Deployment: Current state, plans for next 6 months, issues raised. (Bobby)
* Summary of ongoing tests: ACCRE depot tests, LoDN/warming with ACCRE depot, VTNA, recursive augment for FACIT, CMS experiments (Alan,Santi, Chris, Harold)
* Request tracker for problem resolution (Matt)
*Issues?
** Protocols for infrastructure testing vs. application use
** Monitoring and management
** Instrumentation/monitoring? For example, PerfSonar?

'''9:30-10:00''' REDDnet Communications

'''10:00-10:15''' Morning Break

'''10:15-11:30''' Software and Service Development
Current tool set
* L-Store (Santi)
* LoCI tools and services(Chris and Harold)
* 3rd party
**Phoebus?
* Future

==== Testing plans and Schedule ====
====Software Development====
*exNode
*exMSP

===Afternoon: Planning for Application Communities (1:30p - 5:00p)===

==Projected Attendees==
===Full Day===
*Vanderbilt: Paul Sheldon, Dan Engh, Alan Tackett, Bobby Brown, Matt Binkley,...
*University of Tennessee: Terry Moore, Chris Sellers, Harold Gonzales, Micah Beck (remotely)
*Stephen F. Austin: PR Blackwell
*University of Deleware: Martin Swany
*[http://www.muni.cz/ Masaryk University (Czech Republic)]: Lukáš Hejtmánek

===Afternoon: Application Communities===
#Library of Congress
#SURA
#UCSB
#Joe Isabelle

Operations and Deployment

2008-01-31T14:45:18Z

Rgb:

=== Deployment ===
* '''Bring current deployment up-to-date (estimate complete by mid-Feb)'''
** Build new image for 2GB internal USB memory
*** may be done by All-Hands
** Design and implement a depot recovery process
*** This process will be vetted on current deployed hardware
*** Initial process may be done by All Hands or soon thereafter
*** Begin with SFASU for initial vetting
** Send recovery keys out to sites and update the depots
*** early February
*** need to recruit one person at each site to assist
** Set Nagios back up
*** need a more stable system before this makes sense
*** turned off during this transition period to avoid flood of diagnostics
*** needs a day or two of time, could be done now depending on priority

* '''Prepare additional existing hardware for deployment (19 nodes)'''
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites for remaining 13.
*** Ideas?

* Develop MOU for current deployment (timescale uncertain?)
** Longer term project

* Define a standard set of software tools for depots
** The following also exist
*** Iperf
*** Nagios
*** mtr
** other tools to be added?
*** investigating new tools now

* Gain experience with existing deployment
** See "Validation Framework" below.
** make frequent reports in weekly REDDnet meetings
** review deployment experience end of March

* '''Proposed multi-tiered system for sites for discussion'''
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new management tools over the next two months
** rsync or similar (short term)
** Perceus (long term)

=== Monitoring ===
* '''Use StorCore, Nagios, iperf, and visualization tools from SC07'''
** Have a statistic page that gathers information from tests and presents them cleanly
*** Long term project - 6 months to a year?

* '''What is required to provide adequate support for REDDnet'''
** Want feedback on this.
** Setting expectations?
** Actively talk to users over the next couple of months - 6 months - ongoing
** Develop an initial plan by mid-Feb, then review every 3 months and tweak

* Create a REDDnet status site, using google maps
** short term just get green dots on a map (what is the priority for this?)
** longer term - expected to evolve, integrate with the vis site

* '''Create an RT site to resolve users' issues'''
** needs to happen quickly. mid-Feb.

=== Validation Framework ===
* '''Stress and WAN testing on Production REDDnet'''
** Automated testing with Clyde
*** excercise system prior to heavy real world use
*** unfortunately longer term - first of April?
*** this testing will move to test deployment eventually
** Real world use (happening now, although not heavy)

* QA testing on Test REDDnet required before moving into production REDDnet
** A stringent set of tests to test both the hardware, OS, IBP, and LStore as throughly as possible (primarily Clyde)
** Allow users to test using this system

Operations and Deployment

2008-01-28T14:29:54Z

Rgb:

=== Deployment ===
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Design and implement a depot recovery process
** Send recovery keys out to sites and update the depots
** Set Nagios back up
** Develop MOU for current deployment

* Prepare existing hardware for deployment
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites

* Define a standard set of software tools for depots
** Iperf
** Nagios
** mtr
** other tools...

* Gain experience with existing deployment

* Discuss a multi-tiered system for sites
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new monitoring and management tools
** rsync or similar (short term)
** Perceus (long term)

=== Monitoring ===
* Use StorCore, Nagios, iperf, and visualization tools from SC07
** Have a statistic page that gathers information from tests and presents them cleanly
** Define support for REDDnet

* Create a REDDnet status site, using google maps

* Create an RT site to resolve users' issues

=== Validation Framework ===
* Stress and WAN testing on Production REDDnet
** Automated testing with Clyde
** Real world use

* QA testing on Test REDDnet required before moving into production REDDnet
** A stringent set of tests to test both the hardware, OS, IBP, and LStore as throughly as possible (primarily Clyde)
** Allow users to test using this system

Operations and Deployment

2008-01-28T14:28:21Z

Rgb: /* Validation Framework */

= Deployment =
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Design and implement a depot recovery process
** Send recovery keys out to sites and update the depots
** Set Nagios back up
** Develop MOU for current deployment

* Prepare existing hardware for deployment
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites

* Define a standard set of software tools for depots
** Iperf
** Nagios
** mtr
** other tools...

* Gain experience with existing deployment

* Discuss a multi-tiered system for sites
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new monitoring and management tools
** rsync or similar (short term)
** Perceus (long term)

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
** Have a statistic page that gathers information from tests and presents them cleanly
** Define support for REDDnet

* Create a REDDnet status site, using google maps

* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
** Automated testing with Clyde
** Real world use

* QA testing on Test REDDnet required before moving into production REDDnet
** A stringent set of tests to test both the hardware, OS, IBP, and LStore as throughly as possible (primarily Clyde)
** Allow users to test using this system

Operations and Deployment

2008-01-28T14:27:25Z

Rgb: /* Validation Framework */

= Deployment =
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Design and implement a depot recovery process
** Send recovery keys out to sites and update the depots
** Set Nagios back up
** Develop MOU for current deployment

* Prepare existing hardware for deployment
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites

* Define a standard set of software tools for depots
** Iperf
** Nagios
** mtr
** other tools...

* Gain experience with existing deployment

* Discuss a multi-tiered system for sites
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new monitoring and management tools
** rsync or similar (short term)
** Perceus (long term)

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
** Have a statistic page that gathers information from tests and presents them cleanly
** Define support for REDDnet

* Create a REDDnet status site, using google maps

* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
** Automated testing with Clyde
** Real world use

* QA testing on Test REDDnet required before moving into production REDDnet
** A stringent set of tests to test deployment as throughly as possible (primarily Clyde)
** Allow users to test using this system

Operations and Deployment

2008-01-28T14:24:12Z

Rgb: /* Monitoring */

= Deployment =
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Design and implement a depot recovery process
** Send recovery keys out to sites and update the depots
** Set Nagios back up
** Develop MOU for current deployment

* Prepare existing hardware for deployment
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites

* Define a standard set of software tools for depots
** Iperf
** Nagios
** mtr
** other tools...

* Gain experience with existing deployment

* Discuss a multi-tiered system for sites
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new monitoring and management tools
** rsync or similar (short term)
** Perceus (long term)

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
** Have a statistic page that gathers information from tests and presents them cleanly
** Define support for REDDnet

* Create a REDDnet status site, using google maps

* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
* QA testing on Test REDDnet required before moving into production REDDnet

Operations and Deployment

2008-01-28T14:16:54Z

Rgb: /* Deployment */

= Deployment =
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Design and implement a depot recovery process
** Send recovery keys out to sites and update the depots
** Set Nagios back up
** Develop MOU for current deployment

* Prepare existing hardware for deployment
** Update image on internal USB (will use for testing of the above recovery process)
** Send 6 depots to SFASU with additional PDU
** Find new collaborators/sites

* Define a standard set of software tools for depots
** Iperf
** Nagios
** mtr
** other tools...

* Gain experience with existing deployment

* Discuss a multi-tiered system for sites
** Tier 1: Sites that run their own LServer and Chord ring
** Tier 2: Sites that manage their own REDDnet depots
** Tier 3: Sites that use their own storage resources as depots
** Develop MOU for each tier

* Investigate new monitoring and management tools
** rsync or similar (short term)
** Perceus (long term)

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
* Create a REDDnet status site, using google maps
* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
* QA testing on Test REDDnet required before moving into production REDDnet

All Hands Meeting, Feb 1, 2008

2008-01-28T13:46:10Z

Rgb:

==Agenda for All-Hands==

"What needs to happen to make REDDnet happen?"

Meeting Goals:
* lay out a roadmap and vision for REDDnet
* specify tasks and jobs and prioritize
* identify and make necessary policy decisions

roadmap should be driven by application groups: CMS, TVNA, AmericaView, Facit,...

we need a scribe for each session to write down action items from
that session and major decisions.

====List of questions we know should be addressed====

* titles of working group probably need to be changed?
* opt-in policy for new groups
* contributed nodes policy (do we want to require contributors to be collaborators?)
* what services does REDDnet provide?

===Morning Session 9-12:30===

====09:00-09:15 --- Management Overview====

====09:15-10:00 --- IBP====
:[[Presentation information]]

====10:00-10:45 --- Software Integration and Interoperability====
* standardizing on an exnode - what is current state of exnode interoperability?
* how should checksum issue be resolved?

====10:45-11:00 --- 15 minute coffee break====

====11:00-11:45 --- LoCI Tools====

====11:45-12:30 --- L-Store Tools====

===Afternoon Session 1:30-5:00===

====01:30-02:15 --- Infrastructure Maintenance and Operations====
:[[Operations and Deployment]]

====02:15-03:00 --- Application Liason Activities====

* how do new groups join?

====03:00-03:15 --- 15 minute coffee break====

====03:15-04:00 --- Applications====

====04:00-05:00 --- The Big Picture====

Operations and Deployment

2008-01-25T14:03:55Z

Rgb: /* Deployment */

= Deployment =
* Bring current deployment up-to-date
* Prepare existing hardware for deployment
* Develop MOU for current deployment
* Design and implement a depot recovery process
* Define a standard set of software tools for depots
* Gain experience with existing deployment
* Discuss a multi-tiered system for sites
* Find new collaborators/sites
* Investigate Perceus as an update tool

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
* Create a REDDnet status site, using google maps
* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
* QA testing on Test REDDnet required before moving into production REDDnet

Operations and Deployment

2008-01-25T14:03:15Z

Rgb: /* Validation Framework */

= Deployment =
* Bring current deployment up-to-date
* Prepare existing hardware for deployment
* Develop MOU for current deployment
* Design and implement a depot recovery process
* Define a standard set of software tools for depots
* Gain experience with existing deployment
* Discuss a multi-tiered system for sites
* Find new sites
* Investigate Perceus as an update tool

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
* Create a REDDnet status site, using google maps
* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
* QA testing on Test REDDnet required before moving into production REDDnet

Operations and Deployment

2008-01-25T14:02:15Z

Rgb: New page: = Deployment = * Bring current deployment up-to-date * Prepare existing hardware for deployment * Develop MOU for current deployment * Design and implement a depot recovery process * Defi...

= Deployment =
* Bring current deployment up-to-date
* Prepare existing hardware for deployment
* Develop MOU for current deployment
* Design and implement a depot recovery process
* Define a standard set of software tools for depots
* Gain experience with existing deployment
* Discuss a multi-tiered system for sites
* Find new sites
* Investigate Perceus as an update tool

= Monitoring =
* Use StorCore, Nagios, iperf, and visualization tools from SC07
* Create a REDDnet status site, using google maps
* Create an RT site to resolve users' issues

= Validation Framework =
* Stress and WAN testing on Production REDDnet
* tools QA testing on Test REDDnet required before moving into production REDDnet

REDDnet Deployment and Monitoring Working Group

2008-01-24T19:09:35Z

Rgb:

This task consists of:
* deployment and system administration of the REDDnet hardware
* interfacing with the networking partners (such as UltraLight or AMPATH)
* monitoring and characterization/testing of REDDnet

== Deployment ==

* See [[Hardware specifications]] for a discussion of the the hardware being considered for deployment

* need to develop a deployment schedule, should be relatively specific for near term work and obviously less so for far term work.
* What are tasks, schedule?
* How does SC06 fit into all of this?

== Networking Partners ==

* ???

== REDDnet Monitoring/Characterization ==

* What do we plan to do for monitoring and characterization? Need to write something down here...
* How will we use MonaLisa?
* what about Hunter's monitoring applications?
* AMPATH work...

=== All Hands Meeting January 2008 ===
* [[Operations and Deployment]]

=== SC06 Demonstration Project(s) ===
[http://www.reddnet.org/mwiki/index.php/SC06 The official SC06 Demo wiki page]

* Work with UltraLight folks
* Our own demo: both onsite and offsite
* Work with SRM folks: [http://www.reddnet.org/mwiki/index.php/SC06 SRM SC06 Demo]

=== Ongoing Testing and Monitoring ===

* [[L-Store Profile Analysis]]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=77 Storage Test Framework] (Document describing the framework)

* [[Network Characterization Tests]]

* [[L-Store Upload Structured Testing]]

* [[Brazil Data Transfer Tests]]

REDDnet Deployment and Monitoring Working Group

2008-01-24T16:21:46Z

Rgb:

This task consists of:
* deployment and system administration of the REDDnet hardware
* interfacing with the networking partners (such as UltraLight or AMPATH)
* monitoring and characterization/testing of REDDnet

== Deployment ==

* See [[Hardware specifications]] for a discussion of the the hardware being considered for deployment

* need to develop a deployment schedule, should be relatively specific for near term work and obviously less so for far term work.
* What are tasks, schedule?
* How does SC06 fit into all of this?

== Networking Partners ==

* ???

== REDDnet Monitoring/Characterization ==

* What do we plan to do for monitoring and characterization? Need to write something down here...
* How will we use MonaLisa?
* what about Hunter's monitoring applications?
* AMPATH work...

=== SC06 Demonstration Project(s) ===
[http://www.reddnet.org/mwiki/index.php/SC06 The official SC06 Demo wiki page]

* Work with UltraLight folks
* Our own demo: both onsite and offsite
* Work with SRM folks: [http://www.reddnet.org/mwiki/index.php/SC06 SRM SC06 Demo]

=== All Hands Meeting January 2008 ===
* [[Operations and Deployment]]

=== Ongoing Testing and Monitoring ===

* [[L-Store Profile Analysis]]

* [http://mimir.accre.vanderbilt.edu/cgi-bin/public/DocDB/ShowDocument?docid=77 Storage Test Framework] (Document describing the framework)

* [[Network Characterization Tests]]

* [[L-Store Upload Structured Testing]]

* [[Brazil Data Transfer Tests]]

REDDnet Hardware Release Schedule

2007-03-15T18:45:20Z

Rgb: /* Local VU development cluster - complete by March 15? */

=Depot Network Milestones and Workplan=
The following assumes that the version of the L-Store code used for SFASU demo at the USGS in early March (we will call it 0.8) is the current "release" version and that the next release version will be version 1.0 which will become available June 1.
* need info on devel plan for libxio replacement...

==Local VU development cluster - complete by March 15?==
* 10 ACCRE depots + 4 metadata servers - COMPLETED

==Local VU test/resease deployment - to be completed by April 1==
* Hardware Deployed - '''roughly 50 TBytes'''
** 2 systems in physics
** 2 systems in Pheobe (1 Gig link to be determined - ITS does)
** 2 depots piston lab in MRBIII (firewall issues not necessarily included)
** 10 ACCRE depots + 2 metadata servers
* Version 0.8 software in all cases...
** master campus server installed
** Phoebe lab server
** physics lab server
** Piston lab server
* Each installed depot will be verified to be working properly
** develop install verification test - do by hand if need be.
** individual install verification using chicken feeder

==April 1 - June 1... User testing of test deployment==
* stability testing under load - Clyde??? or use chicken feeder... (Bobby)
* Engh CMS testing
* Piston testing (McCaughey)
* Phoebe testing
** Saturating the medical network
** need 1 Gig connection to Phoebe
** use chicken feeder, extension of install verification test.
** time indeterminant, set by ITS and medical
* some coordination of use may be necessary so we don't get in each others way.
* as external depots added, include those in tests
* need to do test installs of the client by users on the major OSes.

==May 1 - July 1... external deployments==
* total of '''24 TBytes deployed externally, 75 TBytes in all'''
* by remote PDUs and KVMs - takes 1 week
* verify racks and rack mount issues are OK at remote sites.
* goal: 2 sites a month for two months.
* Potential Sites: (2 depots at each site)
** ORNL
** Michigan
** FIU
** Caltech - use our UltraLight connections
* Swap out old hardware, bring back to ACCRE to add in to local depots or just toss.
* install software prior to shipping, send someone out to bring up.
* bring up master REDDnet server
* all still using version 0.8 initially until rollout of version 1.0

==Rollout version 1.0 of L-Store - complete on July 1==
* can do in a scheduled downtime - takes half an hour.
* just need to do on server(s) which are local.
* how do clients work here? people are going to have to upgrade their clients...

==July 1 and beyond continue rolling out external sites, now with V1.0==
*sites and amounts TBD
*we need to discuss this!

==when is real release for all users? CMS for example...==
*need to decide!

REDDnet Hardware Release Schedule

2007-03-15T18:42:40Z

Rgb: /* June 1 and beyond continue rolling out external sites, now with V1.0 */

=Depot Network Milestones and Workplan=
The following assumes that the version of the L-Store code used for SFASU demo at the USGS in early March (we will call it 0.8) is the current "release" version and that the next release version will be version 1.0 which will become available June 1.
* need info on devel plan for libxio replacement...

==Local VU development cluster - complete by March 15?==
* 10(?) ACCRE depots + 4 metadata servers

==Local VU test/resease deployment - to be completed by April 1==
* Hardware Deployed - '''roughly 50 TBytes'''
** 2 systems in physics
** 2 systems in Pheobe (1 Gig link to be determined - ITS does)
** 2 depots piston lab in MRBIII (firewall issues not necessarily included)
** 10 ACCRE depots + 2 metadata servers
* Version 0.8 software in all cases...
** master campus server installed
** Phoebe lab server
** physics lab server
** Piston lab server
* Each installed depot will be verified to be working properly
** develop install verification test - do by hand if need be.
** individual install verification using chicken feeder

==April 1 - June 1... User testing of test deployment==
* stability testing under load - Clyde??? or use chicken feeder... (Bobby)
* Engh CMS testing
* Piston testing (McCaughey)
* Phoebe testing
** Saturating the medical network
** need 1 Gig connection to Phoebe
** use chicken feeder, extension of install verification test.
** time indeterminant, set by ITS and medical
* some coordination of use may be necessary so we don't get in each others way.
* as external depots added, include those in tests
* need to do test installs of the client by users on the major OSes.

==May 1 - July 1... external deployments==
* total of '''24 TBytes deployed externally, 75 TBytes in all'''
* by remote PDUs and KVMs - takes 1 week
* verify racks and rack mount issues are OK at remote sites.
* goal: 2 sites a month for two months.
* Potential Sites: (2 depots at each site)
** ORNL
** Michigan
** FIU
** Caltech - use our UltraLight connections
* Swap out old hardware, bring back to ACCRE to add in to local depots or just toss.
* install software prior to shipping, send someone out to bring up.
* bring up master REDDnet server
* all still using version 0.8 initially until rollout of version 1.0

==Rollout version 1.0 of L-Store - complete on July 1==
* can do in a scheduled downtime - takes half an hour.
* just need to do on server(s) which are local.
* how do clients work here? people are going to have to upgrade their clients...

==July 1 and beyond continue rolling out external sites, now with V1.0==
*sites and amounts TBD
*we need to discuss this!

==when is real release for all users? CMS for example...==
*need to decide!

REDDnet Hardware Release Schedule

2007-03-15T18:42:26Z

Rgb: /* Rollout version 1.0 of L-Store - complete on June 1 */

=Depot Network Milestones and Workplan=
The following assumes that the version of the L-Store code used for SFASU demo at the USGS in early March (we will call it 0.8) is the current "release" version and that the next release version will be version 1.0 which will become available June 1.
* need info on devel plan for libxio replacement...

==Local VU development cluster - complete by March 15?==
* 10(?) ACCRE depots + 4 metadata servers

==Local VU test/resease deployment - to be completed by April 1==
* Hardware Deployed - '''roughly 50 TBytes'''
** 2 systems in physics
** 2 systems in Pheobe (1 Gig link to be determined - ITS does)
** 2 depots piston lab in MRBIII (firewall issues not necessarily included)
** 10 ACCRE depots + 2 metadata servers
* Version 0.8 software in all cases...
** master campus server installed
** Phoebe lab server
** physics lab server
** Piston lab server
* Each installed depot will be verified to be working properly
** develop install verification test - do by hand if need be.
** individual install verification using chicken feeder

==April 1 - June 1... User testing of test deployment==
* stability testing under load - Clyde??? or use chicken feeder... (Bobby)
* Engh CMS testing
* Piston testing (McCaughey)
* Phoebe testing
** Saturating the medical network
** need 1 Gig connection to Phoebe
** use chicken feeder, extension of install verification test.
** time indeterminant, set by ITS and medical
* some coordination of use may be necessary so we don't get in each others way.
* as external depots added, include those in tests
* need to do test installs of the client by users on the major OSes.

==May 1 - July 1... external deployments==
* total of '''24 TBytes deployed externally, 75 TBytes in all'''
* by remote PDUs and KVMs - takes 1 week
* verify racks and rack mount issues are OK at remote sites.
* goal: 2 sites a month for two months.
* Potential Sites: (2 depots at each site)
** ORNL
** Michigan
** FIU
** Caltech - use our UltraLight connections
* Swap out old hardware, bring back to ACCRE to add in to local depots or just toss.
* install software prior to shipping, send someone out to bring up.
* bring up master REDDnet server
* all still using version 0.8 initially until rollout of version 1.0

==Rollout version 1.0 of L-Store - complete on July 1==
* can do in a scheduled downtime - takes half an hour.
* just need to do on server(s) which are local.
* how do clients work here? people are going to have to upgrade their clients...

==June 1 and beyond continue rolling out external sites, now with V1.0==
*sites and amounts TBD
*we need to discuss this!

==when is real release for all users? CMS for example...==
*need to decide!

REDDnet Hardware Release Schedule

2007-03-15T18:42:06Z

Rgb: /* May 1 - July 1... external deployments */

=Depot Network Milestones and Workplan=
The following assumes that the version of the L-Store code used for SFASU demo at the USGS in early March (we will call it 0.8) is the current "release" version and that the next release version will be version 1.0 which will become available June 1.
* need info on devel plan for libxio replacement...

==Local VU development cluster - complete by March 15?==
* 10(?) ACCRE depots + 4 metadata servers

==Local VU test/resease deployment - to be completed by April 1==
* Hardware Deployed - '''roughly 50 TBytes'''
** 2 systems in physics
** 2 systems in Pheobe (1 Gig link to be determined - ITS does)
** 2 depots piston lab in MRBIII (firewall issues not necessarily included)
** 10 ACCRE depots + 2 metadata servers
* Version 0.8 software in all cases...
** master campus server installed
** Phoebe lab server
** physics lab server
** Piston lab server
* Each installed depot will be verified to be working properly
** develop install verification test - do by hand if need be.
** individual install verification using chicken feeder

==April 1 - June 1... User testing of test deployment==
* stability testing under load - Clyde??? or use chicken feeder... (Bobby)
* Engh CMS testing
* Piston testing (McCaughey)
* Phoebe testing
** Saturating the medical network
** need 1 Gig connection to Phoebe
** use chicken feeder, extension of install verification test.
** time indeterminant, set by ITS and medical
* some coordination of use may be necessary so we don't get in each others way.
* as external depots added, include those in tests
* need to do test installs of the client by users on the major OSes.

==May 1 - July 1... external deployments==
* total of '''24 TBytes deployed externally, 75 TBytes in all'''
* by remote PDUs and KVMs - takes 1 week
* verify racks and rack mount issues are OK at remote sites.
* goal: 2 sites a month for two months.
* Potential Sites: (2 depots at each site)
** ORNL
** Michigan
** FIU
** Caltech - use our UltraLight connections
* Swap out old hardware, bring back to ACCRE to add in to local depots or just toss.
* install software prior to shipping, send someone out to bring up.
* bring up master REDDnet server
* all still using version 0.8 initially until rollout of version 1.0

==Rollout version 1.0 of L-Store - complete on June 1==
* can do in a scheduled downtime - takes half an hour.
* just need to do on server(s) which are local.
* how do clients work here? people are going to have to upgrade their clients...

==June 1 and beyond continue rolling out external sites, now with V1.0==
*sites and amounts TBD
*we need to discuss this!

==when is real release for all users? CMS for example...==
*need to decide!

REDDnet Hardware Release Schedule

2007-03-15T18:41:35Z

Rgb: /* April 1 - June 1... external deployments */

=Depot Network Milestones and Workplan=
The following assumes that the version of the L-Store code used for SFASU demo at the USGS in early March (we will call it 0.8) is the current "release" version and that the next release version will be version 1.0 which will become available June 1.
* need info on devel plan for libxio replacement...

==Local VU development cluster - complete by March 15?==
* 10(?) ACCRE depots + 4 metadata servers

==Local VU test/resease deployment - to be completed by April 1==
* Hardware Deployed - '''roughly 50 TBytes'''
** 2 systems in physics
** 2 systems in Pheobe (1 Gig link to be determined - ITS does)
** 2 depots piston lab in MRBIII (firewall issues not necessarily included)
** 10 ACCRE depots + 2 metadata servers
* Version 0.8 software in all cases...
** master campus server installed
** Phoebe lab server
** physics lab server
** Piston lab server
* Each installed depot will be verified to be working properly
** develop install verification test - do by hand if need be.
** individual install verification using chicken feeder

==April 1 - June 1... User testing of test deployment==
* stability testing under load - Clyde??? or use chicken feeder... (Bobby)
* Engh CMS testing
* Piston testing (McCaughey)
* Phoebe testing
** Saturating the medical network
** need 1 Gig connection to Phoebe
** use chicken feeder, extension of install verification test.
** time indeterminant, set by ITS and medical
* some coordination of use may be necessary so we don't get in each others way.
* as external depots added, include those in tests
* need to do test installs of the client by users on the major OSes.

==May 1 - July 1... external deployments==
* total of '''24 TBytes deployed externally, 75 TBytes in all'''
* by remote PDUs and KVMs - takes 1 week
* verify racks and rack mount issues are OK at remote sites.
* goal: 2 sites a month for two months.
* Potential Sites: (2 depots at each site)
** ORNL
** Michigan
** FIU
** Caltech - use our UltraLight connections
* Swap out old hardware, bring back to ACCRE to add in to local depots or just toss.
* install software prior to shipping, send someone out to bring up.
* bring up master REDDnet server
* all still using version 0.8 initially unti. rollout of version 1.0

==Rollout version 1.0 of L-Store - complete on June 1==
* can do in a scheduled downtime - takes half an hour.
* just need to do on server(s) which are local.
* how do clients work here? people are going to have to upgrade their clients...

==June 1 and beyond continue rolling out external sites, now with V1.0==
*sites and amounts TBD
*we need to discuss this!

==when is real release for all users? CMS for example...==
*need to decide!