Specifying and installation bridge
by Dale, Christopher [Colloquium]
I am setting up a virtual environment and would like to have a
specific 'Deploy' network that I use for both installation and likely
a management network post installation. I would like this to always
reside on eth3. I have made some observations about the behavior of
this setup and would like to know if there is a way to improve my
approach. Here are two cobbler definitions that I have been using:
cobbler system add --name=client
--profile=rhel5-x86_64-generic:1:inCommonInc --clobber
cobbler system edit --name=client --hostname=client.deploy.local
--gateway=192.168.50.1
cobbler system edit --name=client --interface=eth0
--mac=52:54:00:35:a1:00 --ip=172.16.1.2 --subnet=255.255.255.0 \
--dns-name=client.clan.local
--static=true --virt-bridge=virbr2
cobbler system edit --name=client --interface=eth1
--mac=52:54:00:35:a1:01 --ip=192.168.242.11 --subnet=255.255.255.0 \
--dns-name=client.wan.local
--static=true --virt-bridge=virbr4
cobbler system edit --name=client --interface=eth2
--mac=52:54:00:35:a1:03 --ip=192.168.50.3 --subnet=255.255.255.0 \
--dns-name=client.deploy.local
--static=true --virt-bridge=virbr0
cobbler system edit --name=rscorp --kopts='device=eth2'
cobbler system edit --name=client --netboot-enabled=false
cobbler system add --name=server
--profile=rhel5-x86_64-generic:1:inCommonInc --clobber
cobbler system edit --name=server --hostname=server.deploy.local
--gateway=192.168.50.1
cobbler system edit --name=server --interface=eth0
--mac=52:54:00:35:a1:0a --ip=172.16.2.2 --subnet=255.255.255.0 \
--dns-name=server.slan.local
--static=true --virt-bridge=virbr3
cobbler system edit --name=server --interface=eth1
--mac=52:54:00:35:a1:0b --ip=192.168.242.12 --subnet=255.255.255.0 \
--dns-name=server.wan.local
--static=true --virt-bridge=virbr4
cobbler system edit --name=server --interface=eth2
--mac=52:54:00:35:a1:02 --ip=192.168.50.4 --subnet=255.255.255.0 \
--dns-name=server.deploy.local
--static=true --virt-bridge=virbr0
cobbler system edit --name=rscorp --kopts='device=eth2'
cobbler system edit --name=server --netboot-enabled=false
I build each of these KVMs with the following KOAN commands:
koan --virt --server=192.168.50.2 --system=client
--virt-path=/dev/mapper/vg160-lvClient
koan --virt --server=192.168.50.2 --system=server
--virt-path=/dev/mapper/vg160-lvServer
where 192.168.50.2 is a Satellite 5.4 KVM.
When the VM launches, it will always try to DHCP to eth0 first. I
have not found a way to prevent this. I set the kopts to point to
eth2 (even when there is only one other network - e.g. eth0). When
the dhcp request times out on eth0, it gives me the option to manually
configure eth0. If I select 'Back' where I then can select eth2
(unless I have only specified 2 devices - like eth0 and eth2 - in
which case I am presented options for eth0 and eth1). On the next
screen (the device configuration screen), I can select OK and eth2
will dhcp, get the correct address and install.
There are two questions:
1) Is there a way to essentially turn off the PXE capability of a
virtual Ethernet device as you would on a real box in the BIOS?
2) Is it a bug or by design that the Ethernet devices are enumerated
sequentially even when specifically told to do otherwise?
--
Christopher Dale | President and Forum Moderator
mobile: 540-903-1775 | email: christopher.dale(a)colloquium.co
web: http://www.colloquium.co | twitter: @colloquiumco | identica:
@colloquiumco
