Changes between Initial Version and Version 1 of GENIExperimenter/Tutorials/StitchingTutorial/DesignSetup

03/13/14 09:11:24 (7 years ago)



  • GENIExperimenter/Tutorials/StitchingTutorial/DesignSetup

    v1 v1  
     1= [ GENI Inter-Aggregate Stitching Tutorial] =
     5<div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;">
     6<img id="Image-Maps_5201305222028436" src="" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" />
     7<map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436">
     8<area shape="rect" coords="18,18,135,110" href="" alt="" title=""    />
     9<area shape="rect" coords="180,18,297,111" href="" alt="" title=""    />
     10<area shape="rect" coords="344,17,460,110" href="" alt="" title=""    />
     11<area shape="rect" coords="493,136,495,138" href="" alt="Image Map" title="Image Map" />
     13<!-- Image map text links - End - -->
     18= Step 1: Download and Import Initial Resource Request RSpec =
     20This tutorial starts with an existing RSpec which includes 3 nodes in a linear topology. The resources are un-bound, which means the resources are not affiliated with any rack/aggregate.
     24To get started download the initial RSpec file and import it into the flack to make modification as follows:
     26'''1.''' Download the Rspec named [ 3nodes-1rack.rspec] to your local system
     28'''2.''' Login to the GENI Portal at
     30'''3.''' Go to the [ "Projects"] panel and click on the '' "Create Slice" '' button for the tutorial project. (If you are running this tutorial on your own, you may use any existing project.)  On the resulting page named "Create New Slice" enter a slice name and click on "Create slice" button. For the purpose of this tutorial we will assume the slice is named ''!MySlice'', but you should use a unique name because each slice name must be unique within a project.
     32'''4.''' Once you are on the slice page ''(Home → Project !MyProject → Slice !MySlice)'' select the ''"Launch Flack"'' button. (You must wait for all aggregates to show up in the !MySlice panel before you can proceed.
     34'''5.''' Select the pull-down named ''"Import"'' and choose ''"Import from file"'' option:
     36     [[Image(LuisaSandbox/StitchingTutorial/attachments:import-from-file.jpg)]]
     38'''6.''' Navigate to the file location and choose select the 3nodes-1rack.rspec file.
     40'''7.''' You will see a pop-up that states no manager is associated with the resource, click ''"OK"'' and another pop-up will have you select an aggregate manager, select one of the two aggregate manager assigned to you and click on ''"Accept"'' button.  (If you are running this tutorial on your own, you may use any aggregate found on the [ GENI Network Stitching Sites] page.
     42     [[Image(LuisaSandbox/StitchingTutorial/attachments:import-add-aggr.jpg)]]
     45= Step 2: Modify RSpec to include 2 Aggregates with stitched link =
     47Now that you have imported the RSpec, we will modify it to include a stitched link. Modification in this section will result in the following topology:
     51To get to the above topology, we must make changes to the resources imported into flack.  We will now modify ''"right-host"'' to become part of a different rack make modify its link to a stitched link.
     53'''8.''' Click on the ''"right-server"'' VM information button[[Image(LuisaSandbox/StitchingTutorial/attachments:info.jpg)]].
     55'''9.''' In the host details panel select the second manager manager that was assigned to you at the beginning of the tutorial and click on the ''"Apply"'' button.  (If you are running this tutorial on your own, you may use another site aggregate found on the [ GENI Network Stitching Sites] page. Remember this cannot be the same as the aggregate selected initially)
     57'''10.''' You will now see that the link from the ''"client"'' VM to ''"right-server"'' VM is now a gre-tunnel1 link.  Select the gre-tunnel1 link information button[[Image(LuisaSandbox/StitchingTutorial/attachments:info.jpg)]] to modify the link type to ''"stitched"'' and click ''"Apply"'' button.
     59     [[Image(LuisaSandbox/StitchingTutorial/attachments:gre-to-stitched.jpg)]]
     61'''11.''' You should now see that the topology has changed and that between the ''"client"'' VM and the ''"right-server"'' VM the link is now named ''"stitched1"''.
     64'''12.''' We will now export this topology to a file by selecting the "View" pull-down and choosing "Preview requested document(s)". You will now choose "Save to file" to export the RSpec we just modified. For the purpose of this experiment we will assume the file is saved to ''"MyTopology.rspec"'', but you can choose any name or location, just make a not of it.
     66     [[Image(LuisaSandbox/StitchingTutorial/attachments:export-to-file.jpg)]]
     69We are now ready to use stitcher to create the stitched topology for our experiment!
     73= Step 3: Run stitcher tool to get resources =
     75The stitcher tools delivers the same features as the omni tool, but with one major difference, the stitcher will submit sliver request at all aggregate in your requests RSpec. Let's now set up slivers for the request RSpec generated in the previous section:
     77'''13.'''  Use stitcher to create a sliver and using the slice that we created in flack.  The request will use the RSpec that was saved to file in the setup steps:
     79$ stitcher createsliver MySlice MyTopology.rspec
     8011:48:18 INFO     stitcher: Loading agg_nick_cache file '/Users/lnevers/.gcf/agg_nick_cache'
     8111:48:18 INFO     stitcher: Loading config file /Users/lnevers/.gcf/omni_config
     8211:48:18 INFO     stitcher: Setting option useSliceMembers based on omni_config setting
     8311:48:18 INFO     stitcher: Using control framework portal
     8411:48:18 INFO     stitcher: Member Authority is (from config)
     8511:48:18 INFO     stitcher: Slice Authority is (from config)
     8611:48:19 INFO     stitcher: Checking that slice MySlice is valid...
     8711:48:19 INFO     stitcher: Slice expires on 2014-03-17 14:57:35 UTC
     8811:48:20 INFO     stitcher: Stitched reservation will include resources from these aggregates:
     8911:48:20 INFO     stitcher:     <Aggregate wisconsin-ig>
     9011:48:20 INFO     stitcher:     <Aggregate stanford-ig>
     9111:48:20 INFO     stitcher:     <Aggregate ion>
     9211:48:20 INFO     stitch.Aggregate:
     93        Stitcher doing createsliver at
     9411:48:38 INFO     stitch.Aggregate: Allocation at <Aggregate wisconsin-ig> complete.
     9511:48:38 INFO     stitch.Aggregate:
     96        Stitcher doing createsliver at
     9711:48:58 INFO     stitch.Aggregate: Allocation at <Aggregate stanford-ig> complete.
     9811:48:58 INFO     stitch.Aggregate:
     99        Stitcher doing createsliver at
     10011:49:43 INFO     stitch.Aggregate: DCN AM <Aggregate ion>: must wait for status ready....
     10111:49:43 INFO     stitch.Aggregate: Pause 30 seconds to let circuit become ready...
     10211:50:20 INFO     stitch.Aggregate: DCN circuit 74871 is ready
     10311:50:27 INFO     stitch.Aggregate: Allocation at <Aggregate ion> complete.
     10411:50:27 INFO     stitch.launcher: All aggregates are complete.
     10511:50:27 INFO     stitcher: Saved combined reservation RSpec at 3 AMs to file MySlice-manifest-rspec-stitching-combined.xml
     106Stitching success: Reserved resources in slice MySlice at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 1 link(s).
     110We are now ready to run the experiment!
     112= [ Introduction] =
     113= [ Next:  Execute] =