Changes between Version 5 and Version 6 of GEMINI/Tutorial/GEC15/ActiveMeasurements
- Timestamp:
- 10/23/12 11:29:53 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEMINI/Tutorial/GEC15/ActiveMeasurements
v5 v6 98 98 99 99 100 == == Visualize Measurement Data ====100 == Visualize Measurement Data == 101 101 102 102 Doing the user experiment should have given the scheduled active measurements enough time to gather some data. We also generated some heavy traffic during our iperf data transfers. This section of the tutorial covers how to visualize the data for regular active tests. We will also check the passive monitoring graphs again to see how the iperf transfers affected our hosts. 103 103 104 === == Accessing perfAdmin for Active Measurements Data =====104 === Accessing perfAdmin for Active Measurements Data === 105 105 106 106 To query and visualize the active measurements data we will use perfAdmin. perfAdmin is a web service that is able to query perfSONAR services and plot relevant data. You can access a perfAdmin instance running on your slice through the portal or by going to https://<gn node>/perfAdmin (note the capitalization). … … 136 136 While it's good to be able to query each service for its data, sometimes it's better to have access to all measurements in our slice on the same page. perfAdmin provides this option on the left menu for each of the regular testing measurement types currently supported (One-way Delay, Ping and Throughput). When we access one of these pages, perfAdmin will query each known service storing measurements of the given type for all the related metadata. It then builds a single page that we can use to query for a particular measurement's data. For example, if we go to the One-Way Delay page we should be able to see the measurements stored in both nodes VM1 and VM4. 137 137 138 139 140 ===== Changes in Passive Monitoring Graphs =====141 142 Using the GEMINI Portal, you can also view the changes in Passively monitored Network traffic and system resources when running any experiment or traffic or any other kind of load on the nodes in your slice.143 [[BR]]144 [[BR]]145 146 138 147 148 === Move selected collected measurements and other artifacts from storage service to long-term archive service ===149 150 - identify archived objects with persistent identifier151 152 - include policy for sharing with others153 154 - allow retrieval for further analysis and visualization155 156 157 === Release experiment resources ===