there's a wiki article on this subject:
https://fedorahosted.org/cobbler/wiki/MultipleCobblerServerAddresses

i'm guessing that the DNS trick mentioned is alluding to setting up a couple 
different 'views' in BIND with different A records for each subnet pointing to 
the 'next-server' value used in your DHCPD config.  even though i consider 
myself a DNS guy, i think this option is a little too convoluted for my taste.

the Cobbler solution seems cleaner to me.  basically you set the 
'server-override' config to the IP/FQDN of the cobbler/PXE/kickstart server as 
it's addressed on each VLAN/network.  this value is set either at the profile 
or system level.

if you can't accomplish your goal with either of the above, perhaps modifying 
some of the python code in 
/usr/lib/python${ver}/site-packages/cobbler(/modules) directories and or 
snippets in /var/lib/cobbler/snippets would be an option.  however, personally 
i'd save that as a last resort.

HTH


byron

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Tuesday, August 10, 2010 9:25 PM
To: [email protected]; [email protected]
Subject: Re: Cobbler on multi-segmented network.

Thank you

Ip helper is not an option and I have vlan tagging already set.  I created dhcp 
template for each subet and that's all working.   Finally I have dhcp-tag setup 
for dhcp and hosts are in correct group.

The only thing I need is a way to work with pxe and kickstart.  I am thinking 
that pxe might work with dhcp-tag but no clue how to do kickstart.  What I 
would like to see is a variable I can use for the tree in profile so that 
install tree's ip changes base on vlan tag the host is coming from.

----- Original Message -----
From: [email protected] 
<[email protected]>
To: cobbler mailing list <[email protected]>
Sent: Tue Aug 10 20:07:14 2010
Subject: Re: Cobbler on multi-segmented network.


On Tue, 10 Aug 2010 16:47:36 -0500, <[email protected]>
wrote:
> Hey
> 
> I am wondering if anybody can give me a suggestion as to which way is
> best to proceed.
> I have a server on a multi-segment network. I.E. it has a lot of VLANs
> connected to it.
> On this server I installed cobbler. What I want to do is have each
> server that needs to be installed automatically pick the right
> pxe/kickstart options.
> I am not sure if there is a way to script this, without having a profile
> for each segment. I would prefer to avoid that and have a single "if
> then" structure in a template for the pxe menu and kickstart.
> 
> Is there any variable that cobbler has an access to that I could use to
> do this? (for instance ability to read the IP of the host).

Are you using tagged vlans?  Personally, I would not set cobbler up that
way, as it becomes a maintenance headache.  If you're using Cisco hardware,
you can configure your switches to use the "ip helper" command to forward
layer 2 traffic to a layer 3 host, so you can do things like DHCP and PXE
across segments.

In your case, if you're using tagged vlans, you'll have to create a vlan
interface for every vlan you want to build things on, and configure dhcpd
networks for each of them in dhcpd.template (also add the vlan interface to
your dhcpd settings, /etc/sysconfig/dhcpd if you're using RHEL or similar).
 Then you can use the dhcp tags variable to pin systems to a specific dhcp
network.  The down side is, everytime you add a new network, you have to
update your dhcpd.template, settings, etc., thus the maintenance
headache.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
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

Reply via email to