Monitoring in GENI with Periscope (and other related updates)

Transcription

1 Monitoring in GENI with Periscope (and other related updates) Martin Swany Associate Professor of Computer Science, School of Informatics and Computing Associate Director, Center for Research in Extreme Scale Technology (CREST) Indiana University

2 perfsonar-ps Topology Service (TS) Lookup Service (LS) Measurement Point (MP) Various perfsonar-ps components created in a distribution called the perfsonar Toolkit supported by Internet2, ESnet, and Indiana U. Initial support from the NSF via a grant to U. Delaware perfsonar-ps at the time was the implementation developed by U. Delaware, Internet2 and ESnet Measurement Archive (MA)

3 LAMP (created Periscope) Unified Network Information Svc (UNIS) TS LS Measurement Point (MP) Measurement Archive (MA) GENI GENI GENI GENI Periscope Portal perfsonar MA and MP were made AuthN/AuthZ aware extract X.509 certs from GENI credentials perfsonar LS and TS merged into Periscope UNIS and made GENI-aware Auth Rspec Periscope Portal created to configure experiments, cache and display topology and performance data

4 Periscope Unified Network Information Svc (UNIS) TS LS Measurement Point (MP) Measurement Archive (MA) Auth Auth Auth Auth Auth Periscope Portal Measurement Store (MS) BLiPP Reimplementation of the perfsonar architecture In Python Speaks both perfsonar classic and our RESTful re-implementation of the perfsonar protocols Implemented lightweight host and application probes called Basic Lightweight Periscope Probes (BLiPP) Using LBL s NetLogger JSON Meas. Store Periscope has been used in other projects and collaborators Notably LBL/ISI for STAMPEDE and FNAL/BNL in ESCPS

5 Unified Network Information Service (UNIS) Unified network and service topology Services are just another graph annotation Makes it is easier to discover topologically appropriate services (services close to a path) Pub/sub for changes to topology

6 UNIS Represents the multi-layer topology as a multigraph Reusing the same primitive types with layerspecific annotations

7 Periscope: BLiPP Python Measurement Point with an extensible probe mechanism Support for the standard active measurement tools Various system variables Collects NetLogger data from application instrumentation Gets configuration information from UNIS

8 HELM Conflict-Free Active Measurement Scheduling for Shared Network Resource Management Miao Zhang, Martin Swany, Adithya Yavanamanda, and Ezra Kissel To appear in IFIP/IEEE Int l Symposium on Integrated Network Management (IM2015) Probe interference affects validity Critical as we look toward more automated alarms/triggers Virtual resources hide the real topology This was always true, but the proliferation of software-defined everything exacerbates the problem

9 HELM Goal: specify an aggregate measurement set (mesh) and have something figure it out Configure mesh to avoid conflict at all layers

10 UNIS Topology for HELM Gather topology from published router configuration perfsonar Topology Service instances On-demand traceroutes OpenFlow controllers Normalize into UNIS graph Tolerates incomplete information, but we can always form a graph

11 Graph Coloring Common in scheduling conflicting measurements need to have a different color minimize colors for most compact schedule Based on the Path of a measurement, we can create a conflict graph Unfortunately, our graphs are not perfect graphs (chordal, trapezoidal) We hoped they were as it allows an efficient, optimal solution Implemented a heuristic: smallest-last, greedy coloring

12 Experiments Randomly selected 300 pairwise measurement points from Internet2 and ESnet hosts Active throughput test mesh (iperf) Probes have an edge in the figure if they have a conflict and require a distinct color Reasonable runtime on relatively small machine

13 Measuring in a sliced Network World Goal: prototype diagnostic services that perform fault localization in reaction to observed network degradation within multi-layered networks Working with U. Utah and ESnet Openflow slices on top of virtual circuits (ESnet OF testbed, GENI, OSCARS and AL2S/OESS) Fully represent topology and relationships between layers (UNIS) Shared model and runtime for scheduling active measurements within topology (HELM)

14 Measuring in a sliced Network World When a fault is detected at monitoring agent: 1. Measurement metadata is queried for affected endpoints within topology description. 2. Through path decomposition, additional measurement points (MPs) are selected along end-toend path. 3. Each MP may probe the path bidirectionally along the underlying physical link, virtual circuit, or OF slice depending on connectivity. 4. Probe traffic to endpoints within the slice require reactive OF switch configuration, the details of which are referenced from the topology service and drive the OF controller interface. 5. Diagnostic probe data is analyzed to isolate the sub-path responsible while correlating with existing measurements across the known topology.

15 Small device network sensors Lots of ARM hacking in my Operating Systems class Lightweight, non-linux OS work Various ARM boards support functionality with the potential to increase the fidelity and decrease the overhead of measurements Some of which can be exposed in Linux, so that isn t a requirement Xilinx Zynq is a dual core Cortex A9 with FPGA logic on-die 15

16 X-Gene (ARM64) Development Board 8 core ARM64 (Cortex A9) 1 x 10GE w/ SFP+ 2 x 1GE 1 x PCI-E 8x ~$1200

17 hot off the bench Experiments Throughput in Gb/s Latency in ms Throughput

18 Ongoing work Automatic configuration and coordination of measurements Multi-layer, virtual environments Measurement correlation, derivation UNIS expressivity, scalability Small network probes Drive need for scalability and automatic configuration End to end performance fault diagnosis Relate measurement data to application performance