[one-users] [VNET]why the vnet template always enable VLAN?

[Carlos Martín Sánchez]

Hi,

The PHYDEV attribute is used only by the network isolation driver 802.1Q
[1].
When OpenNebula sees it, it assumes you meant to set VLAN="YES"

Regards

[1] http://opennebula.org/documentation:rel3.4:hm-vlan
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>



On Tue, Jun 12, 2012 at 4:09 AM, mario wu <iamokcn at gmail.com> wrote:

> hi,all
>       i found a strange problem, why the vnet template after created,
> always enable VLAN?
> vnet template like this:
>
> NAME = "test 10.5"
> TYPE = RANGED
>  NETWORK_SIZE    = C
> NETWORK_ADDRESS = 10.10.0.0
> PHYDEV = "eth1"
> BRIDGE="brtest10.10"
>
> there isn't VLAN attribute. but wher i use "onevnet create
> test.vnet.template", the VLAN attribute is ENABLE.
> i need a network ,it isn't need a VLAN setting. i know i set the default
> VLAN id,can bypass the issue.
> my question is : why opennebula use such restrict? or this is a bug?
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120614/64c5286e/attachment-0002.htm>