This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:tasklist [2008/08/19 11:51] jodal Move completed tasks to the tasklist3.4 node. |
devel:tasklist [2008/08/26 08:31] thomaska added commet about tasks being moved to lp |
||
---|---|---|---|
Line 151: | Line 151: | ||
====== Stein Magnus' Tasks ====== | ====== Stein Magnus' Tasks ====== | ||
- | ===== SMJ8: Reduce Device Management to Device History ===== | + | Tasks moved to [[https://blueprints.launchpad.net/nav]]. |
- | + | ||
- | ^ Assigned to | Stein Magnus Jodal | | + | |
- | ^ Estimated time | 40 hrs | | + | |
- | ^ Start date | | | + | |
- | ^ Status | | | + | |
- | ^ Due for | Post 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. | + | |
- | + | ||
- | When Device Management is reduced, so little is left that it may be a candidate for rewriting using the Django framework. | + | |
- | + | ||
- | ===== 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 | Post 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 | Post 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. | + | |
- | + | ||
- | Alternative solution: | + | |
- | + | ||
- | * I think we discussed earlier a backoff mechanism: When SMSD is unable to dispatch a message, it shouldn't keep retrying at fixed intervals, it should wait longer between each attempt, using a backoff factor and a configurable maxium retry count. Only on complete and utter failure should it log a CRITICAL message, and abandon/ignore the sms. It should perhaps log some details about the abandoned message as well. | + | |
- | + | ||
- | ===== SMJ13: IP Device Info ===== | + | |
- | + | ||
- | ^ Assigned to | Stein Magnus Jodal | | + | |
- | ^ Estimated time | 160 hrs | | + | |
- | ^ Start date | 2007-12-17 | | + | |
- | ^ Status | In development | | + | |
- | ^ Due for | NAV 3.4 | | + | |
- | ^ Depends on | SMJ4 | | + | |
- | + | ||
- | Implement IP Device Info (ipdevinfo). | + | |
- | + | ||
- | * ipdevinfo should be a full replacement of the features in IP Device Center and IP Info. | + | |
- | * Support the new NAV 3.4 virtual module model with the netbox.commander boolean attribute. | + | |
- | * (DONE, using Django) IP device center is too slow. Get rid of forgetsql and forgethtml. | + | |
- | * (DONE) Change the popup text on switch ports on the port activity tab from (used today, active now) to (MAC seen today, link now). | + | |
- | + | ||
- | + | ||
- | ===== SMJ14: Finish the new web design ===== | + | |
- | + | ||
- | ^ Assigned to | Stein Magnus Jodal | | + | |
- | ^ Estimated time | 20 hrs | | + | |
- | ^ Start date | | | + | |
- | ^ Status | | | + | |
- | ^ Due for | Post NAV 3.4 | | + | |
- | ^ Depends on | SMJ8, SMJ9, SMJ13 | | + | |
- | + | ||
- | The new web design which was introduced in NAV 3.3 is not fully complete: | + | |
- | + | ||
- | * Update design of AlertProfiles | + | |
- | * Update design of Edit DB (in coordination with SMJ9) | + | |
- | * Update design of Preferences | + | |
- | * Inner tab of Device Management does not show which tab is active (in coordination with SMJ8) | + | |
- | * Update design of the RRD viewer in IP Device Browser (defer, as IP Device Browser is being replaced in SMJ13) | + | |
- | * Eliminate use of colspan="0" as it is not supported in IE and Opera | + | |
====== John Magne's Tasks ====== | ====== John Magne's Tasks ====== | ||
Line 456: | Line 357: | ||
^ Due for | Post NAV 3.4 | | ^ Due for | Post NAV 3.4 | | ||
^ Depends on | | | ^ Depends on | | | ||
+ | ^ Blueprint? | Moved to lp | | ||
Rewrite Alert Engine (now Perl) in Python with all existing features, plus the following missing features: | Rewrite Alert Engine (now Perl) in Python with all existing features, plus the following missing features: | ||
Line 473: | Line 375: | ||
^ Due for | Post NAV 3.4 | | ^ Due for | Post NAV 3.4 | | ||
^ Depends on | | | ^ Depends on | | | ||
+ | ^ Blueprint? | Moved to lp | | ||
* Treeselect is awkward, starting at location confuses many. Tiresome to put many devices on maintenance. | * Treeselect is awkward, starting at location confuses many. Tiresome to put many devices on maintenance. | ||
Line 489: | Line 392: | ||
^ Due for | Post NAV 3.4 | | ^ Due for | Post NAV 3.4 | | ||
^ Depends on | | | ^ Depends on | | | ||
+ | ^ Blueprint? | Moved to lp | | ||
- (fixed 2007-09-28) A bug is reported, see SF#1799451 | - (fixed 2007-09-28) A bug is reported, see SF#1799451 |