Hey Guys, I'd raised this concern earlier over IRC but didn't get any
reply. I am moving it to a wider audience.
We are running dhcp on the foreman-proxy, where the dhcp leases entries are
just growing over ~1000. With that size, provisioning a box (either adding
a new one or re-building existing one) take a long time, as the process
checks for all current entries one by one in dhcp leases and re-adds
subnets as well as host entries.
You tend to have a quite big broadcast domain with many c-class subnets
joined in a supernet. To my point of view there is "a lot of noise" as a
result. In most of my previous customers the delay is the result of the
obvious size.
I would suggest to snif a bit a provisioning. The goal is to check how much
time does it take for the dhcp request to "nock" on your door in comparison
to how much time does it take to answer it.
What is the load / business of your box during that time ?
On the network part of the action even spanning tree for example can
provide you a significant time of waiting.
Hey Guys, I’d raised this concern earlier over IRC but didn’t get any
reply. I am moving it to a wider audience.
We are running dhcp on the foreman-proxy, where the dhcp leases entries
are just growing over ~1000. With that size, provisioning a box (either
adding a new one or re-building existing one) take a long time, as the
process checks for all current entries one by one in dhcp leases and
re-adds subnets as well as host entries.