Changes between Version 20 and Version 21 of GEC21Agenda/ChoiceNet/run_tests_part2
- Timestamp:
- 10/21/14 11:00:58 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEC21Agenda/ChoiceNet/run_tests_part2
v20 v21 1 1 Navigation: [wiki:GEC21Agenda/ChoiceNet/start Up] 2 2 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.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. 4 4 5 5 ---- … … 7 7 8 8 9 The SDN-based implementation has an SDN controller that knows the network topology and detect the path services. It also has a marketplaceserver which accepts the service advertisement from controller and handles the user request.9 The 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. 10 10 11 Although the controller and marketplaceare 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).11 Although 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). 12 12 13 13 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] '''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'''). Section 3 has [wiki:GEC21Agenda/ChoiceNet/terminalsetup#Interactingwithyourslice the instructions about how to open terminals to H1 and H2]. 15 15 16 We will begin by starting the controller and marketplaceon H1 ('''TERMINAL 1''').16 We will begin by starting the controller and Path Broker on H1 ('''TERMINAL 1'''). 17 17 18 18 … … 24 24 25 25 26 this will start both the marketplaceand controller.26 this will start both the Path Broker and controller. 27 27 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 marketplaceto request for path service and deal with payment.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 Path Broker to request for path service and deal with payment. 29 29 30 30 '''On TERMINAL 2 (H2 node)''' … … 40 40 ''' Password ''': customer 41 41 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 marketplaceand 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.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 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. 43 43 44 44 ---- … … 75 75 [[Image(screenshot_SDN_03.jpg, 100%)]] 76 76 77 After you have paid, click the "Return to !marketplace@choicenet.info". After the webpage redirection, the marketplacewill be notified about this payment, and the download should start. You will see the output on TERMINAL 3:77 After 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: 78 78 79 79