Hi
i didnt say we use different profiles. we use the same profile across all subnets. we actually have 4 cobbler servers and all the slaves replicate from one master. our cobbler servers are in different data centers. each dc has one or more subnets we pxe boot on. you set the server override at the system item level and cobbler takes care of the rest. so if a host is on netA it must have server override IP x.
btw, are you using an old version of cobbler? best to get up to date if u can. appreciate this can be tricky if your cobbler is integrated into a product like satelite or katello.
regarding profiles: we only have one per major release of the os. eg el5, el6, el7, ub
1404. so thats 4 profiles that are used across rhel, centos, oracle linux and ubuntu
1404, plus all the point releases, and loads of different configs. furthermore we dont differentiate between vms and real servers. one profile works across them all. also you can use the meta ks variables to pass your requirements to the builds. so we have build=vm, build=bda, build=hadoop, build=sas94vm. these then setup different disk layouts. we also implemented the ability to turn off or on functionality using enable= or disable=. eg enable=proxy,nimsoft,uek disable=swap, vas4. these are not cobbler builtins, its just coding the templating engine. cobbler used the cheetah templating engine which allows you embed bits of python code.
its much better to have a simple build system and then have a cfg mgmt tool like puppet do all the post build config.
--
Alastair Munro
-----Original Message-----
From: Tory M Blue <tmblue@gmail.com>
To: cobbler mailing list <cobbler@lists.fedorahosted.org>
Sent: Mon, 02 May 2016 2:53
Subject: [cobbler] Re: Multiple subnets, multiple dhcp --dhcp-tag, profiles, distro
On Sun, May 1,