Version 3 (modified by 10 years ago) (diff) | ,
---|
How to Share a VLAN
The contents of this page are adapted from an e-mail from Leigh Stoller.
This page describes how to convert a LAN into a Shared LAN without operator intervention.
The general process to share a LAN is:
- Reserve resources which contain a LAN.
- Run
perform operational action
with the commandgeni_sharelan
and setting the two optionsgeni_sharelan_lanname
andgeni_sharelan_token
.geni_sharelan_lanname
is theclient_id
of the LAN reserved in the previous step.geni_sharelan_token
is the name the new shared VLAN will be known by. - Reserve resources connect to a LAN (probably in another slice). Configured the LAN to be a shared LAN whose name matches the value of
geni_sharelan_token
in the previous step. - Resources should now be able to communicate with each other using the shared VLAN.
The general process to unshare a LAN is:
- Run
perform operational action
with the commandgeni_unsharelan
and setting the two optionsgeni_sharelan_lanname
andgeni_sharelan_token
set as they were when you originally shared it. - Resource no longer be able to communicate with each other using the shared VLAN.
Caveats:
- The LAN being shared must obviously be a real VLAN, not a trivial link
(link between two VMs on the same physical host). In other words, the minimal case requires two VMs which each have a different
component_id
. - There is no change to idleness or expiration behavior; these resources must be renewed like other resources using the usual mechanisms.
- When the shared LAN is unshared, or the slice terminated, all of the other slices that were using that LAN will have the ports yanked out and disabled. However, the resources will remain.
- As of November 8, this only works at ProtoGENI Utah.