Network reconfiguration tutorial: Difference between revisions
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
In the first time, we will set up a simple topologie with 2 VLANs, a global and a local. In each VLAN there will be at least one node, and one interface of a node with 2 interfaces. | In the first time, we will set up a simple topologie with 2 VLANs, a global and a local. In each VLAN there will be at least one node, and one interface of a node with 2 interfaces. | ||
= Set up = | |||
== Reservations == | |||
A global VLAN is all over Grid'5000, so we have to reserve it on only one site. We will use Rennes and Nancy sites. | |||
{{Term|location=rennes:frontend|cmd=<code class="command">oarsub</code> -l {"type='kavlan-global'"}/vlan=1+{"type='kavlan-local'"}/vlan=1+{"cluster='paravance'"}/nodes=3,walltime=3 -I -t deploy}} | |||
With this reservation we have, 1 kavlan-local, 1 kavlan-global and 3 nodes on paravance cluster. Paravance is a cluster of nodes with 2 interfaces. | |||
Get your Vlans ID : | |||
{{Term|location=frontend|cmd=<code class="command">kavlan</code> -V}} | |||
How to know which VLAN is global and which is local ? Is simple, it's write in [[KaVLAN]] : | |||
* kavlan-local : [1-3] | |||
* kavlan : [4-9] | |||
* global : [10-20] | |||
Now we will deploy our nodes with debian wheezy minimal : | |||
{{Term|location=rennes:frontend|cmd=<code class="command">kadeploy3</code> -e wheezy-x64-min -k -f $OAR_NODEFILE}} | |||
During the deployment you can reserve and deploy a node on Nancy in other terminal : | |||
{{Term|location=nancy:frontend|cmd=<code class="command">oarsub</code> -I -l walltime=3 -t deploy}} | |||
{{Term|location=nancy:frontend|cmd=<code class="command">kadeploy3</code> -e wheezy-x64-min -k -f $OAR_NODEFILE}} |
Revision as of 15:29, 4 January 2016
![]() |
Note |
---|---|
This page is actively maintained by the Grid'5000 team. If you encounter problems, please report them (see the Support page). Additionally, as it is a wiki page, you are free to make minor corrections yourself if needed. If you would like to suggest a more fundamental change, please contact the Grid'5000 team. |
Introduction
This TP aims to discover a method to configure a network in Grid'5000 using KaVLAN.
KaVLAN is a tool on Grid'5000 which allow to the user to manage VLANs in the platform. It edits switch configuration to change the VLAN number of the port corresponding to the interface of a node. This method permits complete layer 2 isolation.
Three kinds of VLANs are available on Grid'5000, you can find more information on the page KaVLAN. In this TP, we will use only global Vlan and local Vlan.
In the first time, we will set up a simple topologie with 2 VLANs, a global and a local. In each VLAN there will be at least one node, and one interface of a node with 2 interfaces.
Set up
Reservations
A global VLAN is all over Grid'5000, so we have to reserve it on only one site. We will use Rennes and Nancy sites.
![]() |
rennes:frontend :
|
oarsub -l {"type='kavlan-global'"}/vlan=1+{"type='kavlan-local'"}/vlan=1+{"cluster='paravance'"}/nodes=3,walltime=3 -I -t deploy |
With this reservation we have, 1 kavlan-local, 1 kavlan-global and 3 nodes on paravance cluster. Paravance is a cluster of nodes with 2 interfaces.
Get your Vlans ID :
How to know which VLAN is global and which is local ? Is simple, it's write in KaVLAN :
- kavlan-local : [1-3]
- kavlan : [4-9]
- global : [10-20]
Now we will deploy our nodes with debian wheezy minimal :
During the deployment you can reserve and deploy a node on Nancy in other terminal :