Nav-dev

nav-dev@lister.sikt.no

96 discussions

NAV status meeting minutes 2009-01-27
by Morten Brekkevold 29 Jan '09

29 Jan '09

NAV status meeting minutes 2009-01-27 ===================================== Jørgen ------ * Improved page design in report system (table-less, liquid front.html and tabled report list). * CSV-export underway. * Some CSS tweaks. * Killing old/unused report code. Magnus ------ * Fixed bugs reported in Alert Profiles. * Working on device history, which is mostly functional now. - Working out search kinks - Page design is a mess, need feedback and testing. Thomas ------ * Fighting with IE (quicksearch component was reported to not work in IE) * Fixed reported bugs in Alert Engine. * Working on ipdevpoll - topological sort implemented for plugin dependency handling. - Need feedback on persistence layer. Morten ------ * NAV 3.5.0 released. * Fixed reported bugs in snmptrapd and getBoksMacs. * Met with Ole Martin Bjørndalen from Tromsø University, discussed their MailIn system, among other things. - Will write a design specification for MailIn, so Ole Martin will know what basic direction to work in. Hopefully, we can have somthing in time for NAV 3.6. * Wrote a Mercurial extension to quickly fill a changeset log or MQ patch description with information about a Launchpad-registered bug. * Unable to find an optimal timeslot for status meetings this spring. Will prioritize in-house developers, so John-Magne seems to be out of luck. -- mvh Morten Brekkevold UNINETT

1 0

Proposal: Simpler source file headers
by Stein Magnus Jodal 22 Jan '09

22 Jan '09

Hi, I've written up a proposal on what source file headers should contain at [1]. Comments, changes, questions welcome from everyone. Approval of the proposal welcome from Vidar and/or Morten. [1] http://metanav.uninett.no/devel:source_file_headers -- Stein Magnus Jodal UNINETT

4 6

Bugfixing for 3.5
by Morten Brekkevold 22 Jan '09

22 Jan '09

Hi everyone, thanks for your good work and contributions towards creating the 3.5.0 release! Now, a word on bugfixing the 3.5 series. As of this writing, there are already 6 open bug reports targeted for a 3.5.1 release, which I've scheduled for March 1st (incidentally, these are all assigned to Kristian, and were moved from the 3.5.0 target because of lack of progress). series/3.5.x is now considered the stable branch. Clone this branch for any bugfixes you need to make to the 3.5 series (NB: There's a 3.5.x named branch in this repo, so don't forget to do an "hg update -C 3.5.x" after cloning). As before, I like to review patches for the stable branches, so push access to https://metanav.uninett.no/hg/series/3.5.x is only open for me at this time. When you've created changesets on the 3.5.x branch, notify me of where I can pull them from, or mail them to me as patches or hg bundles. I'll review them and (hopefully) push them to the above URL. Don't make your 3.5-bugfixes in your feature branches. Those branches which have been merged with default in time for 3.5.0 should be closed and moved to the dead directory at metanav. New features for 3.6 and future series will still happen on separate feature branches and be merged to default as they mature. Questions? Happy hacking! -- mvh Morten Brekkevold UNINETT

1 0

Device operational lifecycle
by Morten Brekkevold 21 Nov '08

21 Nov '08

As you know, we're planning to get rid of some of the complexity of recording device lifecycle events in NAV, by removing parts of the device management system. Yet, it appears that parts of the lifecycle event recording that was planned, is still wanted, and should have been present since 2003 has not been properly implemented. As the tigaNAV report [1] of 2003 states, there are supposed to be events for "start of operation" and "end of operation". When a device is first seen on the network, serving as either a netbox or a module, a "start of operation" event should be posted. When the netbox is deleted, an "end of operation" event should be posted. This is all neatly explained on pages 56-57 of the report. Also, when a netbox is replaced in the field, one "end of operation" should be posted for the old device, and a "start of operation" should be posted for the new device. The former seems to have never been implemented. The latter is partially implemented through the serialChanged event type, which is posted by getDeviceData when it notices that a netbox' serial number has changed. Before I go on, I'll add this reference to an ongoing issue where this surfaced: https://bugs.launchpad.net/nav/+bug/285336 The serialChanged event does not have the deviceid field set, because it is related to two deviceids, not one. A consequence of this is that alerthist entries for serialChanged will never be removed from the database, even when the netbox is deleted. The only trigger action here is setting netboxid=NULL when a netbox is deleted. The alerthist table is left with orphaned records (i.e. no deviceid or netboxid foreign keys set). There does exist a deviceState event type, with at least to related alert types (deviceInIPOperation, deviceInStack) that address the aforementioned lifecycle events from tigaNAV. These lack the corresponding stop-events, and they seem to be unused by NAV - at least, I cannot find them present in the alerthist tables of any of the installations I've checked. So far, this is all informational. Here's hoping that some discussion will result from this. Nonetheless, this is material for a blueprint. Seeddb obviously needs modification to support this, and so does gDD. Probably, it will be implemented as part of the new ipdevpoll, not gDD, so hopefully it will be there in NAV 3.6. [1] http://metanav.uninett.no/static/reports/tigaNAV.pdf -- mvh Morten Brekkevold UNINETT

1 0

NAV status meeting minutes 2008-10-23
by Morten Brekkevold 23 Okt '08

23 Okt '08

NAV status meeting minutes 2008-10-23 ===================================== Jørgen ------ * Fixed report list bug (random sort order), reduced bloat in the process. * Moved report files to fit with new structure proposed by jodal. * (re)Centered search result table captions. * Advanced search form close bug fixed (LP#276246). * Report now invalidates result cache if report.conf is modified. * Cache timestamp displayed in search results. * Refactored report JavaScript to use jQuery. * Looking forward to bugsquashing today. Thomas ------ * Testing pping/servicemon, attempting to automatically provoke the bug described in LP#258321. - Committed a patch that seems to work, for reasons unknown. Patch needs more work. - Will try to provoke the bug while running strace on the processes. * Fixed reported bugs in alert engine. Morten ------ * Werner visited last Monday, working on the Debian package. - He has published a working nav_3.5.0b1 package in his etch-test repository, but not announced it yet. - I have installed this on four beta-test volunteers' servers. - Werner is working on some more packaging details to better comply with Debian standards, which will increase our chances of successful upload to Debian unstable archives. - Discussed ideas for improving verification of database schema upgrades. One idea is to implement a db table that tracks the schema version, and is the last to be updated in a schema upgrade transaction. * Fixed concurrency issues in getDeviceData's ArpHandler, and related issues that were discovered during debugging. * Resumed work on the hp-switchstack blueprint (https://blueprints.launchpad.net/nav/+spec/remove-hp-switchstack-hack) - Made some patches for snmptrapd/makecricketconfig/arnold, which John-Magne should review. * Suggestion to write a blueprint for removing forgetSQL entirely from NAV. * Suggestion to write a script to pull launchpad bugtracker numbers from Mercurial changelog, pull bug report titles from launchpad and compose a bugfix-changelog suitable for inclusion in NAV's CHANGES file. John-Magne ---------- * Present, but has not made any NAV-related progress in a while. Discussion ---------- Stein Magnus has proposed some changes to the way our source code headers are made up. Constructive debate at meeting, conclusions will be posted in Stein Magnus' thread at nav-dev. -- mvh Morten Brekkevold UNINETT

1 0

22 bugs currently targed for b2
by Vidar Faltinsen 20 Okt '08

20 Okt '08

Dear developers, I see 22 bugs targeted for b2. Morten told me the b2 date will be postponed one week, probably till Oct 28. I hope all these bugs will have fix committed by then. Keep up the good work, folks :) We then have max one week to set the final 3.5 release, that is Nov 04. Morten then has a couple of days for installing the release on all the verktoykasse before he leaves for the lisa conference. Remember there is a NAV/verktøykasse gathering Nov 19. Feel free to attend, at least on the NAV part! Lunch is on me, give me a hint, https://ow.feide.no/gigacampus:samling:vk_des_2008 cheers - Vidar

1 0

Status meeting minutes, 9 October 2008
by Morten Brekkevold 09 Okt '08

09 Okt '08

Status meeting minutes, 9 October 2008 ====================================== Magnus ------ * Last finish on Alert Profiles, "it works". * Been testing for bugs. * Still lots of bugs to fix in the new Device History tool. "Register error event" not yet implemented. Jørgen ------ * Finished implementing caching + summing in time for 3.5.0b1 * Bugs in report system have been reported, will be working on these next. Kristian -------- * Currently refactoring network explorer, completing the search function. Thomas ------ * Been busy with school projects. * Will prioritize the pping/servicemon stability bug next (LP#258321). Morten ------ * Mostly working on merging, testing and fixing of the code to release 3.5.0b1. A two day internal seminar delayed the release further, which in total was delayed one week. * No feedback on the beta release yet. Still waiting for Werner's Debian package so we have something to ship to our beta testers. * Assigned several high-priority bugs to self. Hoping to have time to fix all of them in time for the 3.5.0 final release. Discussion ---------- Launchpad issues: We can paste changelog info into release details, but where does it show up in the release page? Nowhere, it seems. Quick look at http://help.launchpad.net seems to suggest that changelogs and release notes can/should be uploaded as separate files in the release. Still doesn't explain what the changelog textarea in the release details form is used for. Should probably send a support question to the Launchpad team. Various network weather maps from http://drift.uninett.no/kart/ were demoed. Olav Kvittem has submitted a project to Sør-Trøndelag University College, which aims to develop some sort of OpenStreetMap+NAV mashup. -- mvh Morten Brekkevold UNINETT

1 0

Suggested text for the new netmap
by Vidar Faltinsen 26 Sep '08

26 Sep '08

Netmap Netmap is a network weather map that displays the layer 3 and layer 2 topology of your network. Current traffic conditions are shown using colored links. - Vidar

2 1

Removing HP SwitchStack support from NAV
by Morten Brekkevold 17 Sep '08

17 Sep '08

Hi everyone, for quite some time we've been aware of many fundamental problems with the way support for HP SwitchStacks has been implemented in NAV. HP SwitchStack support was implemented in NAV 3.0 at NTNU, whose HP equipment consisted solely of HP SwitchStacks at that time. The result is code which is heavily biased towards SwitchStacks, to the point that NAV thinks HP devices are always SwitchStacks, no matter what. While we have been pondering alternative ways to model HP SwitchStacks (and consequently, Cisco switch clusters, which are basically the same thing), NTNU has entirely stopped using SwitchStacks. Today, they're experiencing bad side effects of the existing HP-related code in NAV. They're using some HP devices for routing, which NAV cannot handle at all (because of said "HP=SwitchStack only" view). No router ports are collected for these routers. Also, they seem to have many errors in topology information when HP devices are involved. Realizing that NTNU have stopped using SwitchStacks, we also do not know of anyone else who does, so now we are considering dropping support for SwitchStacks entirely from NAV. This way, the existing NAV code can treat HP devices like everything else. Preliminary tests of these changes at NTNU show promising results. So my question to the users of NAV is: Does anyone actually use virtually stacked HP switches? Will anyone miss support for this if removed from NAV? If there is no feedback on this issue, we will likely remove this support starting from NAV 3.5. -- mvh Morten Brekkevold UNINETT

2 3

Regarding IP info center and 3.5
by Vidar Faltinsen 12 Sep '08

12 Sep '08

Stein Magnus, As I understand it IP Device Info will be feature complete for 3.5 and will be included as a new tool, now also seen from the toolbox. Will you use the RJ45 jack as icon (the one from IP Info center)? Perhaps better with an icon of a switch or something? How about "stealing" the Device Management icon? And then for the new Device History use a faded router icon, perhaps surrounded with a graph or cornered with a clock indicating history? Suggestion for the text in toolbox: "IP Device Info displays all recorded information about a given IP address. If the device is a NAV registered switch or router a port view with details on status and activity is also shown" Even if you are not reimplementing IP Info Center, is it possible to remove this as a tool from the toolbox and instead invoke the tool from the query page of ipdevinfo, in the case the given ip is not a NAV registered box? I think leaving the two tools in the toolbox will confuse users (as indeed is the reason for merging the tools in the end). I further suggest IP Device Info is listed in the toolbox after report. BTW - Morten; The first box in the report links today to "IP Device Center" and leads to /browse Change to "IP Device Info" and go to /ipdevinfo It seems this change has to be done all over the place in report; swap links for /browse with /ipdevinfo Morten; I guess we should work through more of the text from the toolbar. Also the text for the verktøykasse nfsen, here I suggest: "NFSen integrates with NAV to analyze and display your netflow traffic data" - Vidar

3 7

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Nav-dev