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.

Related events

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

Pooja Shah


A little bot for big cause

Submitted Jan 21, 2017

Its Release Day and the code started breaking all of a sudden, tested features not working anymore, its going to take time to figure out whom to reach & people start passing the buck?
Experienced such stormy sail on your release day?

Amidst all this, losing time for release deployment as the traffic on your product is peaking up or exceeding the deadline promised to the clients. Manual monitoring wasn’t a solution as it isn’t scalable ?

Yes, in fast paced organisations like us, it is a burning problem. And we really wanted a system in the dev phase itself that which can bring agility within the teams by having everything & everyone know that what’s there in the black box. Do you also feel the same?

  • Already nodding your head in agreement ? Many times somewhere deep down, did you feel like escaping from the heated discussion or wished there were snapshots of all the important events which could give you the clues/traceback to hunt & chuck the wrong commits out of the system and move ahead. Or even better some software which you could just hook to your system which would never let us reach such a chaotic state itself by blocking/notifying any wrong doings.
  • Or are you someone just starting off your company and do not want to go through the same challenges we went through & help your developers focus only on building the awesome stuff which you wanted to
  • Or are you among those telling yourself “we already solved it”.
    As a tech geek, are you excited to explore a different way as to how we are solving it?

Would you believe if I say “a bot can help in solving such problems of communication between humans”. That too using the same tools we use daily, eager to see how?

Come let’s talk and take a sneak peek at how we are dealing with these at MoEngage Inc. And yes, get to start using the solution open-sourced in almost no time.
In this crisp talk, we will discuss about unleashing the power of Github, Slack and some awesome open-source technologies to create a code monitoring and talking bot which can keep everyone in a team, up to date and be a helper in need.
~ A little attempt towards making healthier work culture and keeping the smart brains happier :-)


The talk is about a bot which can help your team “preventing last moment panic moments” by:

  • monitoring/reminding/blocking/alerting teams/individuals to maintain code hygiene
  • enabling every member in team to get any info about the system @ any time
  • enabling saving some brains whose most of the work time goes in answering same questions about the system
  • having a trustworthy 24x7 code monitoring system from dev to release phase which can prevent & alert for any unhealthy action for the code

Detailed breakup:

  1. problem analysis & origin of the bot - 10 min
  2. The bot at your service - 13 min
    • with a live demo, we will discover, how we got our first bot live and then what more handy features it brought @ work, that its like a team member now.
  3. The exponential future possibilities - 2 min
  4. Questions & Answers - 5 min

Speaker bio

Pooja is an automation nerd and open source enthusiast. She loves brainstorming and implementing crazy ideas to figure out ways to improve the product quality. Having a blend of dev, qa & devops mindset, she strives to bridge the gaps between all the teams to attain the best results.
Driven by curiosity to learn & share new things everyday, She pen them, few glimpses can be found here:



{{ 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