[Feature Request] Add physical nodes within the topology

[jean-christophe-manciot]

@stephenguppy @grossmj @noplay This proposal can be a game changer if it is implemented: it would very significantly broaden GNS3 uses cases.

At least, the following node properties could be defined:

• local name: the one inside the topology
• remote name: the one allowing GNS3 to contact the remote node
  • IPv4/IPv6 addresses
  • or FQDN
• symbol
• console type:
  • telnet
  • vnc
  • spice?
  • ssh
• custom commands: allow the user to launch any kind of local command towards that node:
  • ansible playbook
  • REST API call
  • ...
• GNS3 API: new physical node type in:
  • create node
  • link node
  • change node properties
  • launch command for that node
  • delete node

Of course:

• all the node properties related to the virtual nodes need to be removed from the physical nodes definition templates.
• at least one cloud node should be required to connect the virtual nodes to the physical ones.
• some actions available through the "right-click" menu for the virtual nodes are not directly available anymore, although they could be defined via a REST API for instance depending on the physical node type:
  • start the node
  • suspend the node
  • stop the node
  • reload the node
• ...

[grossmj]

Indeed a good idea, thanks :)

[grossmj]

This has been partially implement by https://github.com/GNS3/gns3-gui/issues/2500