Rootconf 2017

On service reliability

##Submit proposals for flash talks
Rootconf is on 11-12 May. If you have:

  1. Tips and tricks for simplifying infrastructure management and maintenance;
  2. Experiences with new tools to share;
  3. Cool demos;

then propose a flash talk here, or on the spot, at the venue.

The flash talk session is on 11 May, from 17:20-18:20. We have room for about 12 flash talks. Each presentation should be no more than 5 minutes.

A final note of caution when presenting at flash talks: we have a code of conduct at the conference. You must refrain from making remarks that may be perceived as sexist or derogatory. If you want to double check your presentation, contact Sandhya Ramesh, Karthik B. or Zainab Bawa at the venue.

The theme for the 2017 edition is service reliability. The conference will feature talks on state of the art deployment strategies and appropriate monitoring technologies at different scales. Rootconf this year will broadly cover topics like toil, on-call, outage handling, and post-mortem analysis. We are inviting presentation proposals from academics and practitioners on these topics.

Rootconf aims to appeal to the widest possible range of DevOps practitioners: from embryonic startups to the largest established enterprises. We are keen to schedule presentations that appeal both to attendees’ current needs as well as their future aspirations.

##About the Conference
Rootconf is India’s principal conference where systems and operations engineers share real world knowledge about building reliable systems. We are now accepting submissions for our next edition which will take place in Bangalore on 11-12 May 2017.

Topics for Round 2 of the CfP were:

  1. Capacity planning.
  2. Deploying microservices, and issues concerning monitoring and reliability of microservices.
  3. Deployment and orchestration of container based infrastructures.
  4. Open tracing.

Topics for Round 1 of the CfP were:

  1. Monitoring strategies
  2. Deployment strategies
  3. Capacity planning
  4. Automation beyond deployment and monitoring
  5. Eliminating toil
  6. On-call outage handling
  7. Postmortem / root cause analysis
  8. Incident response

Rootconf is a three track conference:

We are inviting proposals for:

  • Full-length 40-minute talks – which cover conceptual topics and include case studies.
  • Crisp 15-minute how-to talks or introduction to a new technology.
  • Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
    Hands-on workshop sessions of 3 and 6 hour duration where participants follow the instructors on their laptops.

##Selection Process
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.

We expect you to submit an outline of your proposed talk, either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.

Selection Process Flowchart

You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.

A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.

There is only one speaker per session. Entry is free for selected speakers.

##Travel Grants
As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable:

  • Two grants covering travel and accommodation for international speakers.
  • Three grants covering travel and accommodation for domestic speakers.

Grants will be made available to speakers delivering full sessions (40 minutes or longer).
*Speaker travel grants will be given in the order of preference to students, women, persons of non-binary genders, and speakers from Asia and Africa.

##Commitment to Open Source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.

##Important Dates:

  • Deadline for submitting proposals: 10 April, 2017
  • Final conference schedule: 15 April 2017
  • Conference dates: 11-12 May, 2017

For more information about speaking proposals, tickets and sponsorships, contact or call +91-7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Ankit Raj


Demystifying DHT in GlusterFS

Submitted Apr 7, 2017

Introduction of GlusterFS: Distributed file system gives us a way for storing and accessing files in a client/server architecture. Here we can use more that one server to store data and use multiple clients (local or remote) that can access data from these servers. It organizes and displays files and directories from multiple servers as if they were stored in your local system, thereby projecting a simple interface to the user or application. Their main advantage is that it is easier to distribute documents to multiple clients and they provide a centralized storage system so that client machines are not using their resources to store the data. There are few terminologies which we need to understand before diving into DHT like:

storage pool

Distributed Hash Table (DHT):
Distribution in GlusterFS is handled by the DHT or the Distributed Hash Table which is loaded on the client stack. All operations are driven by the clients which are all equal. There are no metadata servers or special nodes which have any additional information about where the files are present or should go. Any additional information about file or directories are stored in the extended attributes or xattrs. Xattrs are filesystem features that enable users to associate files/dirs with metadata. They store information as key-value pairs. There are mainly two DHT related xattrs- linkto and layout.

DHT creates directories on all the bricks. When directory is created a layout range is assigned to it which is stored in the extended attribute called trusted.glusterfs.dht .The range varies from 00000000 to 0xffffffff and each brick is assigned a specific subset of this range. The layout is complete and healthy when the range 00000000 to 0xffffffff is distributed across the volume without any gaps or overlap.

Unlike directories file have to be present on only one subvol. Given a file we find its hash value and the brick on which the hash value falls. This brick is known as the hashed brick. The brick on which the data file actually exists is the cached brick. For a newly created file the hashed and the cached brick will usually be the same. Considering the above example if we create a file under the directory dir1 then the file will be created on only one of the brick.

However while renaming a file the destination file’s hashed brick may be different from the source file’s hashed brick. In this case instead of actually moving the entire data file to the new hashed brick we create a linkto file. This is a 0 byte file which is created on the new hashed brick.

Takeaway: The sole aim is to make audince aware of GlusterFS. How It works? Since, DHT is one of the core part. So before diving into the contribution they should have minimal knowledge about how it works. Last but not least, we want audience to contribute on our upstream repo. :)


Introduction about GlusterFS
Basic Terminologies
What is DHT?
How it works?
Major fops algorithm
Contribution guide


Projector, Mic

Speaker bio

Hi there!
This is Ankit Raj, currently working at Red Hat in Gluster Team. Before joining to Red Hat, I have worked as Ruby on Rails developer for few startups. Also, In 2015 I participated as a Student developer under Ruby organisation in Google Summer of Code 2015.
I am programmer, learner, presenter and a Engineer in the process. I have spoken at various national conferences and local meetups.


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more