Changes between Version 2 and Version 3 of HowTo/ShareALan


Ignore:
Timestamp:
11/08/13 18:04:13 (8 years ago)
Author:
sedwards@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ShareALan

    v2 v3  
    33''The contents of this page are adapted from an e-mail from Leigh Stoller.''
    44
     5This page describes how to convert a LAN into a Shared LAN without operator intervention.
    56
     7The general process to share a LAN is:
     8 1. Reserve resources which contain a LAN. 
     9 2. Run `perform operational action` with the command `geni_sharelan` and setting the two options `geni_sharelan_lanname` and `geni_sharelan_token`.  `geni_sharelan_lanname` is the `client_id` of the LAN reserved in the previous step.  `geni_sharelan_token` is the name the new shared VLAN will be known by.
     10 3. 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.
     11 4. Resources should now be able to communicate with each other using the shared VLAN.
    612
    7 Caveats at ProtoGENI:
     13The general process to unshare a LAN is:
     14 1. Run `perform operational action` with the command `geni_unsharelan` and setting the two options `geni_sharelan_lanname` and `geni_sharelan_token` set as they were when you originally shared it. 
     15 2. Resource no longer be able to communicate with each other using the shared VLAN.
     16
     17Caveats:
    818 1. The LAN being shared must obviously be a real VLAN, not a trivial link
    919  (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`.
     
    1222  other slices that were using that LAN will have the ports yanked out and
    1323  disabled. However, the resources will remain. 
     24 4. As of November 8, this only works at ProtoGENI Utah.