REDDnet Hardware Release Schedule: Difference between revisions

From ReddNet
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
= Near-Term Hardware Deployment =
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.
== Validation, Verification, and Performance Testing Depot ==
* need info on devel plan for libxio replacement...
* We will deploy about 20 of the Capricorn Depots in a single system that can be used for validation, verification, and performance testing.
 
* This system will be for developers use only, and it can be taken down at any time. Software can be updated at any time.
=Depot Network Milestones and Workplan=
* Nightly, the L-Store development release code will be built, installed, and tested with Clyde.  This may take a few months to get going smoothly.
 
* this will be available to REDDnet users at the REDDnet Chicago meeting and afterwards, until public depots are available.
==Local VU development cluster - complete by March 15?==
== Public Campus (LAN) System ==
* 10(?) ACCRE depots + 4 metadata servers
* approximately 10 of the Capricorn Depots will be deployed for use by VU campus researchers
 
* A version of this will be made available with the release of L-Store 0.9 (end of January 2007).
==Local VU test/resease deployment - to be completed by April 1==
== Public User (WAN) System ==
* Hardware Deployed - roughly 50 TBytes
* The remainder of the systems will be deployed as a user facility, combined with the existing REDDnet depots.
** 2 systems in physics
* A version of this will be made available with the release of L-Store 0.9 (end of January 2007).
** 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.
 
==April 1 - June 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!

Revision as of 13:22, 8 March 2007

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...

Depot Network Milestones and Workplan

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.

==April 1 - June 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!