Hi Tory

Just a thought: have you tried cobbler web? Nice thing about the gui is it gives you an idea of the options are available for systems/profiles/distros.

I think you would need to define systems in cobbler, even if they had dhcp assigned ip addresses. Then you could define the server override that way. So at a minimum you define hostname, interface, mac address and server override. Then see what cobbler sync generates for dhcpd.conf and the tftpconfig?

--
Alastair Munro

-----Original Message-----
From: Tory M Blue <tmblue@gmail.com>
To: cobbler mailing list <cobbler@lists.fedorahosted.org>
Sent: Thu, 05 May 2016 22:39
Subject: [cobbler] Re: Multiple subnets, multiple dhcp --dhcp-tag, profiles, distro

On Thu, May 5, 2016 at 2:15 PM,  <alastair@alastair-munro.com> wrote:
> Hi Tory
>
> We now use vrealize in vmware to automate the build of vm's. However behind
> the scenes it uses cobbler and creates a system in cobbler to build each vm,
> even though pxe is used to build the vm. Once the vm is built the system
> definition is removed from cobbler. The vm always has a static ip even
> though they are pxe built.
>
> In my 25 years or so of being a sysadmin i have not come across anyone using
> dhcp for servers to get their ip (exception being cloud environments such as
> Azure where the infrastructure controls ip allocation). Thus it makes sense
> for servers to use static ip's even if the build uses pxe (dhcp/tftp). For
> example if the server cannot get its ip then its not available.
>
> Just my tuppence worth. You dont need to follow my advice, but a wise man
> once said dont make the mistakes yourself but learn from others mistakes.
>
> --
> Alastair Munro

Yes sir, currently I'm rebuilding systems, migrating from CentOS6 to
CentOS7 in a production environment. So instead of playing with DNS,
I'm building the system as the replacement system in place. I then
shut down the current system and bring up the new one, so the DHCP
makes sense in this regard. Obviously I could use a throw away static
but really that seems like an unnecessary hurdle.

And remember my issue is not with an IP, it's with cobbler using a
hardcoded http_server and next_server, when it could easily take the
next_server from the DHCP profile (for my use anyways).

Again I appreciate the continued support and ideas.

I'm not discounting anything. I have it working, but it's not how I
see it working. I still think there is something I fundamentally am
not wrapping my head around, or a fundamental flaw in how cobbler
approaches multi network environments.  Because I'm stubborn,  I'm not
happy that it's working, since I had to do some network tricks to
allow it to work. (everything talking to 13.5 interface for the
kickstart process).

I really thought I was on to something using the if/else clauses in
the kickstart file, but Cheetah/Python are now giving me the big
finger :)  But there is a way, I am just floundering at this point!!

Thanks again
Tory
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cobbler@lists.fedorahosted.org