@pdonias said in Netbox Plugin Enhancements:

• Why do you have those interfaces? Could you explain your use case and why they're not visible in XO?
• Sorry, you're right, hosts are not synced for a simple reason: there is no such thing as host types in Netbox (or did we miss something?). So we only group VMs by pools (clusters) and that's it.

Those interfaces are for example wireguard interfaces or any other virtual interfaces. Obv they are not in xo because they are virtual, but in netbox they are needed because I deploy all my wireguard stuff with them.

The host thing already was answered, there are devices which you then can link to Pools.

KR
Peter

@pdonias First of all thanks for the answers.

To your questions:

• yes if I have interfaces in netbox which are not interfaces in XO, everytime I sync they get deleted
• hosts are not synced for me only Pools <> Clusters, I will check if I can find any errors
• ok yes sorry for my wording about the duplicating, didnt see #6135 before sounds good

KR
Pete

Hi All,

first of all I am pretty new to XCP-NG and Xen Orchestra, but so far I like it

Now I wanted to put some more features in the netbox plugin and I have a few questions:

• Are PR's generally welcome or do I have to follow some steps beforehand besides contribution guidlines?
• development wise
  • can I just edit "/opt/xo/xo-server/node_modules/xo-server-netbox/src/index.js" for example if I installed from source?
  • or do I have to "build" it everytime?

Regarding the Enhancements what I have in mind so far:

• ignore IP ranges ( already in the works for RFC1918 #6306 )
• don't delete existing netbox interfaces
  • virtual interfaces ( wireguard for example will otherwise be deleted every sync )
  • maybe work with tags?
• sync Hosts
• don't duplicate VMs if they were moved to other pool
  • any thoughts if this should be toggleable?

Feel free to suggest anything else

KR
Pete