Changes between Initial Version and Version 1 of GeniNetworkStitchingSites/GENIFixeEndpoint

03/18/15 15:22:23 (7 years ago)



  • GeniNetworkStitchingSites/GENIFixeEndpoint

    v1 v1  
     1= Fixed End Point Topology Using GENI Stitching =
     3This page captures steps required by GENI Operators to configure a non-GENI resource (aka fixed endpoint) to be an endpoint in a GENI stitched topology.  This procedure is not intended for GENI experimenters. GENI Operators must coordinate with sites contact to get approval for the configuration changes required in this setup, as well as work directly with site contacts for the initial setup of site resource connectivity.  The topology used in this example includes the following:
     7The above topology allows the High School behind the UTC IG rack campus connection to use a GENI stitching path to the USC fixed endpoint. There is no compute resource in the UTC rack, but simply a special nodes for the campus port using a pre-configured VLAN tag for the special sliver_type "emulab-connect" and has a special component_id "interconnect-highschool".
     10== Prerequisites ==
     12Coordination and approval from site contacts are required to get the GENI and non-GENI site connectivity in place.  Once connectivity is in place, stitching must be configured.  This is set in motion by submitting a request to the InstaGENI team [] to add stitching advertisement and to [] to update the AL2S stitching advertisement.  Requests to add stitching endpoints must include this type of [ information].  The request results in a GMOC ticket that covers both AL2S and Stitching Computation Service (SCS) changes.
     14Before you can proceed to create the GENI stitched topology example described in this procedure it is assumed that the following have already taken place:
     16 1. Fixed endpoint VLAN has provisioned from the site to AL2S and that the site link name is known to GPO. In this example ''usc'' is the link and ''3224'' is the VLAN for the fixed endpoint.
     17 2. ACLs have been created in GENI-FOAM group for the fixed endpoint.
     18 3. InstaGENI rack (UTC IG in this example) has been update to advertise its stitching, and has been configured to extend one VLANs to campus interface to the High School. In this example VLAN is ''3514''.
     19 4. AL2S has updated its advertisement RSpec to include the stitching information for the UTG IG rack and USC fixed endpoint.
     20 5. SCS has picked up the topology for the site and the fixed endpoint.
     22You are now ready to proceed to create an RSpec for the stitcher tool.
     24== Creating a Fixed Endpoint Stitching Request RSpec ==
     26Follow these steps to create a request RSpec for the above stitched topology:
     28 1. Add a GENI node for UTC IG campus connection, but __do not__ include a node for the fixed endpoint. This node allows the High School campus endpoint connection through the rack and on to the remote non-GENI site fixed endpoint.  Add:
     30 <node client_id="utc-hc"
     31       component_manager_id=""
     32       component_id=""  exclusive="false" >
     33   <sliver_type name="emulab-connect"/>
     34   <interface client_id="utc-hc:if0">
     35     <ip address="" netmask="" type="ipv4"/> 
     36   </interface>
     37 </node>
     40If you are interested in stitching to a real compute resource in the UTC rack, you can replace the campus node with the following:
     43 <node client_id="utc-hc" component_manager_id="" exclusive="false" >
     44    <sliver_type name="emulab-xen"/>
     45    <interface client_id="utc-hc:if0">
     46      <ip address="" netmask="" type="ipv4"/> 
     47    </interface>
     48 </node>
     51''     Note: The IP address above is specific to the connection to USC, you will use an address that applies to your experiment''[[BR]]
     52''     Note: The sliver_type ''emulab-connect'' was specifically configured for connecting the campus port to the High School. '''
     55 2. Define a link that includes both GENI aggregates (UTC & AL2S) component_manager. Must also include the interface_ref for the rack's GENI node that terminates the link.  Add:
     57 <link client_id="link-utc-hc-usc">
     58   <component_manager name=""/>
     59   <interface_ref client_id="utc-hc:if0" />
     60   <component_manager name=""/>
     61 </link>
     64 3. Get the AL2S advertisement and look for the peering link that maps to the fixed endpoint, in this example ''usc''. This link will become ''hop id="1"''  in the stitching extension path of your RSpec, along with the VLAN that is used for fixed endpoint. Note that the order of the two hops defined in the stitching path is not important, so UTC could be defined first.
     66The AL2S peering link for the USC fixed endpoint is modified to became a hop definition in our request. Note that the ''remoteLinkId'' is not required because the SCS does not care about the ''remoteLinkId''  if it does not point to a known GENI stitching aggregate. So the ''remoteLinkId'' need not be defined in the stitching path.  Add:
     68   <link id="">
     69       <trafficEngineeringMetric>10</trafficEngineeringMetric>
     70       <capacity>10000000</capacity>
     71       <switchingCapabilityDescriptor>
     72         <switchingcapType>l2sc</switchingcapType>
     73         <encodingType>ethernet</encodingType>
     74         <switchingCapabilitySpecificInfo>
     75           <switchingCapabilitySpecificInfo_L2sc>
     76            <interfaceMTU>9000</interfaceMTU>
     77            <vlanRangeAvailability>3224</vlanRangeAvailability>
     78            <suggestedVLANRange>3224</suggestedVLANRange>
     79            <vlanTranslation>true</vlanTranslation>
     80           </switchingCapabilitySpecificInfo_L2sc>
     81         </switchingCapabilitySpecificInfo>
     82       </switchingCapabilityDescriptor>
     83      <capabilities>
     84       <capability>consumer</capability>
     85        <capability>producer</capability>
     86      </capabilities>
     87    </link>
     90    ''Note: The request above uses VLAN 3224. This is specific to the example experiment, you will use a VLAN that applies to your setup''
     92 4. Get the UTC IG advertisement, from which we will use the site link as a ''hop id="2"'' for the campus node that maps VLAN to the High school. Add:
     95   <link id="">
     96      <trafficEngineeringMetric>10</trafficEngineeringMetric>
     97      <capacity>1000000</capacity>
     98      <switchingCapabilityDescriptor>
     99        <switchingcapType>l2sc</switchingcapType>
     100       <encodingType>ethernet</encodingType>
     101       <switchingCapabilitySpecificInfo>
     102         <switchingCapabilitySpecificInfo_L2sc>
     103            <interfaceMTU>9000</interfaceMTU>
     104            <vlanRangeAvailability>3514</vlanRangeAvailability>
     105            <suggestedVLANRange>3514</suggestedVLANRange>
     106            <vlanTranslation>false</vlanTranslation>
     107          </switchingCapabilitySpecificInfo_L2sc>
     108        </switchingCapabilitySpecificInfo>
     109      </switchingCapabilityDescriptor>
     110    </link>
     113''  Note: The example request uses VLAN 3514 that is specific to this experiment, you will use a VLAN that applies to your setup''
     115You now have the request RSpec needed to set up this example topology.  See the complete request RSpec [ stitch-fixedEndpoint.rspec].
     117== Run the Experiment ==
     119A patched version of the stitcher from GCF 2.9 is required to run this experiment.  Using the v2.9 stitcher create the sliver:
     121 $ stitcher createsliver slice-name stitch-fixedEndpoint.rspec  --fixedEndpoint \
     122   --excludehop -o
     125The above command will create a stitcher sliver from UTC IG to AL2S USC fixed-endpoint, and the stitcher will request VLAN 3514 from the UTC IG rack from the available UTC VLAN range of 3500-3514. The IG aggregate allows the inclusion of a 'vlantag' attribute on the link, but other AMs do not like this manifest attribute in a request. To avoid this problem, we specify the ''--excludehop'' to get the desired VLAN. 
     127=== Stitcher excludeHop option ===
     129The stitcher ''--excludehop'' option can be used to accomplish the following path options:
     131 * Exclude a hop URN from any path in the request. For example:
     133    {{{
     134     --excludehop
     135    }}} 
     137    results in the hop specified not being used in any part of the GENI stitching path.
     139 * Exclude a specific VLAN on a specific hop URN.  For examples:
     141    {{{
     142     --excludehop
     143    }}}
     145    results in VLAN ''3512'' being excluded from the potential VLANs to be used on the GENI stitching path at hop ''''.
     147 * Exclude ranges of VLANs on a specific hop URN.  For examples:
     149  {{{
     150   --excludehop,3512-3514
     151  }}}
     153  results in VLAN ''3511'' being used from the potential VLAN range (3500-3514) in the GENI stitching path at hop ''''.