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, ub1404. 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, 2016 at 11:53 AM,  <alastair@alastair-munro.com> wrote:
> Hi
>
> We have multiple networks that we pxe boot off and have no problem with
> fixed ip addresses being passed throught. Cobbler works on the server
> override ip for each of the networks we pxe boot off, and this is passed
> through as http_server, next server, etc. i can only conclude your cobbler
> config is not setup correctly. basically you add a system, set ip settings
> AND ip for the server override, and cobbler passes the server override ip
> through to wherever its needed.
>
> --
> Alastair Munro

Thanks Alastair.

I'll repeat myself, I'm not really wanting to muck with the profiles.
I want a single profile (for each server class) that can be used from
X networks. Sure I can add server overrides and have x*3 profiles, vs
a single. This makes no sense. The DHCP has the right address in
next-server already, why cobbler can't use that value vs inserting
it's own and utilizing the "server" switch inside cobbler, is exactly
why you are creating multiple profiles, when in reality, I don't see
why you have to..

Yes it works but having to add these to duplicated profiles for each
attached network just doesn't seem like the right answer.

If it's the only answer then I guess it's not going to be a face palm.

But it seems simple enough that I just don't think anyone has ever
gotten the correct answer (many incomplete web posts, questions around
this). That's either because there really is no answer, you work
around the issue. But if DHCP has the information, why can't Cobbler
use it?

Also I'm not adding systems,  so it's not a necessary step for me, a
server is unboxed and imaged.

Thanks for the response.
Tory
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org