Now that Shake has brought this up, I could see it negatively
affecting my environment (if anyone aside from me used koan....). So
rather than just throwing out an idea this time (of which I have one,
its just not great) I figured I'd lay out a bit more thought into the
environments and workflows. Please augment the lists below, as I know
I won't be thinking of everything.
So there are two basic environments and several workflows at play here:
1: Platforms that do not support normal boots if a PXE environment is
available via DHCP/BOOTP at boot time
2: Platforms that do support normal boots if a PXE environment is
available via DHCP/BOOTP at boot time
Then the various workflows (please add any additionals):
1: DHCP Only Environment with PXE boot as primary boot
a. pxe_just_once enabled so that post boot cobbler will not
provide pxe information in dhcp/bootp request.
b. koan re-installs work because DHCP is still available, and koan
provided the other necessary bits (kernel config, initrd, etc)
2: DHCP Only Environment with PXE boot secondary to local boot:
a. pxe_just_once disabled as only manual intervention via koan or
boot menu will open system to DHCP requests again
b. koan re-installs work because DHCP is still avilable, and koan
provided the other necessary bits (kernel config, initrd, etc)
3: Static environment with DHCP available for building, PXE boot as primary boot
a. pxe_just_once enabled so that post boot cobbler will not
provide pxe information in dhcp/bootp request.
b. static enabled, which when combined with pxe_just_once enabled
this disabled netboot_enabled, leading to no dhcp/bootp availability
for the system
c. koan initiated re-installs do not receive any DHCP information
without manually enabling netboot_enabled=1
4: Static environment with DHCP available for building, PXE boot
secondary to local boot
a. pxe_just_once disabled as only manual intervention via koan or
boot menu will open system to DHCP requests again
b. static enabled, but with pxe_just_once disabled this should not
affect DHCP availability
b. koan re-installs work because DHCP can still be available, and
koan provided the other necessary bits (kernel config, initrd, etc)
any other primary workflows that would be good to add to this discussion?
-greg
On Wed, Aug 8, 2012 at 3:44 AM, Shake Chen <shake.chen(a)gmail.com> wrote:
thanks, I got it.
whether is possible provide a option for dhcp entries.
even I set the interface to static, would not delete the dhcp entries. just
because the koan.
On Wed, Aug 8, 2012 at 11:00 AM, James Cammarata <jimi(a)sngx.net> wrote:
>
> On Tue, Aug 7, 2012 at 8:13 PM, Shake Chen <shake.chen(a)gmail.com> wrote:
> > Hi
> >
> > Now in cobbler 2.3.2, only netboot_enable = true, would add the dhcp
> > entries. when the client finish instanlled , the netboot_enabled would
> > change to 0, also would delete the dhcp entries.
> >
> > but when the client plan to use koan
> >
> > koan --server=10.1.199.12 --replace-self --system=node15
> >
> > the install can not finish, just because can not get the IP address.
>
> $ cobbler system edit --name=node15 --netboot-enabled=1
> $ cobbler sync
> $ koan ...
>
> If the interface is not set to static, it will not remove the DHCP entry.
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
--
Shake Chen
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler