Submit proposals for flash talks
Rootconf is on 11-12 May. If you have:
- Tips and tricks for simplifying infrastructure management and maintenance;
- Experiences with new tools to share;
- 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:
- Capacity planning.
- Deploying microservices, and issues concerning monitoring and reliability of microservices.
- Deployment and orchestration of container based infrastructures.
- Open tracing.
Topics for Round 1 of the CfP were:
- Monitoring strategies
- Deployment strategies
- Capacity planning
- Automation beyond deployment and monitoring
- Eliminating toil
- On-call outage handling
- Postmortem / root cause analysis
- Incident response
Rootconf is a three track conference:
- Rooconf talks in the main auditorium.
- Red Hat and Linux Foundation sponsored Platforms track in the banquet hall.
- Birds of Feather (BOF) sessions in the lawns.
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.
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.
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”.
- 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 email@example.com or call +91-7676332020.
Capacity planning for your data stores
In the objective, I described a ticket sales website that does “normal” events like an M2M concert, but occasionally also sells tickets to the Harry Potter theatre show. This is a perfect capacity planning example because you don’t want to be buying servers that aren’t doing anything for much of the time. This is also why the cloud is so popular today. While the focus of this talk is not to help you plan for the application server loads and caches, the data layer is definitely a hard one to tackle.
Selling tickets require you to never sell more tickets than you actually have. You want to load balance your queries. You want to shard your data stores. You may want to split reads and writes. You need to determine where the system bottlenecks, so for that you need a baseline and know what regular traffic patterns are.
Beyond that, we will talk about storage capacity planning for OLTP and data warehousing uses.
The general idea here is that from metrics collection, you will be able to plan your requirements. Couple this with the elastic nature of clouds, and you should never have an “error establishing database connection”.
Tools covered in this talk include but are not limited to: Box Anemometer, innotop, the slow query log, Percona Toolkit (pt-query-digest), vmstat, Facebook’s Prophet, Percona Monitoring & Management (PMM).
Databases (referred here as data stores, since some modern ones prefer to be referred to as stores) require capacity planning (and to those coming from traditional RDBMS solutions, this can be thought of as a sizing guide). Capacity planning prevents resource exhaustion. Capacity planning can be hard. This talk has a heavier leaning on MySQL, but the concepts and addendum will help with any other data store.
The simple example: you’re selling tickets to the Harry Potter theatre show and the last time this happened, people waited for over twelve hours in a virtual queue and then purchased their tickets. The queue helped with capacity planning, but now you’re selling tickets for more shows. What do you do? Learn more about this here.
Colin Charles is the Chief Evangelist at Percona. He was previously on the founding team of MariaDB Server in 2009, and had worked at MySQL since 2005, and been a MySQL user since 2000. Before joining MySQL, he worked actively on the Fedora and OpenOffice.org projects. He’s well known within open source communities in APAC, and has spoken at many conferences.