Phases of the NETS DB project

• Phase 0 08/24/06 - 09/04/06
  Complete the foundation pieces needed to build everything else.
  • Approve initial schema
    
    • See schema drawings
    • Approved by all at 08/24 meeting
  • Document DB management procedures
    
    • How to recreate, populate, and do SELECTS on the database, etc - DM
  • Libraries for data access
    
    • Basic functions like "add node" or "list routers", created as needed
    • Python by DM
    • Perl by PS
  • Scripts to add/edit/remove data
    
    • Command-line tools that use the libraries
    • Python by DM
    • Perl by PS
• Phase 1 09/04/06 - 09/16/06
  This phase will pick the low hanging fruit of tasks. Quite a few of our scripts and tools need not much more than a list of devices and community strings. Getting these done lets us become comfortable with our DB management and stability.
  • Cricket: needs names of routers, switches - DM
  • Pancho: needs names of routers, switches - DM
  • Movaz config fetcher: needs names of Movazen - PS
  • Port lists: needs names of routers and switches - PS
  • Config checker: needs names of routers and switches - PS
  • Nagios: needs names of monitored devices and their preferred IP and parents - PS
  • Live inventory: needs list of names of monitored devices - PS
  • Add real data and go "production", replacing existing sources of data with the database - DM and PS
• Phase 2 09/16/06 - ???
  Once we have become comfortable with our simple tasks, we can begin working on some more sophisticated items. These will be worked on in parallel.
  • Web forms
    • Initially, simple live web pages that show, like, "Routers", "Switches", etc.
    • Interactive forms allowing the user to search.
    • Forms for add/edit/remove. These will relate closely to the command-line scripts created in Phase 0.
    • PS and DM
  • Phones/LDAP
    • Add People/Extensions/Rooms to the database and make it available via LDAP - JV
    • Generate the Blue/Yellow/White pages from the database, or replace them with live web pages that access the database
  • Hardware/Inventory
    • Replace current switch inventory spreadsheet with live web page - DM
    • Replace current live inventory with live web page - PS
• Phase 3
  Longer term items which are more of a 'wish list' right now.
  • Move master networks file / VLAN table into database
  • Migrate wireless AP database into main database
  • Track MAC's / ARP entries and keep history
  • Assure that there are NOC web pages for all monitored devices.
  • Track hardware events like "board RMA'd to Cisco on 8/25/2006".