[ovirt-users] Network tagging

Alex Crow acrow at integrafin.co.uk
Fri Dec 18 14:03:27 UTC 2015


Just curious, why would you want to bond two different VLAN interfaces? 
It does not make much sense.

You can add a network with a VLAN and then use it on a bonded connection 
or an a single interface, if that's what you mean.

I just wish there was a way to make the VLAN ID optional, so you could 
use it tagged on a host with only a couple of ethernet interfaces, and 
then untagged on an interface on a machine it lots of eth interfaces (eg 
to spread the VLANs over multiple interfaces: imagine a host with 2x10G, 
one would be storage and the other for all VLANs tagged. Another host 
might have 8 or more interfaces, on that each VLAN could be untagged 
per-interface.)

Alex

On 18/12/15 13:17, Kevin COUSIN wrote:
> Hi list,
>
> Is it possible to add same VLAN as tagged for different purposes :
>
> * VLAN XX as VM network and tagged to attach VM
> * VLAN XX tagged for bonding with another VLAN on an interface
>
>
> Regards
>
> Kevin C
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).



More information about the Users mailing list