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.
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).
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.
- 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 email@example.com or call +91-7676332020.
Openstack - getting it all up magically - and when the magic fails.
To discuss the experience of openstack setup and testing using CI/CD based on puppet, what all we did and when and where does it fail. At the end of the session, the audience will know about what all works and helps to setup an openstack cluster with no manual intervention. And what all can go wrong in the same openstack production cluster.
This talk will discuss my experience with Openstack, Puppet and setting up the same in a completely automated, no-manual intervention method at Reliance Jio. We used the same openstack setup to create further openstack setups! These mini openstack setups on top of the base openstack setup are used for testing and gating new code changes and further running Acceptance tests. And at the heart of it is the same code which runs itself, runs production, runs and tests itself! At the heart of this setup is a puppet module which is like nothing you would ve seen. This puppet setup is a standalone setup - i.e, no master-client setup. This puppet module is unique in the sense that it manages/uses other puppet modules as well uses itself as a module of itself! Tying all the components of openstack together for service discovery and avoiding dependency failures till a required service is up (by means of a DNS blocker) is consul.
Basic knowledge of openstack and puppet.
I have been working on large scale environments for the last seven years. Starting with Yahoo! search, where I spent the first four years - and from where I decided to move one fine day when I realised I have “touched” each and every machine in the search inventory! From there on, the next stopover was at Aerospike, which brought altogether different numbers (A million TPS in less than a millisecond!). Am presently working with Reliance Jio as Platforms Engineering Manager / Devops on efforts of setting up a public cloud.