-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Allow creating isolated OVN networks (no uplink) #936
Comments
Hey @stgraber, I'm really interested in delving into |
Done! |
Hey @stgraber, sorry to bother you at this moment. I've read the source code for this issue and have a few questions I'd like to make a confirmation with you.
incus/internal/server/network/driver_ovn.go Line 1888 in 0d9855e
|
So the initial steps probably should be:
I think that's about it for what I'm seeing in the OVN driver code. |
@stgraber |
Hey @stgraber sorry to bother you again. I've tried to implement this feature, which creates isolated OVN networks (no uplink), but I've encountered additional problems. After creating the isolated OVN networks using this command and assigning them to the instance, I noticed that upon starting, the instance does not receive IPv4 or IPv6 addresses. This issue appears to be due to a method returning an empty slice. incus/internal/server/network/driver_ovn.go Line 2371 in b0f1040
Another issue occurs when I try to delete isolated networks (those without an uplink), which results in an "object not found" error. I am still debugging this problem. I would like to hear your advice. 🙇🏻♂️ I am very interested in the incus project and hope to thoroughly read and understand the source code. I hope you don't mind my weak computer science background. 🙇🏻♂️ |
This came up in https://discuss.linuxcontainers.org/t/isolated-ovn-network/20167/6
While there are workarounds, it'd probably make sense to just support creating an OVN network with no
parent
, likely by introducing a special value ofnone
(and consequently preventing a managed network be namednone
).The text was updated successfully, but these errors were encountered: