On 1/27/12 11:22 AM, "kmestery" <kmestery@xxxxxxxxx> wrote:
> Hi Dan:
>
> We at Cisco have been looking at this as well, and in fact were going to
> propose some things in this area as well. Our proposal (which frankly just
> builds on top of what you have):
>
> The proposal at hand is to add some libvirt configuration as follows:
>
> <network>
> <name>ovs-network</name>
> <forward mode='ovs' dev='br0'>
> <script path='/etc/qemu-ifup-ovs'/>
> </forward>
> </network>
>
> This would setup the OVS network entity, and sets up a forwarding mode of
> "ovs", which indicates Open vSwitch is used to forward traffic.
>
> <interface type='network'>
> <source network='ovs-network'/>
> <virtualport type='openvswitch'>
> <parameters interfaceid="interface-xyz"/>
> </virtualport>
> </interface>
>
> This model of exposing parameters to virtualport types allows for further
> expansion as new interface types and parameters are added.
>
> Thoughts?
The existing forward mode bridge could also work perhaps. If there are no
special cases for ovs.
<network>
<name>ovs-network</name>
<forward mode='bridge' dev='ovs-bridge'>
<script path='/etc/qemu-ifup-ovs'/>
</forward>
</network>
Or maybe the real syntax is,
<network>
<name>ovs-network</name>
<forward mode='bridge'>
<bridge name='ovs-bridge'/>
<script path='/etc/qemu-ifup-ovs'/>
</forward>
</network>
Thanks,
Roopa
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list