i have our OpenNebula networking set up to just provide a MAC address to the guest as we assign IPs via a dedicated dhcpd. I have already found out that i can easily provide information from the host back via onegate update which works great. What i did not find in the code is a callback to update the NIC information directly from the host … or i might have missed how to do it. I can add user vars with all the values but these are obviously not used as “real” network information as if they were provided via one.
Currently that’s all fine but as we plan to use the AWS api to create hosts this will pretty much break requests for external IP and so on. I know that using external dhcp is not exactly the expected usecase but if i could just do some onegate update calls from the node to fill this data everything would be fine.
Does that sound like a reasonable feature or am i alone with such a scenario?
What i did not find in the code is a callback to update the NIC
information directly from the host … or i might have missed how to do it.
I can add user vars with all the values but these are obviously not used as
“real” network information as if they were provided via one.
Otherwise, the IP information is not embedded into the NIC attribute. You
can still add it through onegate and made custom modifications to the
interface…
Currently that’s all fine but as we plan to use the AWS api to create
hosts this will pretty much break requests for external IP and so on.
AWS used a method similar to the one you desribed, but instead it is
obtained through monitoring. The interfaces react to the AWS_IP keys
I know that using external dhcp is not exactly the expected usecase but if
i could just do some onegate update calls from the node to fill this data
everything would be fine.
Does that sound like a reasonable feature or am i alone with such a
scenario?
As I said, you may try to integrate your DHCP server through the IPAM…