Operations and Deployment

From ReddNet
Jump to navigation Jump to search

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