Changes between Version 4 and Version 5 of HowTo/ShareALan


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

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ShareALan

    v4 v5  
    1515 2. Resource no longer be able to communicate with each other using the shared VLAN.
    1616
    17 Caveats:
     17== Caveats ==
    1818 1. The LAN being shared must obviously be a real VLAN, not a trivial link
    1919  (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`.
     
    2424 4. There is currently no way to determine which slice contains the LAN which is shared. You must keep track of this manually.
    2525 5. As of November 8, this only works at ProtoGENI Utah.
     26
     27== Example ==
     28
     29A minimal RSpec to use for reserving resources is:
     30{{{
     31#!xml
     32<rspec type="request"
     33xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/request.xsd"
     34xmlns:client="http://www.protogeni.net/resources/rspec/ext/client/1"
     35xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     36xmlns="http://www.geni.net/resources/rspec/3">
     37  <node client_id="VM_pc423" component_manager_id="urn:publicid:IDN+emulab.net+authority+cm" component_id="urn:publicid:IDN+emulab.net+node+pc423" component_name="pc110" exclusive="false">
     38    <sliver_type name="emulab-xen"/>
     39    <interface client_id="VM:if0">
     40    </interface>
     41  </node>
     42  <node client_id="VM" component_manager_id="urn:publicid:IDN+emulab.net+authority+cm" exclusive="false">
     43    <sliver_type name="emulab-openvz"/>
     44    <interface client_id="VM-0:if0">
     45    </interface>
     46  </node>
     47  <link client_id="lan0">
     48    <component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/>
     49    <interface_ref client_id="VM:if0"/>
     50    <interface_ref client_id="VM-0:if0"/>
     51    <property source_id="VM:if0" dest_id="VM-0:if0"/>
     52    <property source_id="VM-0:if0" dest_id="VM:if0"/>
     53    <link_type name="lan"/>
     54  </link>
     55</rspec>
     56}}}
     57
     58In the above, we have chosen a xen VM (bound to pc423) and a openVZ container to force the LAN to be non-trivial.
     59
     60