search

nautobot / nautobot-app-device-onboarding

Device Onboarding Plugin for Nautobot
https://docs.nautobot.com/projects/device-onboarding/en/latest/
Other
44 stars 31 forks source link

HTTP-based device auto-detection #17

Open mzbroch opened 3 years ago

mzbroch commented 3 years ago

Current Functionality

Onboarding auto-detection works only with SSH connections.

Proposed Functionality

Onboarding auto-detection works with SSH and HTTP/HTTPS (APIs) connections.

Use Case

Enhance support for Cisco Nexus and Arista eAPI based devices.

jvanderaa commented 1 year ago

Thinking on this one, maybe add an option HTTPAPI Port field, that when auto-discovery is done, that we do an or http_port or ssh_port on the NetDev Keeper to connect to the device? This way the SSH auto discovery works and then can move over to another port for the rest?

mzbroch commented 1 year ago

Thinking on this one, maybe add an option HTTPAPI Port field, that when auto-discovery is done, that we do an or http_port or ssh_port on the NetDev Keeper to connect to the device? This way the SSH auto discovery works and then can move over to another port for the rest?

I do not think we have to introduce port per protocol type.

Ports are well known and standardized:

That being said, a plugin setting would be needed to override standard list with user extra ports like 8443, 8080 etc.

For those non-ssh ports , plugin should be able to determine the remote OS platform based on the auto-discovery.