135/netdisco
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

devices_no and devices_only settings allow global worker restriction

Browse Source
This commit is contained in:
Oliver Gorwits
2017-06-18 23:32:21 +01:00
parent 40ca29cc8c
commit 4f613ea553
7 changed files with 63 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
lib/App/Netdisco/Manual/Configuration.pod
View File

@@ -907,6 +907,26 @@ Value: Number. Default: 2.
Number of times to retry connecting to a device before giving up.
=head3 C<devices_no>
Value: Single item or list of Network Identifiers or Device Properties.
Default: Empty List.
The value will be copied into C<discover_no>, C<macsuck_no>, C<arpnip_no>, and
C<nbtstat_no>, so is a shorthand way to restrict backend workers to avoid
these device targets. See L</"ACCESS CONTROL LISTS"> for what you can use
here.
=head3 C<devices_only>
Value: Single item or list of Network Identifiers or Device Properties.
Default: Empty List.
The value will be copied into C<discover_only>, C<macsuck_only>,
C<arpnip_only>, and C<nbtstat_only>, so is a shorthand way to restrict backend
workers to only specified device targets. See L</"ACCESS CONTROL LISTS"> for
what you can use here.
=head3 C<discover_no>
Value: Single item or list of Network Identifiers or Device Properties.

8
lib/App/Netdisco/Manual/Deployment.pod
View File

@@ -37,10 +37,10 @@ A common scenario is that the network is split into security domains (or
zones) and one Netdisco poller daemon cannot see all devices.
You can run multiple pollers, as long as they all connect back to the same
PostgreSQL database. Use the C<discover_only>, C<macsuck_only>, C<arpnip_only>
configuration settings (or their C<*_no> variants) to control which devices
are "seen" by each poller. You can also include only the necessary minimum
SNMP community/authentication settings in each poller's configuration.
PostgreSQL database. Use the C<devices_only> or C<devices_no> configuration
settings to control which devices are "seen" by each poller. You can also
include only the necessary minimum SNMP community/authentication settings in
each poller's configuration.
Of course you will also need to start the web server somewhere, as well.

21
lib/App/Netdisco/Manual/ReleaseNotes.pod
View File

@@ -56,6 +56,11 @@ interface to use as a canonical (friendly) identity of a device in Netdisco.
=item *
The new settings C<devices_no> and C<devices_only> are shorthand for setting
C<discover_*>, C<macsuck_*>, C<arpnip_*>, and C<nbtstat_*> at once.
=item *
A new setting C<site_local_files> is a shorthand for confguring paths in which
to install local Perl, template, javascript, and images files for overriding
or enhancing Netdisco.
@@ -63,14 +68,9 @@ details.
=item *
Netdisco now tracks SNMP connect failures and after several attempts will no
longer try to connect to devices (default: 10). See the C<max_deferrals>
configuration setting, and the "SNMP Connect Failures" admin report.
=item *
The topology import script (C<nd-import-topology>) will now queue a "discover"
job for each new device it imports.
Netdisco now tracks SNMP connect failures and after 10 failed attempts will
pause trying to connect, for one week (see the C<max_deferrals> and
C<retry_after> settings). See also the "SNMP Connect Failures" admin report.
=item *
@@ -80,6 +80,11 @@ items or lists. ACLs now support negation and OR/AND modifier options.
=item *
The topology import script (C<nd-import-topology>) will now queue a "discover"
job for each new device it imports.
=item *
The C<netdisco-daemon> and C<netdisco-daemon-fg> scripts have
been renamed to C<netdisco-backend> and C<netdisco-backend-fg> respectively.