Changes between Version 120 and Version 121 of GENIExperimenter/ExperimentExample-OF-FOAM
- Timestamp:
- 04/26/12 10:26:42 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/ExperimentExample-OF-FOAM
v120 v121 11 11 Omni tools are used to reserve resources in each of the site's !FlowVisor !OpenFlow Aggregate Manager (FOAM) and GENI Aggregate Managers. Steps required to set up this !OpenFlow experiment are detailed in this page: 12 12 1. Authentication and Omni tools configuration 13 2. Determine Resources Availability 14 3. Define Compute Resources RSpecs 15 4. Define !OpenFlow Network Resources RSpecs 16 5. Create Slice and Request Resources 17 6. Run Experiment 18 7. Release Resources 13 2. Reserve IP Subnet 14 3. Determine Resources Availability 15 4. Define Compute Resources RSpecs 16 5. Define !OpenFlow Network Resources RSpecs 17 6. Create Slice and Request Resources 18 7. Run Experiment 19 8. Release Resources 20 21 Note: IP Subnet reservation is only required for this experiment because MyPLC resources are used (layer 3). 19 22 20 23 Note: FOAM sites must be federated in order to trust a Clearinghouse. This is an !OpenFlow administrator task that must take place before any of the user !OpenFlow operations can take place. 21 24 22 == Authentication and Omni tools configuration ==25 == 1. Authentication and Omni tools configuration == 23 26 24 27 This example assumes that GENI credentials have been set up as detailed in the [wiki:HowToUseOmni#a1.GetGENICredentials GENI Credentials] section of the [wiki:HowToUseOmni Omni how-to] page. … … 65 68 A complete list of Aggregate managers is compiled in the [http://groups.geni.net/geni/wiki/GeniAggregate GENI Aggregate] page, if your site is not listed on this page you should contact your site administrator, or help@geni.net. 66 69 67 == Reserve GENI IP subnet ==70 == 2. Reserve GENI IP subnet == 68 71 69 72 In the Meso-scale network a layer 3 experiment requires its own separate IP subnet in order to control all traffic without interfering with traffic from other experiments. Before you start this experiment, you need to request an IP subnet from the gpo-infra@geni.net mail list along with a duration for the subnet reservation. To view the current list of subnets and their current allocation see the [http://groups.geni.net/geni/wiki/NetworkCore/SubnetReservations GENI Network Core Subnet] page. 70 73 71 74 72 == Determine Resources Availability ==75 == 3. Determine Resources Availability == 73 76 74 77 Each of the 3 sites requires an !OpenFlow RSpec and a compute resource RSpec. Also, an !OpenFlow RSpec is required for the GENI Core (NLR in this example). … … 84 87 The experiment captured in this page uses the BBN, Clemson, Wisconsin and NLR Aggregates. For a complete list of available aggregates see the [http://groups.geni.net/geni/wiki/GeniAggregate GENI Aggregates] page. 85 88 86 == Define Compute Resources RSpecs ==89 == 4. Define Compute Resources RSpecs == 87 90 88 91 This experiment uses Omni V1.6.1 to set up the experiment. As a first step, the experimenter determines the available compute resources at each site. Following are the omni commands issued to get the advertisements of available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates: … … 155 158 156 159 157 == Define !OpenFlow Network Resources Rspecs ==160 == 5. Define !OpenFlow Network Resources RSpecs == 158 161 159 162 To write an OF RSpec you must determine the end-to-end OF path that will be used for the experiment. This section describes this process, which is comprised of the following steps: … … 639 642 640 643 641 == Setup Experiment ==644 == 6. Setup Experiment == 642 645 643 646 Using the !OpenFlow and compute resource RSpecs we defined above, we can now set up an experimennt with Omni. First, we create a slice using the GPO Clearinghouse credentials as defined in the [wiki:GENIExperimenter/ExperimentExample-OF-FOAM#AuthenticationandOmnitoolsconfiguration Omni configuration]. Note, you should choose a slice name that is meaningful to you. Then, we create a sliver for each resource aggregate. In this example there are 4 !OpenFlow aggregates (one per site plus one for the GENI core) and 3 compute resource aggregates (3 MyPLC), which maps to creating 7 slivers. The following commands are executed to set up the experiment: … … 693 696 In the scenario captured in this page, there are 4 sliver approval notifications, one from each of the FOAM aggregates (BBN, Clemson, NLR and Wisconsin). 694 697 695 == Run Experiment ==698 == 7. Run Experiment == 696 699 697 700 Once your flowspace has been opted in, you should be able login to each of the MyPLC hosts and exchange traffic over the approved flows. Simply SSH into one of the hosts and ping any of the other hosts to verify connectivity. If you have connectivity between the allocated hosts, you may start your experiment, if you do not have connectivity, contact [mailto:help@geni.net]. … … 758 761 You can now run an experiment! 759 762 760 == Release Resources ==763 == 8. Release Resources == 761 764 762 765 When the experiment is completed, you should release the resources by deleting the sliver for each of the resource aggregates in the Experiment. In the example experiment in this page, the following commands should be issued to release resources:
