Ovirt devel - Jun 2009 - only seeing one NIC in network device editor

Hi,

When I click on "Edit Network" on my managed node in the hosts tab of 
the oVirt UI I only see one NIC.  My managed node has 2 NICs, one on the 
guest network and one on the admin network.  The NIC on the admin 
network is not listed in the network editor.  Is this normal?

I'm trying to create a VM and boot the cobbler profile I created for 
Fedora 10 but I can only boot the VM on the guest network for some 
reason (presumably because that's the only NIC appearing in the network 
editor for the host).

Cheers,
Justin.

Justin Clacherty wrote:
> Hi,
>
> When I click on "Edit Network" on my managed node in the hosts
tab of
> the oVirt UI I only see one NIC.  My managed node has 2 NICs, one on 
> the guest network and one on the admin network.  The NIC on the admin 
> network is not listed in the network editor.  Is this normal?
>
> I'm trying to create a VM and boot the cobbler profile I created for 
> Fedora 10 but I can only boot the VM on the guest network for some 
> reason (presumably because that's the only NIC appearing in the 
> network editor for the host).
>
> Cheers,
> Justin.
Yes, this is the way it's currently set up to work. In the 2-or-more 
network use csae the admin network is intended for node communication 
only. On the node, the admin network is the only one that gets an IP, 
and the guests are not intended to use this network (in our testing 
environmnent the admin network is completely unconnected to anything but 
the oVirt server and the nodes). If your node had 3 NICs on it you'd 
have 2 networks to choose from for your guest.

There is a problem with the current implementation in that it does not 
support a single-network installation right now. We're currently working 
through determining what needs to be done to support this, but in the 
case where you only have a single network we will have to allow guests 
on the admin (and only) network.

Scott

including ovirt-devel in the reply

Scott Seago wrote:
> Justin Clacherty wrote:
>> Scott Seago wrote:
>>> Yes, this is the way it's currently set up to work. In the
2-or-more
>>> network use csae the admin network is intended for node 
>>> communication only.
>> Ok, that makes sense.  What about storage?  I was under the 
>> impression that the san could sit on the admin network.  Is this the 
>> case or must it be on the guest network?
>>
> The san is fine on the admin network, as the node mounts the storage 
> -- it's exposed to the VM as a local disk.
>> Doesn't this make cobbler somewhat redundant?  If I set up a distro
>> in cobbler, I can't actually use it...  Should cobbler be made 
>> available to the guest network too?  Though that would probably mean 
>> that the admin node would have to serve dns and dhcp to the guest 
>> network which wouldn't be ideal.
>>
> Yes, this is an ongoing point of discussion here.  Originally it was 
> all on one network so there weren't any cobbler issues here. Cobbler 
> images work fine as-is, since the iso gets mounted as a local disk for 
> the guest. For cobbler profiles to work cobbler would have to listen 
> on the guest network as well -- or really on any network that a guest 
> might be on, since it's possible to set up oVirt with more than 2 
> networks on the nodes. I'm not sure about dhcp/dns for the guest 
> network -- we could certainly set it up to do that, but I'd imagine 
> that in most cases your guest network is your existing public (or 
> intranet) network that's already served by existing dhcp/dns. Of 
> course if the guests are coming up on a network that already has an 
> external pxe server you might have other problems using the cobbler 
> instance for pxe booting guests.
>
> Maybe Hugh or someone else has other thoughts on how to handle guest 
> pxe/provisioning -- it's something we're still discussing.
>> Storage is another issue for me at the moment, I set up an iscsi 
>> partition on my san, then added it under storage (on the admin 
>> network, but tried it on both admin and guest) but it just shows up 
>> pending.  There's an odd error in the tasks list which is something
>> along the lines of it returning 255 (-1 I guess)....Is there a 
>> problem with connecting to iscsi at the moment?
> There shouldn't be any problems with iscsi -- it's been recently 
> working. If you get us more information on the task error -- including 
> the relevant contents of /var/log/ovirt-server/taskomatic.log we'll 
> look into it.
>
> Thanks,
> Scott
>>
>> Cheers,
>> Justin.
>
>