| | 143 | + perfSONAR is a multi-domain performance monitoring framework, which defines a set of protocol standards for sharing data between measurement and monitoring systems [[BR]] |
| | 144 | |
| | 145 | Architecture: [[BR]] |
| | 146 | + Interoperable network measurement middleware designed as a Service Oriented Architecture (SOA): [[BR]] |
| | 147 | - Components are Web Services (WS) based [[BR]] |
| | 148 | + Several unique components and design considerations, all of which operate in a cooperative yet independent manner [[BR]] |
| | 149 | - Each functionality is separated into a specific function [[BR]] |
| | 150 | - Clients and servers interact through scripted, XML Based protocols [[BR]] |
| | 151 | - Measurement data is encoded in expressive XML formats [[BR]] |
| | 152 | |
| | 153 | Components: [[BR]] |
| | 154 | + Infrastructure [[BR]] |
| | 155 | - Lookup Service [[BR]] |
| | 156 | - Topology Service [[BR]] |
| | 157 | - Authentication Service [[BR]] |
| | 158 | + Services [[BR]] |
| | 159 | - Measurement Point (MP) Service [[BR]] |
| | 160 | - Measurement Archive (MA) Service [[BR]] |
| | 161 | - Resource protector [[BR]] |
| | 162 | + Analysis and visualization [[BR]] |
| | 163 | |
| | 164 | Open protocols and schema: [[BR]] |
| | 165 | + Base network measurement schema[[BR]] |
| | 166 | - OGF Network Measurement Working Group[[BR]] |
| | 167 | + Topology Schema[[BR]] |
| | 168 | - OGF Network Markup Language (NML-)WG[[BR]] |
| | 169 | - Includes Topology Network ID[[BR]] |
| | 170 | + perfSONAR Protocol Documents[[BR]] |
| | 171 | - OGF Network Measurement and Control (NMC-)WG[[BR]] |
| | 172 | |
| | 173 | Base network measurement schema:[[BR]] |
| | 174 | + Measurement Data, a set of measurement events that have some value or values at a particular time[[BR]] |
| | 175 | + Measurement Metadata, the details about the set of measurement data[[BR]] |
| | 176 | |
| | 177 | Measurement metadata:[[BR]] |
| | 178 | + Subject (Noun)[[BR]] |
| | 179 | - The measured/tested entity (who)[[BR]] |
| | 180 | - E.g. A pair of hosts (end-point-pair), or a Layer 3 interface[[BR]] |
| | 181 | + EventType (Verb)[[BR]] |
| | 182 | - What type of measurement, value, or event occurred[[BR]] |
| | 183 | - Characteristic, tool output, or generic event[[BR]] |
| | 184 | - E.g. latency, bandwidth, utilization, or simply iperf[[BR]] |
| | 185 | + Parameters (Adjectives and Adverbs)[[BR]] |
| | 186 | - How, or under what conditions, did this event occur?[[BR]] |
| | 187 | - E.g. buffer sizes used, TCP vs ICMP packets[[BR]] |
| | 188 | + Key[[BR]] |
| | 189 | - Shortcut substituted in place of previous three items[[BR]] |
| | 190 | - No predefined format[[BR]] |
| | 191 | |
| | 192 | Measurement data: |
| | 193 | + Datum: The actual result (values) of measurement. [[BR]] |
| | 194 | - Can contain time (e.g. a Time element or attribute).[[BR]] |
| | 195 | - Existence of an event might point to the case where there no additional value[[BR]] |
| | 196 | - As in “Link up/down” or threshold events[[BR]] |
| | 197 | + Time: Representation of a time stamp or time range in a specified format.[[BR]] |
| | 198 | - Must be extensible since even agreement about the right structure is not easy, e.g. UNIX timestamp vs NTP time[[BR]] |
| | 199 | |
| | 200 | |
| | 201 | Schema namespaces and extensibility:[[BR]] |
| | 202 | + A namespace: http://ggf.org/ns/nmwg/base/2.0/[[BR]] |
| | 203 | - MAY NOT be a URL[[BR]] |
| | 204 | + We encode the measurement/event type in the namespace (and as a standalone element)[[BR]] |
| | 205 | + We use Data and Metadata elements and vary the namespaces of the specific elements[[BR]] |
| | 206 | + Extensibility achieved through hierarchy with delegation[[BR]] |
| | 207 | - Similar to OIDs in the IETF management world[[BR]] |
| | 208 | + The NM-WG has a hierarchy of network characteristics[[BR]] |
| | 209 | - Good starting point[[BR]] |
| | 210 | - E.g. http://ggf.org/ns/nmwg/characteristic/utilization/2.0[[BR]] |
| | 211 | - E.g. http://ggf.org/ns/nmwg/characteristic/bandwidth/achievable/2.0[[BR]] |
| | 212 | + However, not all tools are cleanly mapped onto the Characteristic space[[BR]] |
| | 213 | - Often a matter of some debate[[BR]] |
| | 214 | + Organization-rooted tools namespace addresses this[[BR]] |
| | 215 | - Easy to add new tools in organization-specific namespaces[[BR]] |
| | 216 | - E.g. http://ggf.org/ns/nmwg/tools/nuttcp/2.0[[BR]] |
| | 217 | |
| | 218 | |
| | 219 | Topology Schema: [[BR]] |
| | 220 | + Topology schema grew from network measurement description [[BR]] |
| | 221 | - Reusable “Subject” elements for common cases [[BR]] |
| | 222 | - Also reduces redundancy [[BR]] |
| | 223 | - Relationships between measurement Subjects [[BR]] |
| | 224 | + Structured by layers and the same elements recurring there (Base, L2, L3, L4) [[BR]] |
| | 225 | - networks as graphs[[BR]] |
| | 226 | + Elements:[[BR]] |
| | 227 | - Domain[[BR]] |
| | 228 | - Node[[BR]] |
| | 229 | - Port[[BR]] |
| | 230 | - Link[[BR]] |
| | 231 | - Network[[BR]] |
| | 232 | - Path[[BR]] |
| | 233 | - Service[[BR]] |
| | 234 | + Varied by namespaces (extensibility)[[BR]] |
| | 235 | - Reuse visualization logic, etc.[[BR]] |
| | 236 | - Validate layer- or technology-specific attributes[[BR]] |
| | 237 | + Used by perfSONAR, IDC Protocol (ION, OSCARS, AutoBAHN), Phoebus[[BR]] |
| | 238 | - Currently calling it the UNIS Topology Schema [[BR]] |
| | 239 | + OGF NML-WG to unify NDL and UNIS Topology schema[[BR]] |
| | 240 | - Happening as we speak at OGF28[[BR]] |
| | 241 | |
| | 242 | LAMP objectives:[[BR]] |
| | 243 | + Collaborate on defining a common but extensible format for data storage and exchange for GENI I&M systems[[BR]] |
| | 244 | - Use perfSONAR NM-WG schema as starting point[[BR]] |
| | 245 | - Identify new characteristics/tools namespaces[[BR]] |
| | 246 | + Develop a representation of GENI topology to be used to describe measurements and experiment configuration[[BR]] |
| | 247 | - UNIS topology schema can be easily extended [[BR]] |
| | 248 | + Collaborate with related GENI measurement and security projects on a common GENI I&M architecture[[BR]] |
| | 249 | - The new GENI I&M Arch. Draft defines very similar services (MP, MC, MDA, MAP), and new ones (MO)[[BR]] |
| | 250 | - perfSONAR is a good starting point, not currently a final solution (for GENI); [[BR]] |
| | 251 | - Use cases have been different, but much can be reused and the framework can be extended[[BR]] |
| | 252 | |
| | 253 | |
