Ovirt and openstack

[ekrichbaum]

No description provided.

[gstorme]

I've tested the ovirt sync (thank you!).
It seems that VMs in the down state are not synced to netbox.
When running with DEBUG2 loglevel, I notice these:

2024-06-17 16:59:03,311 - DEBUG: Parsing oVirt VM: okd-net001
2024-06-17 16:59:03,311 - DEBUG2: Ignoring offline VM 'okd-net001' on first run

But this also occurs on every subsequent run.

[gstorme]

mac_address should be normalized, you do this for virtual machines but not for a host.
This causes a changelog entry for every host interface mac address.

[gstorme]

I've pushed some changes in a PR to fix the comments above.

[bb-Ricardo]

Sorry this is still in my backlog for review

[bb-Ricardo]

Just wondering about all the config options in config.py are all of these used and supported? I would also assume there no deprecated ones.

Can you please have a look at them?

[ekrichbaum]

There are a few caveats that maybe need a specific readme doc to note?

• Memory is not included in the openstack vmobject itself. That needs another call to another location probably.
• Flavor should probably be pulled and added as a tag potentially.
• Came across a use case in multi openstack testing where the url given is used to login and then the targets get returned and used from there. If the target doesn't match, we get an auth failure. i.e. use an ip in auth_url but the targets returned the name. As long as the hosts file or dns contains the name to the ip, this does function otherwise crashes out completely. Needs an error trap and potentially an option and function to rewrite the host portion of those URLs.

[bb-Ricardo]

Hey, have you tried out this project: https://github.com/bl4ko/netbox-ssot

It seems to support way more sources., including ovirt already.

[ekrichbaum]

it is a different take on it for sure. from a device standpoint (fortigate, palo alto, etc.) I'd have to take a look versus something like diode. For the systems, just a different method I guess.