[one-users] Ethernet VLAN configuration

[Yann Vigara]

Ok, that's for the Xen part.
But I also need to automatically create the interface on the node where 
the VM will be deployed.
So before running the VM, we would like to verify that the interface 
already exists and if not execute this command :
# vconfig add <BRIDGE> <VLAN_ID>

I can create in Xen a specific network script which do this job, but 
ideally it should be independent of the vmm driver and managed by ONE.

As the vnet id is generated automatically by ONE, I prefer to have the 
possibility to force manually a VLAN Id (we have specific firewall rules 
for each VLAN).

Yann.

Javier Fontan wrote:
>
> Hello,
>
> Deployment files used to start VM's are generated inside ONE Core. To 
> do that change I think it is better to change the deployment file 
> generation. If you are using Xen here is the place where to add the 
> VLAN_ID:
>
> http://dev.opennebula.org/repositories/entry/opennebula/branches/one-1.2/src/vmm/XenDriver.cc#L280 
>
>
> In Network Definition files you can add that VLAN_ID variable and it 
> will be added to the database.
>
> I don't know if it is a valid option but perhaps you can use the vnet 
> id as the vlan number so you don't have to get that extra information 
> from the vnet definition.
>
> Anyway, that feature seems logical to me, tell us how your 
> developments go.
>
> Bye
>
> On Mar 18, 2009, at 11:17 AM, Yann Vigara wrote:
>
>> Hi,
>>
>> We are currently deploying Opennebula and, for security reasons, we 
>> need to assign an Ethernet VLAN to our customers' private network.
>> We also would like to have the ability to use the same network range 
>> in different VLAN.
>>
>> Here is the kind of configuration we would like :
>>
>> Customer 1 VLAN
>> NAME           = "Customer 1 VLAN"
>> TYPE           = RANGED
>> BRIDGE         = eth0
>> NETWORK_SIZE   = 254
>> NETWORK_ADDRESS= 192.168.1.0
>> *VLAN_ID        = 1*
>>
>> Customer 2 VLAN
>> NAME           = "Customer 2 VLAN"
>> TYPE           = RANGED
>> BRIDGE         = eth0
>> NETWORK_SIZE   = 254
>> NETWORK_ADDRESS= 192.168.1.0
>> *VLAN_ID        = 2*
>>
>> With this config, Opennebula should create and automatically 
>> configure the interface on the nodes. It should result in an eth0.1 
>> and eth0.2 interface.
>>
>> Is such a configuration possible ?
>> Where should I start if I want to implement this behavior (sorry I'm 
>> new to Opennebula and Ruby) ?
>>
>> Thanks in advance for your help.
>>
>> Best regards,
>>
>> Yann.
>> -- 
>>
>> Atomes - Hébergement et infogérance
>> http://www.atomes.com <http://www.atomes.com/accueil>
>> 356, Allée des Sardenas, 13680 Lançon de Provence
>> Hotline : +33 (0)811 033 330   - Tél : +33 (0)4 13 41 62 93
>> Portable: +33 (0)6 75 06 02 76 - Fax : +33 (0)4 13 41 62 94
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>

-- 

Atomes - Hébergement et infogérance
http://www.atomes.com <http://www.atomes.com/accueil>
356, Allée des Sardenas, 13680 Lançon de Provence
Hotline : +33 (0)811 033 330   - Tél : +33 (0)4 13 41 62 93
Portable: +33 (0)6 75 06 02 76 - Fax : +33 (0)4 13 41 62 94