Revision 347db542

b/doc/design-openvswitch.rst
55 55
Example:
56 56
switch1 will connect the VM to the default VLAN of the switch1.
57 57
switch1.3 means that the VM is connected to an access port of VLAN 3.
58
switch1.2:10:20 means that the VM is connected to a trunk port on switch1, carrying VLANs 2, 10 and 20.
58
switch1.2:10:20 means that the VM is connected to a hybrid port on switch1, carrying VLANs 2 untagged and 
59
VLANs 10 and 20 tagged.
60
switch1:44:55 means that the VM is connected to a trunk port on switch1, carrying VLANS 44 and 55
59 61

  
60
This configuration string is split at the dot and stored in nicparams[constants.NIC_LINK] and
61
nicparams[constants.NIC_VLAN] respectively.
62
This configuration string is split at the dot or colon respectively and stored in nicparams[constants.NIC_LINK] 
63
and nicparams[constants.NIC_VLAN] respectively. Dot or colon are stored as well in nicparams[constants.NIC_VLAN].
62 64

  
63 65
For Xen hypervisors, this information can be concatenated again and stored in the vif config as
64 66
the bridge parameter and will be fully compatible with vif-openvswitch as of Xen 4.3.
......
66 68
Users of older Xen versions should be able to grab vif-openvswitch from the Xen repo and use it
67 69
(tested in 4.2).
68 70

  
69
The differentiation between access port and trunk port is given by the number of VLANs that are
70
specified.
71

  
72 71
gnt-instance modify shall be able to add or remove single VLANs from the vlan string without users needing
73 72
to specify the complete new string.
74 73

  

Also available in: Unified diff