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.
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?
I'm in version 2.4.0
Thanks
dan
Dan Alvarez dan.alvarez@xockets.com writes:
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.
Why don't the dhcp entries persist even with netboot-enabled set to False?
I'm actually curious about the inverse - why do some dhcp entries persist even with netboot-enabled set to False? It's not consistent, and it seems to have something to do with whether the host is set to bonding or not.
Is there some additional dhcp templating work that can be done to let both of us have what we want?
(I'm running 2.7.0.)
- Tim Skirvin (tskirvin@fnal.gov)
On 30.05.2014 [15:59:17 -0500], Tim Skirvin wrote:
Dan Alvarez dan.alvarez@xockets.com writes:
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.
Why don't the dhcp entries persist even with netboot-enabled set to False?
I'm actually curious about the inverse - why do some dhcp entries
persist even with netboot-enabled set to False? It's not consistent, and it seems to have something to do with whether the host is set to bonding or not.
Is there some additional dhcp templating work that can be done to
let both of us have what we want?
(I'm running 2.7.0.)
Are the interfaces in question set as "static"? Or, rather, *not* set as "static"?
Thanks, Nish
Nishanth Aravamudan nacc@linux.vnet.ibm.com writes:
Why don't the dhcp entries persist even with netboot-enabled set to False?
I'm actually curious about the inverse - why do some dhcp entries
persist even with netboot-enabled set to False? It's not consistent, and it seems to have something to do with whether the host is set to bonding or not.
Is there some additional dhcp templating work that can be done to
let both of us have what we want?
(I'm running 2.7.0.)
Are the interfaces in question set as "static"? Or, rather, *not* set as "static"?
There's no option for 'static' vs 'dynamic' on bonded devices, at least not in the web interface; so they're set as dynamic, I guess.
- Tim Skirvin (tskirvin@fnal.gov)
Tim Skirvin tskirvin@fnal.gov writes:
Are the interfaces in question set as "static"? Or, rather, *not* set as "static"?
There's no option for 'static' vs 'dynamic' on bonded devices, at
least not in the web interface; so they're set as dynamic, I guess.
I've opened an issue for this problem on the github issue tracker:
https://github.com/cobbler/cobbler/issues/985
- Tim Skirvin (tskirvin@fnal.gov)
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...
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.
Thanks, Nish
Hi Nishanth,
Thanks for the response. Inline... [DA]
On Tue, Jun 3, 2014 at 9:14 AM, Nishanth Aravamudan <nacc@linux.vnet.ibm.com
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.
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
dan
Thanks, Nish
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 <nacc@linux.vnet.ibm.com
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
Short reply: that feature got merged in to 2.6.0, see cobbler manual section release notes.
Cheers Op 3 jun. 2014 18:51 schreef "Nishanth Aravamudan" <nacc@linux.vnet.ibm.com
:
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 <
nacc@linux.vnet.ibm.com
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 cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org