[one-users] Vlan template

[Jaime Melis]

Hi,

I'm not sure I understand the problem, but I have the feeling your use case
is not supported.

You can implement VLANs either with the 802.1Q [1] or the Open vSwitch [2]
drivers.

However, you can only tag one VLAN per interfaces, which as far as I know,
is the only thing that makes sense?

[1] http://opennebula.org/documentation:rel4.0:hm-vlan
[2] http://opennebula.org/documentation:rel4.0:openvswitch

Cheers,
Jaime


On Wed, Apr 24, 2013 at 1:04 PM, Alexandre Bezroutchko <abb at gremwell.com>wrote:

> On 04/23/2013 08:18 PM, Ionut Popovici wrote:
> > Hello i'm interested to know if there is any way to setup on and
> > template a
> > nic interface in TRUNK mode, the thing is that i wana a interface to
> > join in
> > more than 1 Vlan.
> > An example is that i wana to add an router on the network and pass the
> > traffic tru router but the router will handle more vlans, networks
> >
> > The ideea is to manage the traffic tru a router or more but i don't
> > wana the
> > opennebula host to get involed to any traffic.
> If you serious about your host not being involved into handling network
> traffic for VMs, you need to do PCI pass-through of your network cards
> to a separate network driver domain and do all bridging/routing there. I
> saw it in the list of features of xen-4.2 I think. Qubes OS uses such an
> arrangement, but they use earlier version of xen, probably backported
> some patches. You might be able to do the same with other hypervisors
> supporting PCI pass-through.
>
> If you put a bar little lower and accept the host working as a bridge,
> you should be able to have tagged traffic delivered from a physical
> interface to a VM using standard Linux bridge without any further
> trickery. Just use dummy network driver in Opennebula and terminate
> VLANs in your VM with vconfig.
>
> This will not let you choose what VLANs to bridge though. If you really
> need it perhaps you can use ebtables, use OpenVSwitch, or create a mess
> of intermediate bridges to "extract" individual VLANs and bridge them
> again together. None of this will be out-of-the-box though.
>
> Hope this helps.
>
> Cheers,
> Alex
> >
> > Ex in template is
> > NIC=[
> >   IP="x.x.x.x",
> >   NETWORK="wan" ]
> > NIC=[
> >   NETWORK="lan1",
> >   NETWORK="lan2",
> > VLAN="YES",
> > VLAN_ID="64",
> > VLAN_ID="65" ]
> > TEMPLATE_ID="1023"
> >
> > ideea is that on the second nic i i have an interface set on vlan
> > trunk mode
> > not access like vyatta
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Join us at OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin, 24-26
September, 2013
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | jmelis at opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130520/d64b7293/attachment.htm>