Operations and Deployment: Difference between revisions

From ReddNet
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
= Deployment =  
=== Deployment ===  
* Bring current deployment up-to-date
* Bring current deployment up-to-date
** Build new image for 2GB internal USB memory
** Build new image for 2GB internal USB memory
Line 30: Line 30:
** Perceus (long term)
** Perceus (long term)


= Monitoring =  
=== Monitoring ===
* Use StorCore, Nagios, iperf, and visualization tools from SC07  
* Use StorCore, Nagios, iperf, and visualization tools from SC07  
** Have a statistic page that gathers information from tests and presents them cleanly
** Have a statistic page that gathers information from tests and presents them cleanly
Line 39: Line 39:
* Create an RT site to resolve users' issues
* Create an RT site to resolve users' issues


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

Revision as of 08:29, 28 January 2008

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