Changes between Version 36 and Version 37 of GEMINIv1.1Tutorial

Timestamp:

10/23/12 10:48:04 (12 years ago)

Author:

Ahmed El-Hassany

Comment:

--

GEMINIv1.1Tutorial

@@ -393 +393 @@
 [[Image(s6.png,border=1)]]
 
+
+
+
+=== 3) Configure I&M tools and experiment services ===
+
+==== 3.1)  Configuring Passive measurements ====
+
 [wiki:GeminiPortal Intro To Gemini Portal]
-[[BR]]
-[wiki:PathControllerDemo Path Controller]
-
-=== 3) Configure I&M tools and experiment services ===
-
-==== 3.1)   Configuring Active Measuremens ====
+
+
+==== 3.2)   Configuring Active Measuremens ====
 
 
@@ -409 +413 @@
 
 
-===== 3.1.1 Accessing pSConfig UI =====
+===== 3.2.1 Accessing pSConfig UI =====
 
 To configure active measurements we access the pSConfig Web UI. You can find the URL by clicking on the MC node on the GEMINI portal, or by going to https://<gn node>/psconfig.
@@ -427 +431 @@
 [[Image(0-unis.png)]]
 
-===== 3.1.2 Enabling Services =====
+===== 3.2.2 Enabling Services =====
 
 After we've made sure to have a recent copy of the topology information, we can move on to the Manage Services administration page. On this page we will enable the services required to perform on-demand and regularly scheduled tests. We start by enabling the  one-way latency services on VM1. Make sure to save the changes before continuing to the next node.
@@ -453 +457 @@
 
 
-==== 3.2 Configuring Regular Active Measurements ====
+==== 3.3 Configuring Regular Active Measurements ====
 
 Enabling the OWAMP and BWCTL daemons is all we need to perform on-demand active measurements. However, it's usually better to have active measurements running regularly to analyze the performance over time. Throughput and ping tests can be scheduled with a given interval (e.g. every 30 minutes). One-way delay tests are scheduled as a stream (a constant amount of packets is sent per second). 
@@ -482 +486 @@
 [[Image(10-unis-push.png)]]
 
-===== 3.2.1 Applying the Configuration =====
+===== 3.3.1 Applying the Configuration =====
 
 pSConfig will pull the node's configuration from UNIS every 30 minutes (from the time it was started, not hh:00 and hh:30). Since we don't want to wait this long to start gathering data, we can restart pSConfig on each node by clicking the Apply Config link. This is achieved by ssh'ing to the node and restarting pSConfig, so errors are usually ssh related.
@@ -493 +497 @@
   
 === 4)  Run and orchestrate I&M services and experiment services to complete run of experiment ===
-
-
-4.1)  Initial setup:  start basic host measurements and basic ping active network measurements
-
- - objectives:
-   - verify functionality of hosts 
-   - verify topology of slice
-
- - observe measurements with a real-time presentation service
- 
- - continue measurements throughout duration of the test/tutorial/experiment
- 
- - at completion: 
-   - functionality of hosts and topology of slice has been verified throughout duration of the experiment
- 
- 
-4.2)  Continuity test:  for a limited time, run iperf active network measurements 
-
- - objectives:
-   - verify ability of slice to carry traffic expected from experiment 
-
- - observe measurements with a real-time presentation service
- 
- - once satisfactory measurements have been observed, stop continuity test 
- 
- - at completion: 
-   - capability of slice to carry traffic expected from experiment has been verified
-
-   
-4.3)  Instrument and run experiment:  
-
- - objectives:
-   - gather measurements during experiment that allow experiment goals to be met
-   
- - include desired measurement points within hosts and/or experiment services to instrument test/tutorial/experiment
- 
- - begin to run and orchestrate measurement services
- 
- - begin to run and orchestrate experiment services
- 
- - observe measurements with a real-time presentation service, to verify expected operation of experiment
- 
- - collect all measurements for duration of experiment
- 
- - stop experiment services, when this run of the experiment has been completed
- 
- - stop measurement services
- 
- - at completion:
-   - one run of experiment has been completed
-   - real-time look at measurements has verified expected operation of experiment
-   - a full set of measurements has been collected, for later analysis and presentation
-   - collected measurements have been transferred to storage service, so that slice resources can be released (if desired) 
-   
-4.4)  Store collected measurements and other artifacts from test/tutorial/experiment in storage service 
-
- - at completion:
-   - collected measurements and other artifacts have been transfered to storage service
-   - collected measurements and other artifacts are available for later analysis
-   - slice resources can then be released at any time, without loss of any measurements or artifacts
-   
+[[BR]]
+[wiki:PathControllerDemo Path Controller]
+
+
 === 5)  Analyze and visualize measurement results after completing run of experiment ===