ConvoyPanel
IPAM + VM Configuration
Is there an existing feature request for this?
- [X] I have searched the existing issues before opening this feature request.
Describe the feature you would like to see.
Support for IP's over DHCP (MAC address), MTU setting for VM's.
Describe the solution you'd like.
Convoy doesn't support IP's over MAC address from DHCP network also if someone is tunnelling his IP's he might have lower MTU than 1500 but Convoy overwrites this even VM template has all this setup correctly.
Additional context to this request.
No response
I can make it so that Convoy doesn't override configuration, but you're going to have to elaborate about support for IPs over DHCP. It's not clear whether it is possible through Proxmox's API to do this.
I think adding option MTU while adding node would be great and when it's empty it will use default value 1500.
And here's the option I talked about:
-
First is "Bandwidth limit" which is rate in PVE
-
Second is "MTU" which convoy overwrite by default and I had to manually change the code. ^ Screenshot above
-
Third is "Setting only MAC address on IPAM". Currently we need to provide: IP, GW, CIDR which we can replace by MAC addresses with DHCP. And this is because Netplan on Ubuntu doesn't like gateways outside the subnet of allocated IP, for example: 1.2.3.4/32 and gw: 4.3.2.1. Maybe there should be and DHCP option with -- input MAC address
Also I found this:
Which can be located at PVE API: https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu POST
Should MTU be set depending on the network interface or should all VMs in a node have the same MTU? I'm looking for what's the best way to implement this.
But convoy should not override if something custom is set already in proxmox.
But convoy should not override if something custom is set already in proxmox.
Well that would be a bit hard to tell if a value was set by a user or was supposed to be overridden.
You could set it during installation, and not override every few seconds (not like the network speed thing)
You could set it during installation, and not override every few seconds (not like the network speed thing)
The rate limiter currently only sets the network speed in the latest release.
I don't think my question about the technical implementation of DHCP was clarified. Please provide this information for discussion to continue
I'm not sure what needs to be implemented, so I'm closing this issue for now.
I'm not sure what needs to be implemented, so I'm closing this issue for now.
I have an use-case for this with the OVH Virtual Mac adresses. Basically, a mac address needs to be supplied for the VM network interface for the VM to be able to acquire the public IP address.
Can you check if that would be possible @ericwang401 ?
I'm not sure what needs to be implemented, so I'm closing this issue for now.
I have an use-case for this with the OVH Virtual Mac adresses. Basically, a mac address needs to be supplied for the VM network interface for the VM to be able to acquire the public IP address.
Can you check if that would be possible @ericwang401 ?
Sorry but I do not understand you problem. As far as I can see, in ovh you assign a Mac to an ip wich then can only be used on a vm having this Mac address.
And you goal is to have the ip address assigned via dhcp.
This seems redundant. Since you want to thinks, The user seeing their ip in the dashboard, and the server having the proper Mac therefore being able to use the assigned ip.
The first option is not possible if you use dhcp. The second option you can already do.
Let's say you have ip 1.1.1.1 and assigned Mac 70:2f:4c:c2:49:e5 in ovh. So what you do is, create in convoys IPAM an ip 1.1.1.1 and give it a Mac 70:2f:4c:c2:49:e5.
Regarding MTU, currently convoy only overrides the mtu on creation and sets it empty. meaning the mtg form the bridge is being used:
Force MTU of network device (VirtIO only). Setting to 1 or empty will use the bridge MTU https://pve.proxmox.com/wiki/Manual:_qm.conf
The first option is not possible if you use dhcp. The second option you can already do.
Let's say you have ip 1.1.1.1 and assigned Mac 70:2f:4c:c2:49:e5 in ovh. So what you do is, create in convoys IPAM an ip 1.1.1.1 and give it a Mac 70:2f:4c:c2:49:e5.
Glad to see that is already possible, thanks. I'm still pondering and wanted to check if it is already possible. "acquire" wasn't the correct word here as OVH doesn't provide DHCP anyways.
Thanks for clearing that up!