##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.
- Capacity planning.
- Deploying microservices, and issues concerning monitoring and reliability of microservices.
- Deployment and orchestration of container based infrastructures.
- Open tracing.
- 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 firstname.lastname@example.org or call +91-7676332020.
Adventures in Postgres management
The talk will cover deployment, maintenance and monitoring strategies for large-scale Postgres instances. Starting with a story about unexpected performance issues, the journey will continue down the rabbit hole of database management. Concurrency control solutions in Postgres, their benefits, drawbacks and consequences will be discussed - via a post-mortem analysis of an (almost-catastrophic) incident. Structured as a series of investigation-action-learning cycles - the aim is to convey the inquisitive mindset required of DevOps engineers to maintain high-reliability systems.
The aim of this section is to provide a gentle introduction to the system being examined. The use-case, requirements and setup of the tools will be discussed to benefit those not familiar with the intricacies of the domain.
- basic overview of Postgres/SQL database management
- solutions for concurrency control via transaction IDs
- caveats to these solutions and its consequences
This section will form the crux of the talk. Beginning with investigations into reports of degraded performance, the story leads towards specific limitations of Postgres’s MVCC implementation.
Tools used in investigating the incident and various attempted solutions will be discussed. The focus will be on diagnosing/fixing systems without compromising on underlying performance and uptime requirements.
- overview of use-case, system setup and configuration specifics
- initial monitoring and tracking system performance reports
- tools used to investigate the degradation
- first attempt at a fix, its failure to correct, and subsequent learning
- second attempt to brute-force a solution, and the resulting (failed) inconsistent state
- final attempt at a simpler solution, and learning
The last section will cover lessons learned - including checks and systems that could have avoided the problem. The various knobs available to DevOps engineers to manage the performance of their systems will be explored. Combining personal experiences with industry best practices, the aim is to deliver concrete steps to simplify database management. Also, in the months since the incident, patches in newer Postgres releases which fix the problem will be listed.
- knobs to turns and levers to pull when tuning systems
- best practices to simplify Postgres management roles
- updates and relevant patches available via newer releases
Even though the session is aimed at the novice DevOps engineer, a general understanding of relational databases and their performance requirements/constraints would help.
I am a member of the data science team at Semantics3 - building data-powered software for ecommerce-focused companies. Over the years, I have had the chance to dabble in various fields covering data processing, pipeline setup, database management and data science. When I am not picking locks, or scuba diving, I usually blog about my technical adventures at our team’s engineering blog.
- Original incident writeup - https://engineering.semantics3.com/2016/07/20/an-unexpected-dba-journey/
- Some interesting discussion that followed at https://news.ycombinator.com/item?id=12209395 and https://www.reddit.com/r/programming/comments/4vr00u/an_unexpected_journey_a_postgres_dbas_tale/
- My other technical articles - https://engineering.semantics3.com/authors/ramananbalakrishnan/