Rootconf 2016

Rootconf is India's principal conference where systems and operations engineers share real world knowledge about building resilient and scalable systems.

Rootconf is India’s principal conference where systems and operations engineers share real world knowledge about building resilient and scalable systems.

We are now accepting submissions for our next edition which will take place in Bangalore 14-15 April 2016.


The theme for this edition will be learning from failure. We are keen to explore how devops think about failure when designing, building and scaling their systems. We invite presentations related to failure in database systems, servers and network infrastructure.

We encourage presentations that relate to failure not only in terms of avoidance but also in terms of mitigation and education. How do we decide which parts of our systems cannot fail? What measures do we take to mitigate failure when it does inevitably happen? And most importantly: what lessons can be learned from failure?


This year’s edition spans two days of hands-on workshops and conference. We are inviting proposals for:

  • Full-length 40 minute talks.
  • Crisp 15-minute talks.
  • Sponsored sessions, 15 minute duration (limited slots available; subject to editorial scrutiny and approval).
  • Hands-on Workshop sessions, 3 and 6 hour duration.

Selection process

Proposals will be filtered and shortlisted by an Editorial Panel. We urge you to add links to videos / slide decks when submitting proposals. This will help us understand your past speaking experience. 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 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.

We will notify you about the status of your proposal within three weeks of submission.

Selected speakers must participate in one-two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.

There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek will provide a grant to cover part of your travel and accommodation in Bangalore. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer).

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

Key dates and deadlines

  • Paper submission deadline: 31 January 2016
  • Schedule announcement: 29 February 2016
  • Conference dates: 14-15 April 2016


Rootconf will be held at the MLR Convention Centre, J P Nagar.


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

Related events

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Kushal Das


Failure at Cloud & rescued by Python

Submitted Feb 22, 2016

This talk will go through the issues we faced in the Fedora Cloud SIG while testing the cloud imgaes, and how we solved the issues in record time with help from a programming language called ‘Python’. I hope this talk will encourage people to use more of Python as a tool to solve problems.


The Fedora Cloud SIG works to make Fedora successful on all major cloud platforms, public and private. As a community we maintain, build, and release a set of images which not only covers the standard cloud installations, but also for Vagrant users in different operating systems. Couple of
release back we had some last minute release blocking bugs which escaped our manual qa effort from the community. This talk will re-introduce Python programming language in a situation like above, and how it helped to create an efficient automated testing framework up & running.
The major points of the talk:

  • Why didn’t we just write some shell scripts? What was the benifit of using Python, a full blown programming language? (Hint: think about maintaining the codebase)
  • First introduction of Python as unittests. Even though we were running shell commands, and checking the output, the introduction of unittests helped even new comers to become a helping hand in the process. Showcasing the amount of flexibility unittest module provided.
  • Boot -> Test -> Destroy: Moved the whole process into a Python module. (Reusability in other codebases)
  • Minimal configuration: import json came to rescue. Example of trying to do the same over shell scripts.
  • In cloud there is no guaranty of successful instances. We had to bring in another standard Python language
    feature called Decorator. We will see diffrent code examples about how we can use this language feature in different places.
  • Just 2 week before production deployment, rel-eng team said this is
    not what they want. We need to test Vagrant images.
  • Oops, libvirt storage failure. Have to refresh all storage volumes. Let us call another Python function.
  • Remember those unittest module we talked about before? I never had to start writing tests from scratch, someone will do that even before I start writing.
  • Batteries included in Python. There is a readymade Python module to do anything you want. We had to add feature to control instances over AWS. Seems to be few more lines of code.
  • Total project is now around 1k lines of code, 45KB rpm size.

This talk will showcase how one can use these batteries to solve most of the problems in one’s life (or the job). I will go through the code examples as required in the talk.

Speaker bio

Kushal Das is a core developer of CPython project. He is a long time Fedora project contributor, and currently works as Fedora Cloud Enginner in the Fedora Engineering team at Red Hat. He is also a fellow at Python Software Foundation.




{{ 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 forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more