[ovirt-devel] [ovirt-users] How to add ovs-based VM in version 4.0.2? Thank you

[lifuqiong]

Hi Petr,
	Thank you for your advice. But what does "Clean hosts" mean, as I know now, When you add a clean Host to ovirt engine, the vdsm or ovirt node will create a Network named ovirtmgmt, which is an Linux bridge network, 
How do I clean the network? Just delete the linux bridge and reset the linux bridge binding's physical Nic?
	
	Hope to get your help as sonn as possible.
	Thank you.
	Mark

-----邮件原件-----
发件人: Petr Horacek [mailto:phoracek at redhat.com] 
发送时间: 2016年8月2日 18:29
收件人: lifuqiong
抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; users
主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 4.0.2? Thank you

If the host was a part of legacy cluster you must do manual cleanup of all networks. Currently VDSM cannot change Linux bridges into OVS ones (this will be implemented soon). Make sure that you are adding clean hosts (with NIC interface/s only) to OVS cluster.

Regards,
Petr

2016-08-02 10:01 GMT+02:00 Michael Burman <mburman at redhat.com>:
> Hi ,
>
> Did you synced network/s after you moved the host to the ovs type cluster?
> It seems like you didn't..)
> Go to 'Hosts' main tab' and choose the host, go to 'Network 
> Interfaces' sub tab and press the 'Sync All Networks' , now the 
> networks should be synced to host as ovs switch type.
> Run the vm and check the xml.
> It should look something like this:
>
> <source bridge='vdsmbr_nRL3asDq'/>
>       <virtualport type='openvswitch'>
>
> thanks
>
>
> On Tue, Aug 2, 2016 at 9:37 AM, Meni Yakove <myakove at redhat.com> wrote:
>>
>>
>>
>> On Tue, Aug 2, 2016 at 7:12 AM, lifuqiong <lifuqiong at cncloudsec.com>
>> wrote:
>>>
>>> I create a cluster which already enabled ovs network as you 
>>> mentioned , but when I create vm in this cluster,  I can only using 
>>> ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux bridge.
>>>
>>> I found no way to add a OVS vNIC profile,  I have to chose 
>>> ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the vm 
>>> is still using Linux bridge to communicate with outside, not the ovs.
>>>
>>>
>>>
>>> Need I to create a ovs bridge or vport and bind it to physical NIC 
>>> in vdsm manually?
>>>
>>>
>>>
>>> Hope your reply as soon as possible.
>>>
>>> Thank you
>>>
>>> Mark
>>>
>>>
>>>
>>> 发件人: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] 代表 
>>> Meni Yakove
>>> 发送时间: 2016年8月1日 16:42
>>> 收件人: Dan Kenigsberg
>>> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in 
>>> version 4.0.2? Thank you
>>>
>>>
>>>
>>> On Mon, Aug 1, 2016 at 11:07 AM, Dan Kenigsberg <danken at redhat.com>
>>> wrote:
>>>
>>> On Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote:
>>> > Hi, I upgrade my ovirt to version 4.0.2.2, how to using ovs in 
>>> > this version?
>>> > Is there any instruction? Thank you
>>>
>>> Please note and note well: OVS is not production-grade yet. It is 
>>> only a preliminary tech preview, under active development.
>>>
>>> However, we'd be very happy to get your help in testing it (and 
>>> possibly fixing it, too).
>>>
>>> When defining a new cluster, you should see a check box, letting you 
>>> select OVS for that cluster.
>>>
>>>
>>>
>>> To be precise, this is not a check box. In the Edit Cluster dialog, 
>>> look at the "switch
>>>
>>> type" option, and change "LEGACY" to "OVS".
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> After being checked, each VM network that is defined in your cluster 
>>> would be implemented with OVS instead of Linux bridge.
>>>
>>> As aluded before, there are plenty of known definciencies (e.g., no 
>>> persistence of ip config on VM network, no live migration, not all 
>>> bond modes, etc etc). But do not hesitate to raise other issues with 
>>> the devel mailing list.
>>>
>>> Happy testing!
>>>
>>> Dan.
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>>
>>
>>
>
>
>
> --
> Michael Burman
> RedHat Israel, RHEV-M QE Network Team
>
> Mobile: 054-5355725
> IRC: mburman