Gluster and Outreachy!
Application deadline: 17 Oct 2016
Selection decisions are made: 8 Nov 2016
Internships: 6 Dec 2016 to 6 Mar 2017
Introducing instrumentation tooling into Gluster
The suite of tools available to undertake performance related instrumentation on Linux has improved over the period of years. As various layered products - clustered applications; distributed storage and such were adopted and deployed at large scale, administrators have constantly voiced a need to improve upon the methods, tools and data processing capabilities of the tools.
Gluster is a software defined distributed storage system which would readily benefit of a structured approach to instrumentation. There already exist known methods to trace specific issues on the Gluster stack. These include and are not limited to SystemTap, PCP, and read-write performance tools like iozone and such.
The scope of the project is to (a) identify a first pass set of instrumentation framework to be adopted and made available to the community as a recommended approach (b) design, develop, deploy and evangelize a set of working examples of instrumentation hooks which provide adequate spectrum of information (c) document the usage of the framework in a variety of deployment environments viz. bare-metal, hyperconverged and public cloud deployments
Initial Contribution: We intend this exercise to help applicants familiarize themselves with Gluster and also run some performance tests against a Gluster setup. In addition to this, an understanding of how the applicant perceives instrumentation and analysis of the results from such an exercise. Part or most of the instrumentation developed as a part of this project would land in the Gluster bench project. As an initial contribution an applicant could attempt the following:
When you're finished with this, please add your contribution to the firstname.lastname@example.org mailing list for review.
Operator focused documentation for Gluster
Documentation is always hard in large open source projects! There are issues with stale documentation; correctness of the content; focus and approach and even whether it enables a reasonably proficient administrator to get up to speed.
The scope of this project to create a first version of the documentation and content which can be consumed by operators intending to bootstrap Gluster with technologies like Kubernetes and OpenShift. Within the scope is the testing and documentation of the sequence of steps; creating a playbook can be easily extended and refreshed; adding any demo videos and such which are supplementary companions to the documentation. The target audience for this set of content is someone planning to use Gluster as a persistent store for applications which are managed via Kubernetes etc
At the end of the project the candidate will have acquired a sufficient depth and understanding of Gluster in a micro-services environment; creating scripts to build and tear-down small set-ups; interview operators and developers to enhance documentation.
To make an initial contribution, please review our current documentation at Read The Docs for our overall project. Please choose something in our documentation that you'd like to make a meaningful improvement to, and submit a pull request. As you do so, please tag github user @amye with your pull request for review.