After successfully building a couple of machines using cobbler, I was
after some suggestions on the best way to go about rolling it out on
a larger scale.
Our machines all have two ethernet interfaces setup as follows:
eth0 - public interface, will be configured with a static IP
eth1 - build network, will be configured using DHCP managed by
cobbler, with PXE booting across this network.
After a bit of playing around, I have managed to get PXE booting from
eth1 okay, and the first steps of the process occur okay. The OS
though (CentOS) keeps still prompting for the IP address to assign eth0
The system was added to cobbler using the following command:
where the IP x.x.x.1 is on the public interface (ethernet addr
00:x:x:x:9A:F8)
and ethernet 00:x:x:x:9A:F9 is on the build network interface
Is this the "right" way to go about this, or should I instead be
modifying profiles/ks files?
Thanks for any suggestions,
Matt
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-26-2008, 12:54 PM
Michael DeHaan
build over eth1
Matt Baker wrote:
After successfully building a couple of machines using cobbler, I was
after some suggestions on the best way to go about rolling it out on a
larger scale.
Our machines all have two ethernet interfaces setup as follows:
eth0 - public interface, will be configured with a static IP
eth1 - build network, will be configured using DHCP managed by
cobbler, with PXE booting across this network.
After a bit of playing around, I have managed to get PXE booting from
eth1 okay, and the first steps of the process occur okay. The OS
though (CentOS) keeps still prompting for the IP address to assign eth0
Basically this deals with not having the extra network line in the
kickstart file, not with what you have configured in Cobbler.
The system was added to cobbler using the following command:
cobbler system add --profile=CentOS-5.1-x86_64 --interface=0
--ip=x..x.x.1 --mac=00:x:x:x:9A:F8 --gateway=x.x.x.254 --interface=1
--name=00:x:x:x:9A:F9
This is fine, in fact, interface=0 is the default, so you don't need to
specify it. You can have any number of interfaces listed here (well,
up to 8 currently), and you do not need to enter all of them into
Cobbler, just the ones that you need to show up in the PXE Linux tree
and possibly for DHCP reservations.
I assume the "x's" are just to not share the full details here and
aren't literal.
where the IP x.x.x.1 is on the public interface (ethernet addr
00:x:x:x:9A:F8)
and ethernet 00:x:x:x:9A:F9 is on the build network interface
Is this the "right" way to go about this, or should I instead be
modifying profiles/ks files?
You need to do both. If you have two network interfaces, your
kickstart needs two network lines.
Basically you can use variables like $ip_address_intf0 and so forth in
there to automate filling those in if you like, or just putting in two
lines to tell both interfaces to dhcp. You might also be able to
indicate the other interface should not be used there also.
I'd also recommend looking into ksdevice=link for kernel options.
Thanks for any suggestions,
Matt
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-26-2008, 02:12 PM
Matt Baker
build over eth1
Hello Michael,
The system was added to cobbler using the following command:
This is fine, in fact, interface=0 is the default, so you don't
need to specify it. You can have any number of interfaces listed
here (well, up to 8 currently), and you do not need to enter all of
them into Cobbler, just the ones that you need to show up in the
PXE Linux tree and possibly for DHCP reservations.
I assume the "x's" are just to not share the full details here and
aren't literal.
Correct, I just removed the real life IP's from habit. The build
network (eth1) are from private IP address space, and the eth0
interface IP's are public IP space.
where the IP x.x.x.1 is on the public interface (ethernet addr
00:x:x:x:9A:F8)
and ethernet 00:x:x:x:9A:F9 is on the build network interface
Is this the "right" way to go about this, or should I instead be
modifying profiles/ks files?
You need to do both. If you have two network interfaces, your
kickstart needs two network lines.
Basically you can use variables like $ip_address_intf0 and so forth
in there to automate filling those in if you like, or just putting
in two lines to tell both interfaces to dhcp. You might also be
able to indicate the other interface should not be used there also.
I'd also recommend looking into ksdevice=link for kernel options.
Ah, that's the hint I think I needed - and have now found the section
in the wiki. I was not understanding the use of the $ip_address_intf0
variable. Obviously I wanted to keep the ks files as generic as
possible (all the systems are pretty much built the same), with just
the IP's changing. using the 'cobbler system add' seemed the best way
to do this.
thanks for your help,
Matt
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-27-2008, 01:14 PM
Matt Baker
build over eth1
The system was added to cobbler using the following command:
This is fine, in fact, interface=0 is the default, so you don't
need to specify it. You can have any number of interfaces listed
here (well, up to 8 currently), and you do not need to enter all of
them into Cobbler, just the ones that you need to show up in the
PXE Linux tree and possibly for DHCP reservations.
Following on from this, I am finding an issue which I cannot seem to
work out where I am going wrong.
# cobbler system report
system : test
profile : CentOS-5.1-x86_64
kernel options : {}
kickstart : <<inherit>>
ks metadata : {}
netboot enabled? : True
owners : ['admin']
server : <<inherit>>
virt cpus : <<inherit>>
virt file size : <<inherit>>
virt path : <<inherit>>
virt ram : <<inherit>>
virt type : <<inherit>>
interface : intf0
mac address :
ip address :
hostname :
gateway :
subnet :
virt bridge :
dhcp tag :
interface : intf1
mac address : 00:15:60:ED:9A:F9
ip address : 10.2.25.1
hostname :
gateway : 119.252.19.254
subnet :
virt bridge :
dhcp tag :
I have tried a few options, like leaving off the first --mac entry,
putting in an --interface=0 statement etc, but in all cases it
appears any options are only used for the 2nd interface. Leaving off
the 2nd interface definitions:
# cobbler system add --name=test --profile=CentOS-5.1-x86_64 --
mac=00:15:60:ED:9A:F8 --ip=119.252.19.1 --gateway=119.252.19.254
places all the configuration as expected under intf0
Anyone have a suggestion on where I am going wrong?
Cheers,
Matt
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-29-2008, 02:54 PM
Matt Baker
build over eth1
The system was added to cobbler using the following command:
This is fine, in fact, interface=0 is the default, so you don't
need to specify it. You can have any number of interfaces listed
here (well, up to 8 currently), and you do not need to enter all
of them into Cobbler, just the ones that you need to show up in
the PXE Linux tree and possibly for DHCP reservations.
Following on from this, I am finding an issue which I cannot seem
to work out where I am going wrong.
# cobbler system report
system : test
profile : CentOS-5.1-x86_64
kernel options : {}
kickstart : <<inherit>>
ks metadata : {}
netboot enabled? : True
owners : ['admin']
server : <<inherit>>
virt cpus : <<inherit>>
virt file size : <<inherit>>
virt path : <<inherit>>
virt ram : <<inherit>>
virt type : <<inherit>>
interface : intf0
mac address :
ip address :
hostname :
gateway :
subnet :
virt bridge :
dhcp tag :
interface : intf1
mac address : 00:15:60:ED:9A:F9
ip address : 10.2.25.1
hostname :
gateway : 119.252.19.254
subnet :
virt bridge :
dhcp tag :
I have been trying to try a few different combinations, all with
basically the same result. Until that it, I fired up the web
interface to cobbler!
Entering the 2nd interface information via the web interface works
fine as the system report below shows.
Has anyone managed to get more than one interface configured via the
command line tool?
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-29-2008, 05:14 PM
Robin Bowes
build over eth1
Matt Baker wrote:
Hello Michael,
The system was added to cobbler using the following command:
cobbler system add --profile=CentOS-5.1-x86_64 --interface=0
--ip=x..x.x.1 --mac=00:x:x:x:9A:F8 --gateway=x.x.x.254 --interface=1
--name=00:x:x:x:9A:F9
This is fine, in fact, interface=0 is the default, so you don't need
to specify it. You can have any number of interfaces listed here
(well, up to 8 currently), and you do not need to enter all of them
into Cobbler, just the ones that you need to show up in the PXE Linux
tree and possibly for DHCP reservations.
I assume the "x's" are just to not share the full details here and
aren't literal.
Correct, I just removed the real life IP's from habit. The build network
(eth1) are from private IP address space, and the eth0 interface IP's
are public IP space.
where the IP x.x.x.1 is on the public interface (ethernet addr
00:x:x:x:9A:F8)
and ethernet 00:x:x:x:9A:F9 is on the build network interface
Is this the "right" way to go about this, or should I instead be
modifying profiles/ks files?
You need to do both. If you have two network interfaces, your
kickstart needs two network lines.
Basically you can use variables like $ip_address_intf0 and so forth in
there to automate filling those in if you like, or just putting in two
lines to tell both interfaces to dhcp. You might also be able to
indicate the other interface should not be used there also.
I'd also recommend looking into ksdevice=link for kernel options.
Ah, that's the hint I think I needed - and have now found the section in
the wiki. I was not understanding the use of the $ip_address_intf0
variable. Obviously I wanted to keep the ks files as generic as possible
(all the systems are pretty much built the same), with just the IP's
changing. using the 'cobbler system add' seemed the best way to do this.
Matt,
I wrote a kickstart snippet that automates the network section of the
kickstart file. Let me dig it out...
Put this in /var/lib/cobbler/snippets/network_config:
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-30-2008, 12:15 AM
Michael DeHaan
build over eth1
I have been trying to try a few different combinations, all with
basically the same result. Until that it, I fired up the web interface
to cobbler!
Entering the 2nd interface information via the web interface works
fine as the system report below shows.
Has anyone managed to get more than one interface configured via the
command line tool?
You must split your edits into two commands as the edit command effects
only one interface at a time:
cobbler system edit --name=foo --interface=0 ...
cobbler system edit --name=foo --interface=1 ...
For complex configs, using the webapp is better.
--Michael
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
06-30-2008, 02:12 AM
Matt Baker
build over eth1
Thanks Michael, that was the key I was missing !
Unfortunately, while the web interface is good I am looking to script
as much of this as possible.
Regards,
Matt
I have been trying to try a few different combinations, all with
basically the same result. Until that it, I fired up the web
interface to cobbler!
Entering the 2nd interface information via the web interface works
fine as the system report below shows.
Has anyone managed to get more than one interface configured via
the command line tool?
You must split your edits into two commands as the edit command
effects only one interface at a time:
cobbler system edit --name=foo --interface=0 ...
cobbler system edit --name=foo --interface=1 ...
For complex configs, using the webapp is better.
--Michael
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
build over eth1
