#14 Allow discover_no to match against partial DNS name

fixed
2014-01-11
2007-10-11
Bill Fenner
No

[From Edward Vopata]:
Is there a way to exclude a set of device based upon a
wildcard or regex hostname expression? For example,
discover_no = sep0*
or
discover_no = (sep0.*)

...

I think just excluding a device based upon a DNS lookup would be
sufficient and probably perferable. I am trying to find a quick
way to keep Netdisco from attempting to poll devices, such as IP
phones. This feature might also be used to exclude devices in
a particular DNS domain.

Discussion

  • Oliver Gorwits

    Oliver Gorwits - 2013-10-06
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-06

    Netdisco 2 will accept an FQDN in any of the conf file _no/_only/etc settings.

    No support for wildcarding though. I guess you mean, put an IP in the config file and if it resolves to something matching the regex then it "matches" as far as the ACL goes.

    Could be added easily to Netdisco 2 (App::Netdisco::Util::Device::check_no) so moving the ticket there.

     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-06

    Ticket moved from /p/netdisco/feature-requests/90/

    Can't be converted:

    • _milestone: 1.0
    • _priority: 5
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-07
    • labels: Back-End Enhancements --> Feature, Daemon
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-07
    • labels: Feature, Daemon --> Daemon, Enhancement
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09
    • summary: Allow discover_no to match against DNS name --> Allow discover_no to match against partial DNS name
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09
    • status: open --> closed
    • assigned_to: Oliver Gorwits
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09
    I believe this is already the case in Netdisco 2 :)
    
    I implemented the vendor:<regex> and model:<regex> support for *_only and *_no config items as a more simplistic <device_property>:<regex>.
    
    Which means that you can have dns:<regex> or name:<regex> right now:
    
    discover_only:
      - 'dns:.*\.example\.com'
    
    Note that the is anchored so must match the full value of the field, beginning to end.
    
     
    Last edit: Oliver Gorwits 2013-10-09
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09
    • status: closed --> open
    • assigned_to: Oliver Gorwits --> nobody
     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09

    reopened as I realised this is pre-discovery and dns:x is only available post-discovery.

     
  • Oliver Gorwits

    Oliver Gorwits - 2013-10-09
    • Status: open --> new
     
  • Oliver Gorwits

    Oliver Gorwits - 2014-01-11
    • status: new --> fixed
    • assigned_to: Oliver Gorwits
     
  • Oliver Gorwits

    Oliver Gorwits - 2014-01-11

    Implemented (rather lazily) using YAML Regexp support.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks