Hi Dan, On 03.06.2014 [09:26:49 -0700], Dan Alvarez wrote: > Hi Nishanth, > > Thanks for the response. Inline... [DA] > > On Tue, Jun 3, 2014 at 9:14 AM, Nishanth Aravamudan <[email protected] > > wrote: > > > Hi Dan, > > > > On 29.05.2014 [15:57:56 -0700], Dan Alvarez wrote: > > > I read through the thread back in 2012, but it didn't look to have > > resulted > > > in a final conclusion. I'm happily using cobbler to set up my DHCP and > > > DNS for the cluster. It all works fine for my regular ports, but I'm > > also > > > using provisioning through cobbler for my ipmi interfaces (DHCP and DNS) > > > but I loose my DHCP leases on those after some time. > > > > I'm not sure why there is a difference between the two, but... > > > > [DA] I'm pretty sure it is because the ipmi interface rely on DHCP > still being there after the initial lease expires. The configuration > learned from DHCP is not persisted in linux for the ipmi interfaces. > You could argue that I could provision ipmi separately, but I'm hooked > on cobbler and would like to keep all my provisioning in one place.
Ok, that makes sense. > > > Why don't the dhcp entries persist even with netboot-enabled set to > > False? > > > Is there a way to force the dhcp entries for an interface to be > > persistent? > > > > Upstream has commited an option "always_write_dhcp_entries" for exactly > > this purpose. > > > > [DA] Do you know what version of cobbler I need to pick up for this? > Thanks It only was merged in April of this year, so I'm not sure it's in any release. -Nish _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
