Skip to content

Latest commit

 

History

History
234 lines (148 loc) · 8.68 KB

README.md

File metadata and controls

234 lines (148 loc) · 8.68 KB
Raw

Project Proposal: End-to-End Tracing, Ceph Tracing

Authors:

  • Golsana Ghaemi
  • Bowen Song
  • Oindrilla Chatterjee
  • Aditya Singh

Mentors:

  • Mania Abdi
  • Raja Sambasivan
  • Peter Portante

Project Video

https://youtu.be/suZOpLZELwU

Configuring Ceph with Blkin

  1. ssh into VM1 where Ceph is Deployed ssh [email protected] -A

  2. Go to the build folder cd ceph/build

  3. Startup Ceph with desired configurations OSD=3 MON=3 RGW=1 ../src/vstart.sh -n

  4. Stop Ceph so that the tracepoints can be enabled.: /home/centos/ceph/src/stop.sh

  5. Start up an Lttng session and enable tracepoints

lttng create blkin-test

lttng enable-event --userspace zipkin:timestamp

lttng enable-event --userspace zipkin:keyval

ttng start

  1. Startup Ceph again OSD=3 MON=3 RGW=1 ../src/vstart.sh -n

  2. To resume the creation of the Ceph virtual cluster, run this parallely ~/ceph/build/bin/ceph-mgr -i x -c ~/ceph/build/ceph.conf

  3. Now put something in using rados, check that it made it, get it back, and remove it

./bin/rados mkpool test-blkin

./bin/rados put test-object-1 ../src/vstart.sh --pool=test-blkin

./bin/ceph osd map test-blkin test-object-1

./bin/rados get test-object-1 ./vstart-copy.sh --pool=test-blkin

md5sum vstart*

./bin/rados rm test-object-1 --pool=test-blkin

  1. Now stop Lttng session and see what was collected lttng stop

  2. To view the traces lttng view

Vision and Goals Of The Project

This project focuses on enabling a strong and open source tracing infrastructure for Ceph, a novel open source high-performance distributed software storage. The focus of the implementation is to identify the challenges involved in ripping out Blkin's definition of tracing and propagation of Metadata and replacing with Jaeger and identify the feasibility of doing so. If it is feasible, the aim is to replace Blkin tracing infrastructure with Jaeger for enabling an "always-on" and open source end-to-end tracing feature for Ceph.

Users/Personas Of The Project

Modern Internet services are often implemented as complex, large-scale distributed systems. These applications are constructed from collections of software modules and could span many thousands of machines across multiple physical facilities. Knowing the system behavior and reasoning about performance issues are invaluable in such environments[1]. Therefore, the obvious use is to allow system engineers and researchers better understand the infrastructure and keep the system at highest efficiency. The users of the system are the administrators operating Ceph who want to understand a performance anomaly and understand the scope of the possibility of reducing the performance overhead.

Scope and Features Of The Project

The project is concerning two tracing tools for tracking requests in Ceph: Blkin and Jaeger. As a basic tracing infrastructure Blkin is thought to be naive and less effective in terms of "always-on" to continuously capture traces and on top of that it is simply an addition to Ceph, just applicable to that without any open source community behind it. For a more sophisticated approach, the project is dedicated in introducing Jaeger as a strong and open source tracing infrastructure for enabling end-to-end tracing and replacing Blkin with it.

Solution Concept

Ceph is an open source storage software designed to provide highly scalable object, block and file-based storage under a unified system [2]. As an open source distributed file system, Ceph emphasizes its performance, reliability and scalability with its novel approach towards metadata and improvements to file system principles. A Ceph Storage Cluster requires at least one Ceph Monitor, Ceph Manager, and Ceph OSD (Object Storage Daemon). The Ceph Metadata Server is also required when running Ceph Filesystem(CephFS) clients[3]. The novelty in distributing metadata workload is dependent on object-based storage which allows direct communication between storage unit and client.

An evolution in committing Reliable Automatic Distributed Object Storage (RADOS) and its sibling interfaces helps to achieve linear scaling capacity and performance in terms of availability, throughput rate, and fail recovery. Beside Ceph specific interface (RADOS), there are three other standard interfaces that work with RADOS(called as clients): CephFS for handling POSIX, Rados Block Device(RBD) for handling images (and virtual machines), and Radios Gateway (RGW) for handling REST API requests.[4]

The importance of Ceph is in its advancement, its scalability and the volume of acceptance from the industry. Due to its importance, it crucial to know Ceph's behavior. Tools such as tracing infrastructures that help us understanding system behavior and reasoning about performance issues are invaluable.

This project wishes to enable end-to-end tracing, from the request issue time till the time that is completed. The default tracing tool for ceph is "Ceph Blkin" which is considered as a naive one and is going to be replaced by Jaeger. The effort is to better study the anomaly, steady-state problem, distributed profiling, and resource attribute within the system[5].

Blkin Tracing System

Blkin is a library which follows the tracing semantics of Google's Dapper. It allows us to trace applications using LTTng, an open source tracing framework for Linux[6]. The major drawbacks of Blkin is its offline tracing (i.e. for tracing Ceph using Blkin, it should be started and then stopped and traces are collected for that specific time slot). Of course this way is not appropriate for one system (like Ceph) that is always running. In addition, Blkin is specified for Ceph, there is no specific open source community to work on it independently and improve it. So the solution can be replacing Blkin with other efficient and open source tracing tool like Jaeger.

Jaeger Tracing System

Jaeger, inspired by Dapper and OpenZipKin, is a distributed tracing system released as open source by Uber Technologies. It can capture traces, process them and finally visualize them and has its own specific interface for doing that. On each node of the cloud, Jaeger's agent should be installed and tracing point of the user application should be in Jaeger's syntax (format).

The most important pros of Jaeger is that it is supported by an open source community and is improved continuously. It is literally important to have such a tracing tool in a live community like Ceph.

Acceptance Criteria

  1. A weighted decision to determine if Jaeger can be used   to replace the existing Blkin infrastructure. Identification of the complexities involved in the replacement.

  2. Take Blkin’s tracepoints and replace with jaegers backend, thus, introduce Jaeger as a tracing infrastructure in Ceph.

  3. Capture traces for Ceph using Jaeger. Visualize "always-on" traces in Ceph with a sample workload.

Milestones/Deliverables

The project would be implemented and delivered incrementally at the end of each iteration

  1. Compilation of the project proposal.

  2. Showing traces using Blkin (making instances in OpenStack environment, Deploying Ceph on instances in OpenStack, Compiling Blkin for Ceph, Running Ceph with Blkin.)

  3. Understanding the Blkin architecture, replacement of Blkin with Jaeger.

  4. Presenting the plan and starting replacing Blkin with Jaeger.

  5. Demonstration of capturing traces using Jaeger, system integration, testing, bug-fixing and user documentation completion.

References

[1] B. H. Sigelman, L. A. Barroso, M. Burrows, P. Stephenson, M. Plakal, D. Beaver, S. Jaspan, and C. Shanbhag, “Dapper, a large-scale distributed sys- tems tracing infrastructure,” Google, Inc., Tech. Rep., 2010. [Online]. Available: https://research.google.com/archive/papers/dapper-2010-1.pdf

[2] Red Hat, Inc. (2017) Ceph homepage. [Online]. Available: https://ceph.com

[3] ——. (2016) Intro to Ceph Ceph Documentation. [Online]. Available: http://docs.ceph.com/docs/master/start/intro/

[4] Sage A. Weil, et al., “Ceph: a scalable, high-performance distributed file system,” OSDI 06 Proceedings of the 7th symposium on Operating systems design and implementation, 2006.

[5] Raja R. Sambasivan, et al., “So, you want to trace your distributed system? Key design insights from years of practical experience,” Carnegie Mellon University Parallel Data Lab Technical Report CMU-PDL-14-102, April, 2014.

[6] Red Hat, Inc. (2016) Tracing Ceph With BlkKin Ceph Documentation. [Online]. Available: http://docs.ceph.com/docs/master/dev/blkin/