NAV Wiki

User Tools

Site Tools

Trace:
devel:tasklist

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
devel:tasklist [2007/10/15 11:20]
faltin 		devel:tasklist [2009/06/09 11:14]
morten warning about the relevance of this page
Line 1: Line 1:
 +:!::!::!: This page is no longer relevant. ​ NAV tasks are now registered as [[https://​blueprints.launchpad.net/​nav|blueprints on Launchpad]]. :!::!::!:
 ====== Task list ====== ====== Task list ======
  
Line 7: Line 8:
 NAV releases, see the [[:​roadmap]]. Also see lower priority tasks i [[TaskListLowPri]]. NAV releases, see the [[:​roadmap]]. Also see lower priority tasks i [[TaskListLowPri]].
  
-In time, we are hoping to migrate ​most of these tasks into the [[http://sourceforge.net/pm/?​group_id=107608|SourceForge task list for the NAV project]].  ​ +In time, we are hoping to migrate these tasks into [[https://blueprints.launchpad.net/nav|LaunchPad blueprints]].  ​
- +
- +
- +
- +
- +
-===== NAV 3.4 Plan ===== +
- +
-Our current commit strategy for NAV 3.4 in December includes: +
- +
-   - A rewrite of todays HP virtual module hack to a general virtual module concept.  +
-     * This will in effect open support for Cisco clustering as well +
-   - General ENTITY MIB support. +
-     * This opens for support for chassis based HP switches. +
-     * Requires a change to varchar as module number.  +
-     * Consider a self reference on module, which allow for hierarchical modules (GBICs and such) +
-   - [[#​ss3support_ipv6_in_nav|IPv6 support]]  +
-   - [[#​jm2new_features_in_arnold|Arnold improvements]] +
-   - [[#​ss1new_interactive_and_dynamic_layout_engine_in_traffic_map|New network map]] (as a beta, vlanplot will still be there) +
-   - (if we make it) [[#​smj13reimplement_ip_device_center|Speed up IP device center & support virtual modules]]  +
  
 ====== Morten'​s Tasks ====== ====== Morten'​s Tasks ======
- 
  
 ===== MB2: Support auto insertion of types ===== ===== MB2: Support auto insertion of types =====
Line 61: Line 41:
 ^ Estimated time | ? hrs      | ^ Estimated time | ? hrs      |
 ^ Start date     ​| ​           | ^ Start date     ​| ​           |
-^ Status ​        | Complete? ​ |+^ Status ​        ^ Completed ​ |
 ^ Due for        | ?          | ^ Due for        | ?          |
  
   * Support the ability to except certain prefixes from data collection. Implement config file support.   * Support the ability to except certain prefixes from data collection. Implement config file support.
-  * (2007-08-13) ​Possibly already ​implemented by Jostein Gogstad on his IPv6 branch. ​ Needs further testing.+  * (2007-08-13) ​Already ​implemented by Jostein Gogstad on his IPv6 branch. ​ Needs further testing. Seems ok.
  
 ===== MB4: Collect system.sysname in addition to dns names ===== ===== MB4: Collect system.sysname in addition to dns names =====
Line 77: Line 57:
 ^ Estimated time | ? hrs      | ^ Estimated time | ? hrs      |
 ^ Start date     ​| ​           | ^ Start date     ​| ​           |
-^ Status ​        ​| ​           |+^ Status ​        ​| ​low pri           |
 ^ Due for        | ?          | ^ Due for        | ?          |
  
Line 89: Line 69:
 ^ Estimated time | ? hrs      | ^ Estimated time | ? hrs      |
 ^ Start date     ​| ​           | ^ Start date     ​| ​           |
-^ Status ​        |            ​|+^ Status ​        ^ Done - by John Magne - June 2008    ​|
 ^ Due for        | ?          | ^ Due for        | ?          |
  
Line 113: Line 93:
 ===== MB8: Support delayed SMSes ===== ===== MB8: Support delayed SMSes =====
  
-^ Assigned ​to    | Morten Brekkevold | +Task moved to [[https://blueprints.launchpad.net/​nav/​+spec/​delayed-sms-messages]].
-^ Estimated time | 40 hrs     | +
-^ Start date     ​| ​           | +
-^ Status ​        ​| ​           | +
-^ Due for        | ?          | +
- +
-NAV v2 had the functionality of sending delayed SMS messages. The idea was that the +
-guard on duty should be able to sleep  through less important alerts during the night. +
-In the morning he/she should get updates on SMS. These updates should **not** include +
-events that have fixed themselves during the night. +
- +
-A modification of alert engine and alert profiles is needed to implement this support.+
  
 ===== MB9: New logging system for Java based subsystems ===== ===== MB9: New logging system for Java based subsystems =====
Line 158: Line 127:
 The HP plugin apparently only supports virtual HP stacks and does not understand physical stacks (e.g ProCurve 5308). ​ Physical HP stacks can be understood pretty well by looking at ENTITY-MIB, so it might be a good idea to implement a generic device-plug in for ENTITY-MIB, and make sure the HP plug in does HP specific things afterwards. The HP plugin apparently only supports virtual HP stacks and does not understand physical stacks (e.g ProCurve 5308). ​ Physical HP stacks can be understood pretty well by looking at ENTITY-MIB, so it might be a good idea to implement a generic device-plug in for ENTITY-MIB, and make sure the HP plug in does HP specific things afterwards.
  
 +===== MB12: Rewrite getDeviceData in Python =====
  
-====== Stein Magnus'​ Tasks ======+^ Assigned to    | Morten Brekkevold (and others)| 
 +^ Estimated time | ? hrs      | 
 +^ Start date     ​| ​           | 
 +^ Status ​        ​| ​           | 
 +^ Due for        | 3.6        |
  
-===== SMJ3: Improve ​the report tool =====+Design- and maintenance problems with the getDeviceData codebase, couple with our long term goal of reducing the number of programming languages in NAV, has prompted us to envision a new getDeviceData based entirely on Python code. 
 +It is likely that this would be based off the Twisted framework for asynchronous SNMP polling, which will reduce the complexity introduced by threading in the original gDD.
  
-^ Assigned to    | Stein Magnus Jodal (and Morten) | 
-^ Estimated time | 120 hours         | 
-^ Start date     ​| ​                  | 
-^ Status ​        ​| ​                  | 
-^ Due for        | NAV 3.4 and later | 
  
-  * Add support for local reports. +====== Stein Magnus' ​Tasks ======
- +
-   ​Separate local reports in a local file so that NAV's own reports +
-   are not altered. Local reports with equivalent name as the NAV +
-   ​report takes precedence. The local report does not have to copy all +
-   the original report variables, only the ones that are to be +
-   ​replaced. +
- +
-  * Make an automated report page. +
- +
-   This page gives a listing of all reports defined with +
-   their title and a description. $description is not +
-   a variable today - this should be added. +
-   We suggest the report list is linked from the static +
-   ​report main page of today. We suggest an alphabetical +
-   ​listing. +
-  +
-  * Implement a sum function ($sum).  +
- +
-   This is interesting in some reports, i.e. where we give a machine count on all +
-   ​machines on all prefixes. A total on this report will +
-   give the total number of machines in the network. +
-   This functionality was also present in NAV v2. +
- +
-  * Morten: Add a **duplex mismatch** report. +
- +
-   This report should show analyze all interconnection between +
-   ​switches and look at the duplex value on each side of the +
-   link. If there is a mismatch a row in the report should +
-   be produced. Ideally this report should be empty at all times. +
-   The report can be produced using one (rather complex) SQL +
-   ​sentence in report.conf. We have done something similar +
-   in NAV v2 - NTNU has a solution for their v3!  +
- +
-  * Morten: Also add a **spanning tree blocked ports** report.  +
- +
-   Once again - steal from the NTNU v3 installation. +
- +
-  * Post NAV 3.4: Enhance/​partially rewrite the report code base.  +
- +
-   The overall goal being to improve performance and code readability. +
-   This task may be dropped if it involves a lot of work. +
- +
- +
- +
-===== SMJ4B: Improve the Machine Tracker continued ​===== +
- +
-^ Assigned to    | Stein Magnus ​Jodal | +
-^ Estimated time | 20 hrs             | +
-^ Start date     ​| ​                   | +
-^ Status ​        ​| ​                   | +
-^ Due for        | NAV 3.4            | +
- +
-The following needed further clarification at a meeting, and has not been implemented in 3.3: +
- +
-  * Originally: Support search all the way to room using the cabling and patch data input from Edit DB. +
-    * Comment: Link historic data in the cam table with current data in the patch/​cabling/​room tables?! +
-    * Resolution: Link to the port view in IP Device Center, stating clearly that the data is reflecting the current situation. Add patch/​cabling/​room information to IP Device Center port view. +
-  * Originally: The MAC search result should include port description. Perhaps link to report? +
-    * Comment: As it stands, the only port description available for retrieval is the current one.  This will not be accurate for historical results, unless we make changes to the CAM table and the camlogger to add historical information about port descriptions. +
-    * Resolution: Link to the port view in IP Device Center, stating clearly that the data is reflecting the current situation. +
- +
- +
-===== SMJ5: Rewrite Alert Engine ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 120 hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
- +
-Rewrite Alert Engine (now Perl) in Python with all existing features, plus the following missing features: +
- +
-  * Support all operators from AlertProfiles (defined in subsystem/​alertprofiles/​config.php:​31) +
-  * Support subcat +
- +
- +
-===== SMJ6: Merge IP Info and IP Device Center to IP Device Info ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 80 hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
-^ Depends on     | SMJ4      | +
- +
-The features of IP Info is mostly a subset of IP Device Center, thus IP Info should be merged into IP Device Center. +
- +
-  - Add room/patch support to Machine Tracker. This is a part of SMJ4. +
-  - Extend IP Device Center to show IP/hostname for hosts which is unknown to NAV, just like IP Info does today. +
-  - Remove the IP Info subsystem. +
-  - Rename IP Device Center (sysname devBrowser, webname browse) to IP Device Info (sysname and webname ipdevinfo, with redirect from webname browse). +
-  - Change all links from /browse to /​ipdevinfo. +
-  - Add IP Device Info search box on the front page, in addition to the existing search box at the reports main page. +
-  - New icon for IP Device Info +
- +
- +
-===== SMJ7: Fix the User Admin panel ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 20 hrs             | +
-^ Start date     ​| ​                   | +
-^ Status ​        ​| ​                   | +
-^ Due for        | NAV 3.4            | +
-^ Depends on     ​| ​                   | +
- +
-  - (fixed 2007-09-28) A bug is reported, see  SF#​1799451 +
-  - Implicit memberships should be indicated in the tool. A new user has implicit membership to anonymous and authenticated +
-  - The report_access privilege should be removed from the grant privilege dropdown +
-  - The default "​Authenticated users" web_access regexp needs updating do to changes in tool urls. (new: seeddb / devhist / ipdevinfo, gone: browse / ipinfo) +
-  - Improvements when creating a user, see SF#​1805506 +
- +
- +
- +
- +
-===== SMJ8: Reduce Device Management to Device History ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 40 hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-   - Remove three tabs: Order, Register serial numbers, Register RMA  +
-   - Remove two tables: product and deviceorder +
-   - Remove the product add, edit, bulk from edit database +
-   - Are the device fields auto, active and deviceorderid now superfluous - check +
-   - There may be some eventtypes that are superfluous +
-   - Reduce complexity in module delete: Deleting a module deletes it. period. The attributes inactive and inventory are superfluous. Check what happens to a deleted module. The device is kept, right? With serial? If gDD encounters the device, as a module on another netbox, he will use this device record for the new module? How can we see all devices that are floating, i.e. not attached to a netbox or module? +
-   - Rename "​Module Delete"​ to "​Delete Module"​ +
-   - Keep Register error event - but bug fix. Verify that it works as intended. Also when one chooses a whole room... Things should show up in Device history. +
-   - Rename the whole tool from Device Management to Device History with url devicehist. ​  +
- +
-In addition: +
- +
-   * Device History lacks support for filtering on location/​room. +
-   * Module Delete sub-tabs are not hi-lighted. +
- +
-===== SMJ9: Edit DB / Seed DB ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 80 hrs (it is 7000 lines of code in one file!) | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-   - Change the name to Seed Database, url seeddb. Links from all over updated. +
-   - There is a reported bug on add prefix and dropdown static: SF#​1805143. +
-   - As mentioned in SMJ8: remove product. +
-   - If time: update style (this can be postponed) +
-   - Sorting by cabling/​patch columns in EditDB doesn't work, see SF#​1803283 +
- +
- +
- +
-===== SMJ10: Queuing of error messages by mail from SMSD ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | 40 hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-Summary of mail from Morten 2007-09-04:​ +
- +
-   The SMTP loghandler for SMSD does only accept log messages of level CRITICAL +
-   or higher. Is it possible to make SMSD/logger queue these log messages and +
-   send them together in batches to avoid several error mails per minute from SMSD? +
- +
-Proposed solution: +
- +
-  * Look at possibilities for doing this with standard logger. +
-  * Secondary, create a new log handler for logger, which does queuing of messages. +
- +
-===== SMJ11: Improve Switch search in Machine Tracker ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | ? hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | post NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-   * Put the mac column to the right +
-   * Add an "​active IP" column showing active IPs on active mac rows +
-   * Add an optional dns column that resolves the active IPs +
- +
-===== SMJ12: Swap treeselect in maintenance with "​intelligent form" ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | ? hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | post NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-   * Treeselect is awkward, starting at location confuses many. Tiresome to put many devices on maintenance. +
-   * A form where users can cut'n paste in a number of boxes would be good. +
-   * Should also be possible to input rooms, substrings of sysnames/​rooms +
- +
- +
- +
- +
-===== SMJ13: Reimplement IP device center ===== +
- +
-^ Assigned to    | Stein Magnus Jodal | +
-^ Estimated time | ? hrs    | +
-^ Start date     ​| ​          | +
-^ Status ​        ​| ​          | +
-^ Due for        | NAV 3.4   | +
-^ Depends on     ​| ​          | +
- +
-   * IP device center is still to slow. Get rid of forgetsql (and forgethtml) +
-   * Keep todays functionality +
-   * Support the new NAV 3.4 virtual module model with the netbox.commander boolean attribute +
-   * Change the popup text on switch ports on the port activity tab: +
-     * now it says: used today, active now. Hard to understand... +
-     * write: mac seen today, link now+
  
 +Tasks moved to [[https://​blueprints.launchpad.net/​nav]].
  
 ====== John Magne'​s Tasks ====== ====== John Magne'​s Tasks ======
Line 519: Line 271:
   * strengthen the admin view when moving routers around. ​   * strengthen the admin view when moving routers around. ​
  
 +====== Jørgen Abrahamsen'​s Tasks ======
  
-====== Jostein Gogstad'​s Tasks ======+===== Contact info =====
  
 +^ Email | jorgen.abrahamsen@uninett.no | 
 +^ Phone | +47 97 04 49 45 | 
  
-===== SS3: Support IPv6 in NAV =====+===== JA1: Improve the report tool =====
  
-^ Assigned to    | Jostein Gogstad ​| +^ Assigned to    | Jørgen Abrahamsen (and Morten) ​| 
-^ Estimated time | 160 hrs         | +^ Estimated time | 120 hours         | 
-^ Start date     ​| ​                ​| +^ Start date     ​| ​06.02.2008 (dd.mm.yyyy) ​      | 
-^ Status ​        ​| ​Completed ​/ Untested ​| +^ Status ​        ​| ​in progress/being worked on |     ​ 
-^ Due for        | NAV 3.4         ​|+^ Due for        | NAV 3.4 or 3.5 and later |
  
-NAV does not support ​IPv6 today. Look into support in this order of priority:+  * Add support ​for local reports. (DONE)
  
-  - Gather data from all routers for IPv6 router ports / prefixes +   ​Separate local reports in a local file so that NAV's own reports 
-  - Complement this with a IPv6 prefix matrix +   are not altered. Local reports ​with equivalent name as the NAV 
-  - Gather IPv6 machine tracker data (IPv6 "​arp"/​neighboring cache). +   report takes precedence. The local report does not have to copy all 
-  - Consider IPv6 traffic statistics (there are separate IPv6 traffic counters, we think...) +   the original report variables, only the ones that are to be 
-  - Look at collecting snmp data from netboxes using IPv6. This we consider far fetched.+   replaced.
  
 +  * Make an automated report page. (DONE)
  
-====== Summer Student Tasks ======+   This page gives a listing of all reports defined with 
 +   their title and a description. $description is not 
 +   a variable today - this should be added. 
 +   We suggest the report list is linked from the static 
 +   ​report main page of today. We suggest an alphabetical 
 +   ​listing. 
 +  
 +  * Implement a sum function ($sum). (DONE)
  
 +   This is interesting in some reports, i.e. where we give a machine count on all
 +   ​machines on all prefixes. A total on this report will
 +   give the total number of machines in the network.
 +   This functionality was also present in NAV v2.
  
-===== SS2: Support generic ​(and HP) syslog messages in the syslog analyzer =====+  * The advanced search form should be dynamically activateable by using Javascript. ​(DONE)
  
-^ Assigned to    | Unassigned ​     | +   ​Today,​ the entire report SQL is re-run when the button for the advanced search form is pressed. ​ This is a waste of resources. 
-^ Estimated time | ? hrs           ​| +   The form should always be in the HTML output, and Javascript should be employed to dynamically display and hide the form from the flow of the page. 
-^ Start date     ​| ​                ​| + 
-^ Status ​        ​| ​                ​| +  * Post NAV 3.4: Enhance/​partially rewrite the report code base.  
-^ Due for        | Post NAV 3.4    |+ 
 +   The overall goal being to improve performance and code readability. 
 +   This task may be dropped if it involves a lot of work. 
 + 
 + 
 +  * Unordered List Item 
 + 
 +====== Thomas Adamcik'​s Tasks ====== 
 + 
 +Tasks moved to [[https://​blueprints.launchpad.net/​nav]]. 
 + 
 + 
 +====== Unassigned Tasks ====== 
 + 
 + 
 +===== UT1 (was SS2): Support generic (and HP) syslog messages in the syslog analyzer ===== 
 + 
 +^ Assigned to    | Unassigned ​  ​| 
 +^ Estimated time | ? hrs        | 
 +^ Start date     ​| ​             | 
 +^ Status ​        ​| ​             | 
 +^ Due for        | Post NAV 3.4 | 
 +^ Depends on     ​| ​             ​|
  
   * HP has syslog messages with four levels. Map these to equivalent cisco levels and support the HP log format so that the messages can be imported in the NAV logger database.   * HP has syslog messages with four levels. Map these to equivalent cisco levels and support the HP log format so that the messages can be imported in the NAV logger database.
   * The syslog parser should be made more generic, so that messages from UPSes and whatnot can be included.   * The syslog parser should be made more generic, so that messages from UPSes and whatnot can be included.
 +
 +
 +===== UT3 (was SMJ11): Improve Switch search in Machine Tracker =====
 +
 +^ Assigned to    | Unassigned ​  |
 +^ Estimated time | 10 hrs       |
 +^ Start date     ​| ​             |
 +^ Status ​        ​| ​             |
 +^ Due for        | Post NAV 3.4 |
 +^ Depends on     ​| ​             |
 +
 +   * (done 2008-04-20) Move the MAC column to the right. I.e. change column order from (MAC, Switch, Module, Interface, Start time, End time) to (Switch, Module, Interface, Start time, End time, MAC).
 +   * For rows where end time is "Still active":​
 +     * Add an "Last known IP" column
 +     * Add an optional "Last known hostname"​ that resolves the IP address in "Last known IP"
  
devel/tasklist.txt · Last modified: 2012/11/16 09:37 by morten

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki