Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Question on discover_waps (Oliver Gorwits)
2. Netdisco db timezone on shared instance (Roberto Martinez)
--- Begin Message ---
Hi Roberto
Good question! OK so the "queued" status jobs are not started -- they are
just entries in the queue in the database.
Netdisco has a process to select the jobs to run, and the backend will
ignore entries in the queue which it is not permitted to run for any reason.
The subtlety here is that you can have multiple different backend daemons
with different config running. For example, it's possible some users want
some backends to discover the WAPs and others not.
So Netdisco is written to allow the jobs to be queued, they are quite
harmless to sit there (and they are removed after a while by the Expiry job
I think, but would be re-added of course).
Your single backend daemon with this config will ignore the jobs in, I
hope, a fairly efficient way (it should not keep trying to run them, they
are ignored).
Hope that helps!
regards,
oliver.
On Mon, 21 Mar 2022 at 09:33, Roberto Martinez <robert...@gmail.com> wrote:
> Hi,
>
> I have a question related to the discover_waps feature. In our
> installation we have set discover_waps=False as we do not want the APs to
> be discovered. We also have set up the wap_platforms with a regex matching
> the waps (all cisco AIR, so the default regex included as example works),
> and we have checked that the regex matches the ap string (the wireless icon
> is shown on the device).
> However, we're seeing a Discover job started (but not finished) on all
> these devices, job that stays in "queued" status. "netdisco-do dumpconfig"
> also shows that the settings have been correctly taken into account
> (discover_waps and wap_platforms), but "netdisco-do show -d <ip> -e
> c_platform" says "Don't know device: <ip>" (which I guess is ok because
> after all, we told NetDisco not to discover them)
>
> The question is: should NetDisco start these jobs and let them in queued
> status, or should NetDisco NOT start these jobs as they are not supposed to
> run?
>
> Thanks
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi,
We have setup a Netdisco installation using a shared postgresql instance.
We would like to set the timezone specifically for the Netdisco DB and not
all the databases of the instance, so it looks like the only way to do this
is to issue a "SET TIMEZONE='<timezone>' upon the connection to the
database. AFAIK there's no setting in the deployment.yaml file to specify
"sql commands to run when netdisco connects", and the way to externally set
the timezone would be touching postgresql.conf and restart the instance,
which affects all the databases on the instance and not only that of
Netdisco.
Do you have any hints on how this could be done?
Thanks in advance
Roberto
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
