NAME

App::Netdisco::Manual::ReleaseNotes - Release Notes

Introduction

This document will list only the most significant changes with each release of Netdisco. You are STRONGLY recommended to read this document each time you install and upgrade. Also see the Changes file, for more information.

Migrating from Netdisco 1.x

This distribution (App::Netdisco) is a complete rewrite of the Netdisco application. Users often ask whether they can run both versions at the same time, and whether the database must be copied. Here are the guidelines for migrating from Netdisco 1.x:

  • You can run both Netdisco 1.x and App::Netdisco web frontends at the same time, using the same database.

  • Only enable the backend daemon and discovery jobs from either Netdisco 1.x or App::Netdisco.

  • You can share a single database between Netdisco 1.x and App::Netdisco. The deploy script for App::Netdisco will make some schema changes to the database, but they are backwards compatible.

2.017000

General Notices

There is a bug in Macsuck whereby in rare circumstances some invalid SQL is generated. The root cause is known but we want to take more time to get the fix right. It should only be a few more days.

The no_port_control configuration setting is now called check_userlog and its logic is inverted. Don't worry if this is not familiar to you - the option is only used by Netdisco Developers.

2.016000

General Notices

The dangerous action log messages are now saved to the database. In a future version there will be a way to display them in the web interface.

2.015000

Heath Advice

Some of the "dangerous action" confirmation dialogs offer to take a log message (e.g. Port Control, Device Delete). Currently the log messages are not saved. This feature will be added in the next release.

2.014000

General Notices

The backend poller daemon is now considered stable. You can uncomment the housekeeping section of the example configuration and thereby enable regular device (re-)discovery, arpnip and macsuck.

2.013000

General Notices

You can now configure LDAP authentication for users.

2.012000

Security Notices

The read-write SNMP community is now stored in the database, when used for the first time on a device. If you don't want the web frontend to be able to access this, you need to:

  • Have separate deployment.yml files for web frontend and daemon, such that only the daemon config contains any community strings.

  • Use separate PostgreSQL users for web frontend and daemon, such that the web frontend user cannot SELECT from the community DB table.

2.011000

General Notices

Users can be managed through the web interface (by admins only).

2.010000

General Notices

You can now simplify database configuration to just the following, instead of the more verbose plugins/DBIC setting which was there before:

 database:
   name: 'netdisco'
   host: 'localhost'
   user: 'someuser'
   pass: 'somepass'

Also, the REMOTE_USER environment variable and X-REMOTE_USER HTTP Header are now supported for delegating authentication to another web server. See the Deployment and Configuration documentation for further details.

2.008000

Heath Advice

This release contains the first version of our new poller, which handles device and node discovery. Please make sure to backup any existing Netdisco database before trying it out.

General Notices

You can remove any settings from ~/environments/deployment.yml which you didn't edit or add to the file yourself. All defaults are now properly embedded within the application. See the new deployment.yml sample which ships with this distribution for an example.

2.006000

Incompatible Changes

The default environment configuration file develpment.yml has been renamed to deployment.yml. This better reflects that users are not developers, and also fits with the default for PSGI compatible cloud deployment services.

Please rename or copy your environment file:

 mv ~/environments/development.yml ~/environments/deployment.yml

General Notices

The installation is now relocateable outside of a user's home directory by setting the NETDISCO_HOME environment variable. This defaults to your own home directory.