Nav-dev

nav-dev@lister.sikt.no

96 discussions

Neat
by Vidar Faltinsen 09 Sep '08

09 Sep '08

https://launchpad.net/nav/+milestone/v3.5.0 ey, ey, ey very neat. I like. I am missing a couple of blueprints: * improvements in netmap o the best list is from the minutes of the July 1 meeting * remove vlanplot and tomcat (is this a blueprint?) - Morten: o we should remove the traffic map portion of seed db as well then? might complicate the possibility of running vlanplot as a contrib? o there are also some (3) vlanplot specific tables: http://metanav.uninett.no/devel:database#traffic_map - Vidar

2 2

Status on certain tasks
by Vidar Faltinsen 09 Sep '08

09 Sep '08

Dear summer developers, Could you please enlighten me, Kristian, * Is all of this done; http://metanav.uninett.no/devel:tasklist I will test, but your word is of value :) your blueprint status is "good progress"... * For the network map * Are we sure the rrd values you get are correct? On nav.uninett.no trd-osl has no load... there should be heaps of traffic here... * The absolute view... how is that coming a long? * Layer two cricket stats - can you display that? i.e. between two swithes Magnus/Thomas * For alert profile/user admin is the following solved; with reference to http://metanav.uninett.no/devel:tasklist - MB7: Admin can change his/her effective user ID - MB8: Support delayed SMSes Magnus; * When deleting a profile subscription you get an extra confirm page for the delete. The info presented there is not what one expect, it reflects the profile time period, not the actual subscription I was to delete... * Have you had a complete walk thru/demo of alert profiles with Morten? If not we should do this and look for potential bugs/missing stuff Thomas; * The new user admin panel returns an error message on navdev. Hard to test :) Are all the subtasks 1-5 of TA3 solved? - Vidar

5 9

Edit DB renamed to Seed DB, needs test and merge
by Stein Magnus Jodal 04 Sep '08

04 Sep '08

Hi, I've just spent an hour on renaming editdb to seeddb, as described in the https://blueprints.launchpad.net/nav/+spec/rename-editdb blueprint. The code is now running at navdev and is available at navdev:~jodal/nav/jodal/rename-editdb. 1) Morten and Vidar: could you please poke around at navdev a bit to test that everything seems okay? 2) Morten: could you please merge the branch or give me a green signal for merging before other branches diverges too much? I've changed code in large parts of NAV (including the infamous nav.django.urls) to accomplish the renaming, and would very much like to win the merge war by merging first ;-) Upgrade instructions are included at the blueprint status whiteboard. -- Stein Magnus Jodal UNINETT

3 2

Introduction to using Django with NAV
by stein.magnus.jodal＠uninett.no 28 Aug '08

28 Aug '08

Hi, I have just completed a first draft of the NAV+Django introduction, available at [1]. I know some of you would for sure had benefit of having this documentation available in June. I'm sorry about that, but now it's finally here. I would very much appreciate if those of you which have been using Django in NAV or elsewhere could take the time to read through the introduction and give some feedback. Both general feedback here at the mailing list and changes directly in the wiki are welcome, especially with regards to the future enhancements section. Hope the docs will be useful to some :-) [1] http://metanav.uninett.no/devel:django_introduction -- Stein Magnus Jodal UNINETT AS

5 4

Bugtracker moved from Sourceforge to Launchpad
by Kristian Klette 19 Aug '08

19 Aug '08

Hi all NAVers! Our new bugtracker is located at http://bugs.launchpad.net/nav All of the bugs that were reported on Sourceforge was imported, so all the data should be there. To simplefy bug-reporting for developers and other console-junkies, the nav-tip[0] now has a small tool called nav_bug.py in the contrib folder. Add this tool to your path and run nav_bug.py --help for more info about how to use the tool. I hope you all will enjoy using a more up-to-date bugtracker, and help us making NAV even better! - Kristian Klette [0]: http://metanav.uninett.no/hg/default -- Mvh Kristian Klette «Programs for sale: Fast, Reliable, Cheap: choose two.»

1 0

Status meeting minutes, 4 August 2008
by Jørgen Abrahamsen 05 Aug '08

05 Aug '08

Status meeting minutes, 4 August 2008 ===================================== This week a lot of people are having vacation. So there is only Jørgen and Thomas attending this status meeting. Thomas ------ * Nothing to add as he was on vacation last week. Jørgen ------ * Continued work on storing report results in session. * Fixed release bug SF#2031154 (Report pages load unnormally slow) -- Jørgen Abrahamsen UNINETT

1 0

Status meeting minutes, 28 July 2008
by Morten Brekkevold 28 Jul '08

28 Jul '08

Status meeting minutes, 28 July 2008 ==================================== Morten ------ * Wrote a simple script to check SQL scripts when they are updated in the default branch. * Thomas proposed a different solution, using buildbot, which looks a lot better :-) * Testing latest netmap changes, alertprofiles and alertengine, feedback to developers. * Cleaned up and merged db-namespaces branch on default. * Resumed development on ipdevpoll. * Looking at Twisted's adbapi (asynchronous db api) * Looking at how Twisted can be used for scheduling jobs. * Looking at strategies for repeated loading of changed model data from database into cache. * Teknobyen-vk's old hardware is ready for reuse as new navdevdb, needs Debian reinstall. Thomas ------ * Useradmin as good as done. Userinfo merged into the new tool. (need to test) * Been looking at buildbot. * Fixing loose ends in code produced so far this summer. * testmaker is a possibly interesting tool for us. * Uses web logs to record replayable unit tests for web interfaces. * Still in development. Jørgen ------ * Been on vacation. * Overloading report config with local reports now works * Testing new code. * Working on caching reults of report SQL queries in user sessions * This requested feature will simplify the sum functions Jørgen is * Shelve extension disappeard with Mercurial upgrade, which caused problems. Magnus ------ * System for storing messages in NAV sessions now works. * MySMS merged into new alertprofiles. * Fixed permissions bugs and some usability fixes. * Been on two days vacation. * Feedback: Test database migration paths from 3.4 for alert profiles. Kristian -------- * Still working on Netmap and Network Explorer. * Only admins can save netmap layout. * LP migration news: Imports from SF.net to LP's test box are now complete. * Wrote script to report NAV bugs to LP from console. * Fixed DEBUG-setting in Django and 500.html-page. -- mvh Morten Brekkevold UNINETT

1 0

Status meeting minutes, 21 July 2008
by Morten Brekkevold 28 Jul '08

28 Jul '08

Seems I forgot to send this out last week, here it goes: Status meeting minutes, 21 July 2008 ==================================== Morten ------ * Released 3.4.1 on Tuesday. * Researched some more of NTNU's previously reported problems, found one of them to be another result of the HP ifindex mangling. * Posted about cherrypicking vs. stable/unstable branches * Found a simpler way to retain a single head in the series repositories. * Found some manage.sql bugs while testing Werner's latest package. * Looks like a 3.4.2 is imminent. * Should look into automatic testing of sql scripts on commits. * Been trying out Mercurial's API (Python) to log stats for repositories found locally at navdev. Magnus ------ * Everything's in place in Alert Profiles. * Authorization checks added several places. * Messages system for web sessions. Thomas ------ * Fixed quickselect bugs. * Jabber alerts seems to be working fine. * Making sure we have robustness, plugins should not be able to bring down the alert daemon. * Useradmin replacement well on the way. * ETA today or tomorrow. * Delete restriction for uids/gids < 1000. * Django Account models have checkPassword and setPassword methods now (copied from forgetSQL "models"). Kristian -------- * Network explorer * Trying to reduce number of small requests * Big requests may appear slow, causing Firefox to issue Javascript warnings. * Launchpad migration: * Belated, Launchpad released a new version last week, which caused a delay. * Test import of NAV's sf.net data mostly successful. * Working on "save layout" feature for Netmap. Discussion ---------- Adamcik: Django 1.0 possibly in september. Will NAV 3.5 come out before or after this time? Feedback: As long as Django 1.0 is backwards compatible with the SVN revision we currently use, everything should be in order. Assigned tasks: Kristian will make a 500.html template, and add new options in nav.conf to control Django's DEBUG and TIMEZONE settings. -- mvh Morten Brekkevold UNINETT

1 0

Bugfixing on stable vs. unstable branches
by Morten Brekkevold 18 Jul '08

18 Jul '08

The recent release of 3.4.1 gave me some more practical experience with using Mercurial for cherrypicking bugfixes, and I've found I want to do things slightly different than we do today. Cherrypicking changesets is done with the transplant extension. I've never been 100% comfortable with this, as I feel it circumvents Mercurial's fine merging capabilites. It gives me slightly the same feeling as merging bugfixes with Subversion did, the only improvement being that each changeset is transplanted separately instead of being mashed together in one big changeset. With transplanted changesets in the series-branches, we cannot easily compare the contents of the series-branches with the default branch, using commands such as 'hg in' or 'hg out'. Really, the only reason I have to do cherrypicking is because we fix bugs on the unstable default branch. I can't very well pull the default branch into any of the series-repositories, as they're supposed to be stable, so I have to pick single bugfix changesets from the default branch and transplant them. If we look at things the other way around, anything that goes into the stable series-branches should also go into the default branch (except for version bumping and tags, see my side note below). If bugfixes are committed to the latest series-branch instead of the default branch, the series-branch can easily be pulled and merged into the default branch, and no transplants need to take place. Conclusion ---------- Starting from series/3.5.x (whenever it is branched from default), I would like everyone to commit bugfixes for stable code directly to this branch. I'm the only one with push access to these branches on MetaNAV, since I'm the only one working as a release technician at the moment, so I will need to know when and where to pull your bugfixes from. The series/3.4.x branch is already a mix of directly committed bugfixes and transplanted bugfixes, which complicates committing bugfixes to this branch (you need to checkout the latest bugfix revision and commit your changes as a child node to that changeset, then merge the whole thing with the last head). This is why I won't start requiring this method of bugfixing until 3.5.x is on its way and this can be done more consistently. Side note --------- For those of you who haven't looked at the series-repositories, please be aware of the specifics of how I tag a new release version on these. I'll use the 3.4.x branch as my example. When I'm satisified that the latest changeset (A) on the 3.4.x branch is ready to become the 3.4.1 release, I change the version number in the file VERSION to 3.4.1 and commit it (changeset B). I then tag changeset B as "3.4.1". The tag changeset itself becomes changeset C. When committing bugfixes and other changes for a later 3.4.2 version, I check out changeset A again, and base my changes on this. This is because I don't want the VERSION file in the following changesets to say "3.4.1", but rather "3.4.x_devel", as it did in changeset A. Also, I don't want to pull the changesets that changed the VERSION file into the default branch at a later time. This may seem a bit contrived, and it leads to having multiple heads in any series-branch, but so far I haven't thought of a more useful way of updating the VERSION file without changing it back and forth all the time. -- mvh Morten Brekkevold UNINETT

1 1

Status meeting minutes, 15 July 2008
by Morten Brekkevold 16 Jul '08

16 Jul '08

Status meeting minutes, 15 July 2008 ==================================== Morten ------ * Mailing list activity. * Several bugfixes on series/3.4.x. * Transplanted Magnus' alertprofiles (php) fix branch onto series/3.4.x w/simple tests and merge. * 3.4.1 candidate in testing, should be released later today. Kristian -------- * Still waiting for launchpad admins to migrate NAV project from SourceForge to Launcphad. * Launchpad admins will run a test import to demo.launchpad.net within the next couple of days. * Unknown users from SourceForge data will be mapped to inactive users on Launchpad, which can be activated later. * Working on Netmap improvements * Basic support for saving layouts is ready. Thomas ------ * Found and fixed several small bugs in time for 3.4.1 release: * PostgreSQL 8.3 stricter typecasting * Errors in web pages. * Idea for system to automatically crawl the dev server web pages and report 404/500 errors. * Quickselect, the Treeselect replacement is finished. * Created a branch for some generic CSS/HTML-fixes, pushable to default branch. * Found an improved and currently maintained fork of the Jabber library used in the AlertEngine Jabber plugin. * Trying to test what happens when a Jabber host goes down. Magnus ------ * Still working on alertprofiles in Django. * Most functions finished. * Working on profile creation. * Need to do code cleanup and make more user friendly interface. Jørgen, Vidar and John-Magne are currently on vacation. -- mvh Morten Brekkevold UNINETT

1 0

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Nav-dev