May 2017
8 Mon
9 Tue
10 Wed
11 Thu 08:40 AM – 11:10 PM IST
12 Fri 08:40 AM – 06:00 PM IST
13 Sat
14 Sun
##Submit proposals for flash talks
Rootconf is on 11-12 May. If you have:
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.
##Theme
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.
##Format
Rootconf is a three track conference:
We are inviting proposals for:
##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.
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:
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:
##Contact
For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020.
Aruna Chakkirala
@arunac
Submitted Feb 15, 2017
Automating deployments and monitoring has become the need and the norm. The real trial starts after the monitoring has rightly alerted a problem. Troubleshooting and diagnosing the problem correctly and quickly is essential in production environments. This can be best achieved by automating beyond monitoring with good diagnostic tools. It starts with collecting the right amount of information. In the next stage, sifting through all the collected information requires a practiced eye which is most often a result of experience. Transferring this know how of the “practiced eye” into a tool makes it a scalable process while also ensuring consistency in the diagnosis.
This is a brief talk on the art of collecting, sifting and automating diagnostic mechanisms.
What is meaningful data: Data data everywhere not a bit to diagnose (5 minutes)
Data gathering: Snapshots and Probes (10 min)
Root Causing: Finding way through the maze. Stepwise elimination (10 min)
Automating: Journey from gut to metric (10)
Questions (5 minutes)
Aruna Chakkirala leads the product operations team at Aerospike India. She has worked at various technology companies including Verisign and Yahoo. She gained a performance perspective and a fascination for scale while leading the production engineering teams at Yahoo. And in her current role, the speed at scale aspect of Aerospike’s NoSql database continues to fuel her excitement.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}