In your template file include a secondary file for non cobbler controlled static entries. Dhcpd wi pick them just like they were in the main file.
On Sep 10, 2010 10:12 AM, "Byron Pezan" <[email protected]> wrote: > you could manually, or via a script, insert the appropriate entries into /etc/cobbler/dhcp.template followed by a `cobbler sync`. in my case i have a dummy profile, i call it "legacy" that is tied to a specific DHCP tag. i use this profile for all systems that were not provisioned by cobbler in addition to network devices that require IP addresses. the distro to which this profile is tied has no real bearing since i control the PXE boot directives based on the DHCP tag and customizations in the dhcp.template file. the custom DHCP tag not only allows me to identify "legacy" systems in the dhcpd.conf file (or anything else that can be accomplish through the use of "groups" in DHCPD. it also allows me to point these systems to a different "next-server" or none at all, which can also be used to prevent network devices and such from hurting themselves, if they can PXE boot. i would be happy to provide you with the dhcp.template that i'm currently using to accomplish this. > > you might want to read: > https://fedorahosted.org/cobbler/wiki/ManageDhcp (for basic understanding of how cobbler manages DHCP, if you haven't already.) > > this will lead to: > https://fedorahosted.org/cobbler/wiki/KickstartTemplating (covers the basics of templating used in kickstarts, snippets and templates.) > > which further leads to: > https://fedorahosted.org/cobbler/wiki/KickstartSnippets (which applies to template files as well as kickstart files. i found that reading through the supplied snippets in /var/lib/cobbler/snippets to be very helpful in this regard.) > > in order to really leverage this feature understanding python is helpful: > http://wiki.python.org/moin/BeginnersGuide (since templating effectively allows you to imbed python code/logic into your configs.) > > if you really want to go down the rabbit hole: > http://cheetahtemplate.org/learn.html (details the underlying pieces used by cobbler for it's templating functionality. probably more detail than you'll need to accomplish your task, but a good reference none the less.) > > HTH > > > byron > > -----Original Message----- > From: [email protected] [mailto: [email protected]] On Behalf Of McEvoy, James > Sent: Thursday, September 09, 2010 5:11 PM > To: cobbler mailing list > Subject: DHCP Entries for HP iLO ports > > Is there a preferred way to add MAC address for HP iLO ports to cobbler to create DHCP entries? I stared using a dummy image file for the system entries as follows; but thought there might be a better way. > > ssh cobbler "cobbler system add --name=myhost-ilo --mac=00:00:00:00:00 --hostname=myhost-ilo.example.com --image=dummy.img --netboot-enabled=N" > > I cannot just add another mac to the system definition with its associated IP because I only have control of the DHCP server and hostnames and have to rely on IT controlled DNS to assign the IP addresses. > > --jim > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
