Back to the original question:
What is most inconvenient for many users is:
1. The name we provide while creating the VNIC differs from the one in the guest
2. No correlation between IP and NIC
The current page covers for this but indeed as raised here does not cover what happens if
this information is not easy to retrieve due to non strait forward configurations.
What I suggest is,
For the short term:
- Agent to report the MACs, IPs and interface names if can be found, engine to match these
to the existing and show
Name In Engine| Name in guest | MAC | IP etc like the current feature page, but...
- If a match could not be found then just report Name in Engine N/A and then the rest and
keep it in dynamic only table.
This is useful for NICs created by hooks, advanced topology that we can't support ATM
*The above does require the agent to at least match MAC to IP.
Long term: The agent to report a topology the same as vdsm does (use same code at least
for Linux guests?) and present it similar to what we present in the host tab. In most
cases this will collapse to the short term.
MTU, is good to have in any of the two if we can get it.
----- Original Message -----
From: "Moti Asayag" <masayag(a)redhat.com>
To: "Yaniv Kaul" <ykaul(a)redhat.com>
Cc: "Simon Grinberg" <simon(a)redhat.com>, engine-devel(a)ovirt.org
Sent: Thursday, November 22, 2012 5:39:53 PM
Subject: Re: [Engine-devel] Report vNic Implementation Details
On 11/22/2012 05:36 PM, Yaniv Kaul wrote:
> On 11/21/2012 10:53 PM, Andrew Cathrow wrote:
>> ----- Original Message -----
>>> From: "Moti Asayag" <masayag(a)redhat.com>
>>> To: engine-devel(a)ovirt.org
>>> Sent: Wednesday, November 21, 2012 12:36:58 PM
>>> Subject: [Engine-devel] Report vNic Implementation Details
>>> Hi all,
>>> This is a proposal for reporting the vNic implementation details
>>> reported by the guest agent per each vNic.
>>> Please review the wiki and add your comments.
>> While we're making the change is there anything else we'd want to
>> report - MTU, MAC (since a user might try to override), etc ?
> Do we support change of MAC from within the VM? Is it even working?
Shouldn't work if the nwfilter rules are enabled (which are by
>>> Engine-devel mailing list
>> Engine-devel mailing list
Engine-devel mailing list