[Engine-devel] bridgeless networks - update

[Roy Golan]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Roy Golan" <rgolan at redhat.com>
> Cc: engine-devel at ovirt.org
> Sent: Thursday, February 16, 2012 12:21:49 AM
> Subject: Re: [Engine-devel] bridgeless networks - update
> 
> On 02/15/2012 06:50 PM, Roy Golan wrote:
> > following ovirt engine weekly here's a summary of the changes:
> >
> > 1. no validation during vmInterface creation
> > 2. when attaching a network the default value is bridged (GUI
> > responsibility)
> 
> so what is the default if one didn't pass it in the API (i.e.,
> backend
> should have a default value. UI may choose whatver).
I generally dislike default values in API because client 
wont know what it is, default behavior might change in time etc... 
> (and the UI/API name in the wiki is something around "allow to run
> vms",
> not bridged - so maybe change the terminology used to discuss this to
> reduce risk of confusion/mistakes later).
> 
> 
> > 3. monitoring - detect mixed configured cluster (network "foo" is
> > bridged on one host and not on another)
> >     and issue an audit log warning with event interval of 1 day
> 
> why does this matter if cluster is mixed?
to inform a potential migration problem
> i.e., wouldn't this be interesting per host, that a network which
> could
> be bridgeless is bridged to warn about?
I agree that an admin might like a notice that he can improve the host's performance.
but currently how can we say a network can be bridgeless given that we don't have the nic type yet?
detect if no vmInterfaces are connected to it maybe?

> 
> >
> > wiki will be updated accordingly.
> 
> having fast read it, couldn't understand the backward compatibility
> section ("Its compatibility version is 3.1 and enforced by the
> enclosed
> command as mentioned already")
> i'd make it clear this is a 3.1 DC feature, and not a cluster one(?)
> becuase iirc, setupNetworks is actually host level 3.1 compatibility
> level, not cluster/dc wide?
yes its not clear enough that 3.0 cluster cannot have their network bridgeless. will fix this to be clearer.
> 
> >
> > Thanks,
> > Roy
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> 
>