Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exceptions for sync_vm_dummy_interfaces #367

Open
Azmodeszer opened this issue Feb 12, 2024 · 6 comments
Open

Exceptions for sync_vm_dummy_interfaces #367

Azmodeszer opened this issue Feb 12, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@Azmodeszer
Copy link

Azmodeszer commented Feb 12, 2024

Is there a way to specify VM/hostname-based exceptions for skipping the virtual interface import? Right now, as far as I can see, the sync_vm_dummy_interfaces option is all or nothing, but we have a few cases where it would be desirable for the virtual interface to show up in Netbox.

@bb-Ricardo
Copy link
Owner

Hey,

Can you give me some examples? Adding a filter option or changing it into one seems doable.

@Azmodeszer
Copy link
Author

We have a couple of virtual DNS servers sharing a pair of (public) anycast IPs for loadbalancing. For each server these two IPs are assigned to dummy interfaces inside the VM. With the flag set to false they are naturally excluded, but needless to say that this information would be useful to have.

@bb-Ricardo
Copy link
Owner

Mhh, not sure what to base the filer on.

This is an example from my test environment:

2024-02-13 17:21:52,339 - INFO: Created new virtual machine interface object: vNIC Dummy-0000 (abc-9-jj8fs)
2024-02-13 17:21:52,412 - INFO: Created new IP address object: 192.168.5.192/32
2024-02-13 17:21:53,092 - INFO: Created new virtual machine interface object: vNIC Dummy-0000 (abc-9-wwn46)
2024-02-13 17:21:53,167 - INFO: Created new IP address object: 192.168.244.64/32
2024-02-13 17:21:53,554 - INFO: Created new virtual machine interface object: vNIC Dummy-0000 (abc-9-sc57c)
2024-02-13 17:21:53,626 - INFO: Created new IP address object: 192.168.122.0/32

Based on the interface name?

Also have this in my example:

2024-02-13 17:23:30,376 - INFO: Created new virtual machine interface object: vNIC Dummy-ADC6 (abc_www)
2024-02-13 17:23:30,496 - INFO: Created new virtual machine interface object: vNIC Dummy-8049 (abc_www)
2024-02-13 17:23:31,503 - INFO: Created new virtual machine interface object: vNIC Dummy-94F8 (Docker-test)

What do you think?

@bb-Ricardo bb-Ricardo added the enhancement New feature or request label Feb 13, 2024
@Azmodeszer
Copy link
Author

It's only a few machines in my use case, so a whitelist of VM names would be enough for me.

@Azmodeszer
Copy link
Author

Hi. Any news here? :)

@bb-Ricardo
Copy link
Owner

I'm really sorry, this project did not get the attention it deserves lately.

Also happy to merge Pull Requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants