Proposals
Rootconf 2019

Rootconf 2019

On infrastructure security, DevOps and distributed systems.

Rootconf

Rootconf is an annual conference on devops and cloud infrastructure, by HasGeek.

M

T

W

T

F

S

S

Jun

17

18

19

20

21

22

23

2019

NIMHANS Convention Centre, Bangalore

Call for proposals

Topics to propose talks:

We are seeking talks on the following topics:

  1. Case studies of shift from batch processing to stream processing
  2. Real-life examples of service discovery
  3. Case studies on move from monolith to service-oriented architecture
  4. Micro-services
  5. Network security
  6. Monitoring, logging and alerting – running small-scale and large-scale systems
  7. Cloud architecture – implementations and lessons learned
  8. Optimizing infrastructure
  9. Aligning people and teams with infrastructure at scale

We do not accept:

  1. How-to and introductory-level talks. We are interested in discussing the “whys” and “approaches” rather than “how-to”.
  2. Talks that have been covered in previous editions of Rootconf. Refer to https://hasgeek.tv/rootconf/ for all talks covered between Rootconf 2012 and 2017
  3. Proposals where code used for implementation is not demonstrated. Ideas are great, but it is the implementation that matters. Don’t talks to us about fantastic ideas. Tell us real stories of implementations – patterns and anti-patterns.

Dates and venue:

Date: 21 and 22 June, 2019
Venue: NIMHANS Convention Centre, Bangalore

Note the following guidelines for sponsored talks and open submissions:

The first filter for a proposal is whether the technology or solution you are referring to is open source or not. Talks which advertise proprietary/paid solutions will be considered under sponsored talks’ category.

  1. If the technology or solution is proprietary, and you want to speak about your proprietary solution to make a pitch to the audience, you must pick up a sponsored session. This involves paying for the speaking slot and following editorial guidelines of review and pre-event rehearsals. Write to rootconf.editorial@hasgeek.com for clearing doubts on whether your talk falls under the sponsored category.
  2. If the technology or solution is in the process of being open sourced, we will consider the talk only if the solution is open sourced at least three months before the conference.
  3. If your solution is closed source, you should consider proposing a talk explaining why you built it in the first place; what options did you consider (business-wise and technology-wise) before making the decision to develop the solution; or, what is your specific use case that left you without existing options and necessitated creating the in-house solution.

Selection criteria:

The criteria for confirming talks, in the order of importance, are:

  1. Key insight or takeaway: what can you share with participants that will help them in their work and in thinking about the problem be it network security, cloud architecture or microservices?
  2. Structure of the talk and flow of content: a detailed outline – either as mind-map or draft slides or textual description – will help us understand the focus of the talk, and the clarity of your thought process.
  3. Ability to communicate succinctly, and how you engage with the audience. You must submit link to a two-minute preview video explaining what your talk is about, and what is the key takeaway for the audience.

No one submits the perfect proposal in the first instance. We therefore encourage you to:

  1. Submit your proposal early so that we have more time to iterate if the proposal has potential.
  2. Write to rootconf.editorial@hasgeek.com if you have questions about how to submit a talk.

Our editorial team helps potential speakers in honing their speaking skills, fine tuning and rehearsing content at least twice - before the main conference - and sharpening the focus of talks.

We only accept one speaker per talk. This is non-negotiable. Workshops can have more than one instructor.

How to submit a proposal (and increase your chances of getting selected):

The following pointers will help you in submitting a proposal:

  1. Focus on why, not how. Explain to participants why you made a business or engineering decision, or why you chose a particular approach to solving your problem.
  2. The journey is more important than the solution you may want to explain. We are interested in the journey, not the outcome alone. Share as much detail as possible about how you solved the problem. Glossing over details does not help participants grasp real insights.
  3. We do not accept how-to talks unless they demonstrate latest technology. If you are demonstrating new tech, show enough to motivate participants to explore the technology later.
  4. Similarly, we don’t accept talks on topics that have already been covered in the previous editions. If you are unsure about whether your proposal falls in this category, drop an email to: rootconf.editorial@hasgeek.com
  5. Content that can be read off the internet does not interest us. Our participants are keen to listen to use cases and experience stories that will help them in their practice.

To summarize, we do not accept talks that gloss over details or try to deliver high-level knowledge without covering depth. Talks have to be backed with real insights and experiences for the content to be useful to participants.

Passes and honorarium for speakers:

We pay an honorarium of Rs. 3,000 to each speaker and workshop instructor at the end of their talk/workshop. Confirmed speakers and instructors also get a pass to the conference and a discount code which they can share with their colleagues, communities they are part of, and on social media channels. We do not provide free passes for speakers’ colleagues and spouses. Please do not ask us for this.

Travel grants for outstation speakers:

Travel grants are available for international and domestic speakers. We evaluate each case on its merits, giving preference to women, people of non-binary gender, and Africans.
If you require a grant, request it when you submit your proposal in the field where you add your location. Rootconf is funded through ticket purchases and sponsorships; travel grant budgets vary.

Last date for submitting proposals is 5 March 2019:

You must submit the following details along with your proposal, or within 10 days of submission:

  1. Draft slides, mind map or a textual description detailing the structure and content of your talk.
  2. Link to a self-recorded, two-minute preview video, where you explain what your talk is about, and the key takeaways for participants. This preview video helps conference editors understand the lucidity of your thoughts and how invested you are in presenting insights beyond the solution you have built, or your use case. Please note that the preview video should be submitted irrespective of whether you have spoken at past editions of Rootconf.
  3. If you submit a workshop proposal, you must specify the target audience for your workshop; duration; number of participants you can accommodate; pre-requisites for the workshop; link to GitHub repositories and a document showing the full workshop plan.

All proposals

Confirmed sessions

Birds of Feather (BOF) session: On taking your home brew projects to graduate into CNCF projects

Neependra Khare (@neependra)

  • 0 comments
  • Thu, 20 Jun

What are the benefits of using Ansible Automation?

OMPRAGASH VISWANATHAN (@ompragash)

  • 0 comments
  • Wed, 19 Jun

Automate your IX’s RS Config

Anurag Bhatia (@anuragbhatia)

  • 0 comments
  • Wed, 12 Jun

SRE Approach to Supporting Products as a PaaS Internally

Akshat Goyal (@aksg) (proposing)

  • 0 comments
  • Wed, 12 Jun

Bug Bounties for organizations

Anant Shrivastava (@anantshri)

  • 0 comments
  • Tue, 11 Jun

POLARDB - A database architecture for the cloud

Øystein Grøvlen (@oysteing)

  • 0 comments
  • Mon, 10 Jun

OSINT for Proactive Defense

Shubham Mittal (@shubhammittal)

  • 0 comments
  • Sat, 8 Jun

Onion Services for devops

Kushal Das (@kushaldas)

  • 0 comments
  • Sat, 8 Jun

Defensive and Offensive Applications of Open Source Intelligence

Karan Saini (@karansaini)

  • 0 comments
  • Fri, 7 Jun

Implementing security from day 1 at a fintech startup

Himanshu Kumar Das (@himanshudas)

  • 2 comments
  • Thu, 6 Jun

How do you keep your secrets and how much does it cost?

Anand Venkatanarayanan (@anand-venkatanarayanan) (proposing)

  • 0 comments
  • Thu, 6 Jun

Devil lies in the details: running a successful bug bounty programme in your organization

Shadab Siddiqui (@shadsidd)

  • 2 comments
  • Thu, 6 Jun

SRE: Culture & Strategy

Talina Shrotriya (@talina06)

  • 3 comments
  • Fri, 31 May

Virtuous Cycles: Enabling SRE via automated feedback loops

Aaditya Talwai (@talwai)

  • 4 comments
  • Thu, 30 May

Decomposing a Monolith: Engineering and Operational strategies we have gleaned from our experience at Endurance

Sudheer Kumar Meesala (@sudheerm)

  • 8 comments
  • Mon, 6 May

OLTP or OLAP? Why not both?

Jiten Vaidya (@jvaidya)

  • 1 comments
  • Mon, 6 May

Software/Site Reliability of Distributed Systems

Piyush Verma (@meson10)

  • 0 comments
  • Sun, 5 May

Scalable dist-sys from grounds up in Elixir

udit kumar (@uditkr)

  • 10 comments
  • Sat, 20 Apr

Security Paranoid OS

Sayan Chowdhury (@sayanchowdhury)

  • 0 comments
  • Thu, 11 Apr

Let’s talk about routing security

Anurag Bhatia (@anuragbhatia)

  • 0 comments
  • Mon, 8 Apr

Virtual Nodes to auto-scale applications on Kubernetes

vivek sridhar (@vivsridh)

  • 1 comments
  • Mon, 8 Apr

Art and science of choices in engineering

srujan akumarthi (@acsrujan)

  • 1 comments
  • Mon, 1 Apr

eBPF: BPF kernel Infrastructure

tk sourabh (@sourabhtk37)

  • 5 comments
  • Mon, 1 Apr

Functional programming and Nix for reproducible, immutable infrastructure

Brian McKenna (@puffnfresh)

  • 0 comments
  • Sun, 31 Mar

DevSecOps

Neelu Tripathy (@br3akp0int)

  • 0 comments
  • Mon, 18 Mar

Using Pod Security Policies to harden your Kubernetes cluster

Suraj Deshmukh (@suraj-deshmukh)

  • 2 comments
  • Sun, 17 Mar

Building reproducible Python applications for secured environments

Kushal Das (@kushaldas)

  • 0 comments
  • Thu, 14 Mar

Deploying and Managing CSP - the Browser-side Firewall

Lavakumar Kuppan (@lavakumark)

  • 0 comments
  • Tue, 12 Mar

Building a 100% remote team

Ratnadeep Debnath (@rtnpro)

  • 1 comments
  • Sat, 9 Mar

Scale MySQL beyond limits with ProxySQL

Ratnadeep Debnath (@rtnpro)

  • 0 comments
  • Fri, 8 Mar

Kafka Streams at Scale

DEEPAK GOYAL (@zonker)

  • 1 comments
  • Tue, 5 Mar

Network Automation with Ansible

Trishna Guha (@trishnag)

  • 2 comments
  • Tue, 5 Mar

Load Balancing : in-depth study to scale @ 80K TPS

Shrey Agarwal (@shreyagarwal)

  • 0 comments
  • Wed, 27 Feb

Shooting the trouble down to the Wireshark Lua plugin

Shakthi Kannan (@shakthimaan)

  • 2 comments
  • Wed, 27 Feb

SSH Certificates: A way to scale SSH access

Pulkit Vaishnav (@pu1kit0)

  • 0 comments
  • Sun, 17 Feb

Code Coverage Based Verification (CCBV)

Omprakash Kasaraboina (@opk)

  • 4 comments
  • Thu, 7 Feb

How convenience Is Killing open standards

Bernd Erk (@bernderk)

  • 2 comments
  • Tue, 15 Jan

Learnings from running my Home Server (and why you should run one too)

Abhay Rana (Nemo) (@captn3m0)

  • 2 comments
  • Tue, 15 Jan

Log Analytics with ELK stack (Architecture for aggressive cost optimization and infinite data scale)

Denis Dsouza (@denisdsouza)

  • 6 comments
  • Sat, 12 Jan

Securing Infrastructure with OpenScap: The Automation Way !!

Jaskaran Singh Narula (@jaskaransingh)

  • 3 comments
  • Thu, 20 Dec

Unconfirmed proposals

Kingsly - The Cert Manager

Tasdik Rahman (@tasdikrahmangojek)

  • 1 comments
  • Sat, 8 Jun

OSINT mindset to protect your organization

Chandrapal (@bnchandrapal)

  • 0 comments
  • Sun, 21 Apr

Meeseeks(Service-Graph)

Gaurav Sharma (@gaurav75)

  • 5 comments
  • Tue, 9 Apr

Data handling patterns for diverse needs of Consistency, Scale, Low Latency and Analytics Injestion

Regunath Balasubramanian (@regunathb)

  • 3 comments
  • Fri, 5 Apr

Why not containerize your desktop

Sayan Chowdhury (@sayanchowdhury)

  • 1 comments
  • Wed, 27 Mar

Audit Mitigate Compromised containers in Docker and Kubernetes

Aravind G V (@aravindgv)

  • 1 comments
  • Wed, 27 Mar

Schema Registry and how the encoding/decoding actually works under the hood!

Shivji Kumar Jha (@shiv4289)

  • 2 comments
  • Tue, 26 Mar

Central Metadata Catalogue - understanding data in your pipelines and data stores the self serve way

Shivji Kumar Jha (@shiv4289)

  • 1 comments
  • Tue, 26 Mar

Infra-Ops Agility

Dushyanth Harinath (@dushyy)

  • 2 comments
  • Tue, 26 Mar

From legacy services to one-click availability - The Rancher Way

Sreekanth G S (@sreekanthgs)

  • 0 comments
  • Tue, 26 Mar

Scaling DevOps - A Practical Guide

Utpal Sen (@utpalsenin)

  • 3 comments
  • Mon, 25 Mar

A Beast to Process Kafka Events

Dinesh Kumar (@devdinu)

  • 4 comments
  • Thu, 21 Mar

Running A Highly Available RabbitMQ Cluster

Kishore N C

  • 3 comments
  • Sat, 9 Mar

Ansible meets Foreman

Amit Karsale

  • 3 comments
  • Fri, 1 Mar

Continuous Delivery of Microservices

Aditya Sood (@aditya-sood)

  • 3 comments
  • Thu, 28 Feb

Building and Deploying applications on OpenShift

Fatima Shaikh (@fatima)

  • 5 comments
  • Thu, 28 Feb

Considerations for East-West Traffic Security and Analytics for Kubernetes Environment

Akshay Mathur (@akshaymathur)

  • 1 comments
  • Wed, 27 Feb

Introducing Hive-Kafka Integration for Real-Time Kafka SQL Queries

Amit Nijhawan (@anijhawa)

  • 7 comments
  • Mon, 25 Feb

Elasticsearch, Fluentd and kibana - Openshift stack for hybrid cloud

Jatan Malde (@jatanmalde)

  • 4 comments
  • Sun, 24 Feb

Eclipse Che and installing it on OpenShift!

Fatima Shaikh (@fatima)

  • 2 comments
  • Sat, 23 Feb

Emulated_Stack -

Nilesh Chandekar (@nileshchandekar)

  • 2 comments
  • Thu, 21 Feb

Automated debugging with git

Amit Nijhawan (@anijhawa)

  • 4 comments
  • Thu, 21 Feb

Microservices using Spring Boot - the new architecture for developers

Arnav Bhati (@arnavbhati)

  • 3 comments
  • Wed, 20 Feb

Patterns for solving distributed systems problems in our applications

Lakshminarasimhan Sudarshan (@lsudarsh)

  • 1 comments
  • Sun, 17 Feb

Lessons from the Migration of Windows and Microsoft based Applications (“Lift and Shift” approach from on premise to AWS)

chaitra acharya (@acharya-c1092)

  • 2 comments
  • Sun, 17 Feb

Cloud Native Persistent Observability with Thanos

Joy Bhattacherjee (@hashfyre)

  • 2 comments
  • Wed, 13 Feb

Iptables magic in sidecar istio

Sumit Murari (@murarisumit)

  • 0 comments
  • Tue, 12 Feb

Istio internals: Envoy

Sumit Murari (@murarisumit)

  • 1 comments
  • Tue, 12 Feb

Metal as a Service: Foreman Discovery

rahul bajaj (@rahulbajaj)

  • 2 comments
  • Mon, 11 Feb

Automating compliance with Foreman: The Lifecycle management tool

rahul bajaj (@rahulbajaj)

  • 2 comments
  • Mon, 11 Feb

Olympus: Terraforming repeatable and extensible infrastructure at GO-JEK

Ravi Suhag (@ravisuhag)

  • 1 comments
  • Sat, 2 Feb

DevOps and Continuous Security on AWS

Meghashyam Varanasi (@meghashyamvaranasi)

  • 2 comments
  • Wed, 23 Jan

Case Study: Transitioning from Batch processing to Event streaming architecture to enable Real time Streaming analytics

Venkatraman J (@venkatraman123)

  • 2 comments
  • Wed, 16 Jan

Building a cricket score fanout system that scales

Kishore Avineni (@kishoreavineni)

  • 1 comments
  • Wed, 16 Jan

MongoDB WiredTiger or Not

Gaurav Tayal (@gauravtayal)

  • 1 comments
  • Wed, 16 Jan

How we brought down costs by 60% without any code change.

Neeraj Prem (@neerajprem)

  • 5 comments
  • Tue, 15 Jan

Patterns for designing stateful microservices at scale

Guruprasad GV (@gurugv)

  • 4 comments
  • Sat, 12 Jan

The power of saying "I don't know"

Andrew Murphy (@andrewmurphy)

  • 0 comments
  • Sun, 6 Jan

Communicating anything to anyone. How to communicate effectively and efficiently

Andrew Murphy (@andrewmurphy)

  • 0 comments
  • Sun, 6 Jan

Human Centered Leadership - Emotional Intelligence for the Technical Mind

Andrew Murphy (@andrewmurphy)

  • 0 comments
  • Sun, 6 Jan

Monitoring Distributed Systems with Riemann

Abhishek A Amralkar (@aamralkar)

  • 3 comments
  • Wed, 26 Dec

Disruptions in Architecture construct

Samit Das (@samdas)

  • 1 comments
  • Fri, 2 Nov

Building Distributed Systems in Distributed Teams

Aravind Putrevu (@aravindputrevu)

  • 3 comments
  • Tue, 16 Oct