On 03/12/2015 05:40 PM, Jeremy Mordkoff wrote:
Is there any reason why cobbler can not manage some systems that it
provisioned via DHCP and some systems that were provisioned by another
DHCP server? It would make my transition from one cobbler server to
another much easier.
Define better "manage". Power management, for instance, is completely
independent of DHCP management.
"systems that were provisioned by another DHCP server" does not make
much sense as DHCP server does not provision a system, it only
provides network information. Reading your entire msg, I assume you
meant "provisioned by another Cobbler server" instead. If a system
was provisioned by another Cobbler server, you just need to remove it
from old server and add it to new one and then you'll be able
to reprovision it.
Maybe you want Cobbler to manage DHCP for some systems and not manage
for others? I *think* that, if you enable DHCP management in Cobbler,
create system objects for all systems, disable netboot for the ones
plugged to another DHCP servers and alter next-server attribute of those
systems in the
external DHCP servers conf files, it will work. TFTP files are currently
always written, independently of Cobbler's netboot flag.
Regards,
Alan Evangelista
_______________________________________________
cobbler mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/cobbler
