Allow default gateway IP assignment to VNF device via VR

[bhorvitz]

Hi all,

I'm pretty sure the answer to this question is that it can't be done, but I thought I'd ask. I have a configuration where I create an isolated guest network and deploy a VR which handles only DHCP and UserData. I then deploy a VNF appliance which is the default gateway for the subnet. Works great.

What's I'd love to do though, is when I attach the guest network to the VNF appliance is to be able to allocate the default gateway to the VNF but of course, the VR says that it's a reserved IP and we can't assign it from DHCP. Makes sense for most cases, but it would be nice to have a way to override for this particular use.

To get around this, I'm assigning a random out of the way IP to the VNF and then statically defining the gateway IP, but at scale this would be a lot easier with DHCP. Maybe if this isn't possible in the current format, it would be a nice feature request to override the default behavior for a VNF.

Thanks,
Brian

[DaanHoogland]

It sounds like a reasonable feature request @bhorvitz . It can be implemented in a few ways. I would say that a “connectivity” provider of type custom could work, but also a dedicated service definition could. I am not sure what is the most convenient or most future proof.

[bhorvitz]

Thanks, for the feedback. I guess this also tells me that I can't do this right now in any fashion, which is what I thought would be the case.

I think I read/saw somewhere (maybe on youtube?) that the VNF framework will be evolving so perhaps it's worth waiting to see where that goes rather than solving it within the current structure.