Changes between Version 20 and Version 21 of GEC21Agenda/ChoiceNet/run_tests_part2


Ignore:
Timestamp:
10/21/14 11:00:58 (5 years ago)
Author:
xinming@umass.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC21Agenda/ChoiceNet/run_tests_part2

    v20 v21  
    11Navigation: [wiki:GEC21Agenda/ChoiceNet/start Up]
    22
    3 In this section we will use a different type of !ChoiceNet service to route and forward packets across the slice.  In particular, we will use an SDN-based (i.e., OpenFlow-based) !ChoiceNet service to forward packets.  During the [wiki:GEC21Agenda/ChoiceNet/gt_tool Configure and Install !ChoiceNet Software] step we already downloaded and configured the software needed for this section, consequently the next step is to run applications that will make use of this new SDN-based service.
     3In this section we will use a different type of !ChoiceNet service to route and forward packets across the slice.  In particular, we will use an SDN-based (i.e., OpenFlow-based) !ChoiceNet service to forward packets.  During the [wiki:GEC21Agenda/ChoiceNet/gt_tool Configure and Install ChoiceNet Software] step we already downloaded and configured the software needed for this section, consequently the next step is to run applications that will make use of this new SDN-based service.
    44
    55----
     
    77
    88
    9 The SDN-based implementation has an SDN controller that knows the network topology and detect the path services. It also has a marketplace server which accepts the service advertisement from controller and handles the user request.
     9The SDN-based implementation has an SDN controller that knows the network topology and detect the path services. It also has a Path Broker server which accepts the service advertisement from controller and handles the user request.
    1010
    11 Although the controller and marketplace are services offered by providers and conceptually should be run on provider machines, for purposes of this tutorial they are located on H1 (to reduce the number of VMs in the slice).
     11Although the controller and Path Broker are services offered by providers and conceptually should be run on provider machines, for purposes of this tutorial they are located on H1 (to reduce the number of VMs in the slice).
    1212
    1313
    14 Like we did in the previous section, we will be using the ssh terminal sessions to nodes H1 ('''TERMINAL 1''' ) and H2 ('''TERMINAL 2'''). ''' [wiki:GEC21Agenda/ChoiceNet/terminalsetup#Interactingwithyourslice Section 3 has the instructions about how to open terminals to H1 and H2] '''
     14Like we did in the previous section, we will be using the ssh terminal sessions to nodes H1 ('''TERMINAL 1''' ) and H2 ('''TERMINAL 2'''). Section 3 has  [wiki:GEC21Agenda/ChoiceNet/terminalsetup#Interactingwithyourslice the instructions about how to open terminals to H1 and H2].
    1515
    16 We will begin by starting the controller and marketplace on H1 ('''TERMINAL 1''').
     16We will begin by starting the controller and Path Broker on H1 ('''TERMINAL 1''').
    1717
    1818
     
    2424
    2525
    26 this will start both the marketplace and controller.
     26this will start both the Path Broker and controller.
    2727
    28 Open up two ssh session terminals to the H2 Node ( we can call them '''TERMINAL 2''' and '''TERMINAL 3''' ). First run the !ChoiceNet App on '''TERMINAL 2'''. The !ChoiceNet App will communicate with marketplace to request for path service and deal with payment.
     28Open up two ssh session terminals to the H2 Node ( we can call them '''TERMINAL 2''' and '''TERMINAL 3''' ). First run the !ChoiceNet App on '''TERMINAL 2'''. The !ChoiceNet App will communicate with Path Broker to request for path service and deal with payment.
    2929
    3030'''On TERMINAL 2 (H2 node)'''
     
    4040''' Password ''': customer
    4141
    42 After login, the app will intercept any TCP SYN packets with destination IP 10.0.0.0/8 and destination port 8080 or 443. Once it intercepts a packet, it communicates with the marketplace and requests for a path service with 3-minute duration. This means it is compatible with almost any existing network applications, here we will use wget and mplayer as two examples.
     42After login, the app will intercept any TCP SYN packets with destination IP 10.0.0.0/8 and destination port 8080 or 443. Once it intercepts a packet, it communicates with the Path Broker and requests for a path service with 3-minute duration. This means it is compatible with almost any existing network applications, here we will use wget and mplayer as two examples.
    4343
    4444----
     
    7575[[Image(screenshot_SDN_03.jpg, 100%)]]
    7676
    77 After you have paid, click the "Return to !marketplace@choicenet.info". After the webpage redirection, the marketplace will be notified about this payment, and the download should start. You will see the output on TERMINAL 3:
     77After you have paid, click the "Return to !marketplace@choicenet.info". After the webpage redirection, the Path Broker will be notified about this payment, and the download should start. You will see the output on TERMINAL 3:
    7878
    7979