NAV Wiki - devel:blueprints

autodiscovery-wizard

Anonymous (anonymous@undisclosed.example.com) — 2011-04-05T14:07:25+00:00

Autodiscovery wizard for NAV Specification for blueprint: Overview It would be nice if NAV could offer an autodiscovery feature to make it even easier to maintain the IP devices you want NAV to monitor. We suggest this is added to the seed database tool.

consolidated-interface-table

Anonymous (anonymous@undisclosed.example.com) — 2009-03-19T13:26:40+00:00

Rationale NAV has for many years had an artifical divide between switch ports and router interfaces, which are stored in each their table (swport and gwport). Conceptually, they are all just network interfaces, which share a set of attributes. On routers, interfaces can also operate on the IP layer, which adds some attributes.

dhcp-checker

Anonymous (anonymous@undisclosed.example.com) — 2010-05-21T12:22:49+00:00

DHCP checker for Servicemon A new DCHP service checker for NAV. Status The checker is written and has been in service at UiTø since 10. May 2010. Arguments The checker takes one optional argument: timeout (in seconds). Inner workings The DHCP checker uses

django_template

Anonymous (anonymous@undisclosed.example.com) — 2010-01-13T12:16:57+00:00

Django templates in NAV In the future NAV should mainly use Django templates, falling back to cheetah on old subsystems. Django systems In the lib-python directory there's a base template, simply called base.html. Subsystems should extend this one (probably with their own base.html) and the base_content block in it.

external-portinfo-link

Anonymous (anonymous@undisclosed.example.com) — 2010-07-09T07:49:09+00:00

Configurable links to external information about ports Link to Launchpad blueprint The simplest way to implement this would likely be to use Django templates. ipdevinfo should have its own config directory under @sysconfdir@/ipdevinfo which should be added to the list of directories where Django searches for templates. ipdevinfo's port view template could include this template at the bottom of the page.

ipdevpoll

Anonymous (anonymous@undisclosed.example.com) — 2012-05-07T11:26:28+00:00

ipdevpoll design specification This page is currently being updated to match whats being developed. Dont trust this stuff just yet :-) Introduction ipdevpoll is the planned replacement for getDeviceData, becoming the third generation SNMP polling framework for NAV. This page will lay out the various design ideas and specifications for the new program.

mailin

Anonymous (anonymous@undisclosed.example.com) — 2009-02-02T12:08:35+00:00

MailIn design specification Introduction Andreas Solberg once wrote a piece of software called MailIn, written in Perl, to parse incoming email from third party monitoring systems and to translate them into NAV events. We would to like to include such a system as part of NAV, but since we do have a long term goal of reducing the number of used programming languages, we would like this to be reimplemented as a Python program. This would enable it to make use of the common Python

pping-ipv6

Anonymous (anonymous@undisclosed.example.com) — 2011-06-14T12:58:56+00:00

Enable IPv6 in pping Specification for blueprint: Overview NAV supports collecting information about IPv6 addresses and prefixes, but does not yet support communication over IPv6. A first step to make NAV more IPv6-compatible would be to enable ICMPv6 ECHO requests in the pping daemon.

refactor-mod-python-to-django

Anonymous (anonymous@undisclosed.example.com) — 2012-10-03T08:29:40+00:00

Specification: Refactor mod_python based web apps to Django based The mod_python project is dead, its recommended successor is mod_wsgi. Much of the legacy web apps in NAV interface directly with the mod_python API at a low level. These systems should all be refactored to be served through Django instead, so we can be independent of the actual low-lever web server technology being used. A separate blueprint for each mod…

servicemon-spring-cleaning

Anonymous (anonymous@undisclosed.example.com) — 2010-06-09T11:09:42+00:00

Servicemon This is more of a todo-list than a blueprint. Todo * make .descr parser a little more robust (it doesn't handle empty arguments (like 'args=') * fix version checking in DNS checker * write a new checkservice? * update copyright notices and encodings for library

servicemon-tool

Anonymous (anonymous@undisclosed.example.com) — 2010-05-20T11:23:28+00:00

Make Servicemon a Tool Servicemon is currently hidden away inside SeedDB. Now that a rewrite of SeedDB is being considered, this is a good time to take Servicemon out and make it a separate tool with its own web interface. This will make it more visible to users. The code should also become easier to work with, since it's no longer tied to the rest of SeedDB.

smsd-retry-backoff

Anonymous (anonymous@undisclosed.example.com) — 2009-06-08T12:01:57+00:00

SMSD retry backoff on full dispatch failure (specification) Introduction When all dispatchers fail to dispatch an SMS, smsd will retry at the next queue read (which implies a 30 second delay, using default values). A total dispatch failure is a CRITICAL level error, and the loghandler will notify the NAV admin via e-mail.

unified_source

Anonymous (anonymous@undisclosed.example.com) — 2010-07-18T15:18:49+00:00

Blueprint at launchpad Unified Source layout This is a blueprint on how to make the source-tree of NAV a bit less complex, and how to make it easier to develop in an local matter (no more “sudo make install”) Todays layout Out current source code tree is heavily influenced by the fact that NAV started out by using a number of different programming languages. This made the installation dependent on numerous Makefiles for handling each subsytem to their needs.