Rootconf 2017

On service reliability

Submit proposals for flash talks

Rootconf is on 11-12 May. If you have:

  1. Tips and tricks for simplifying infrastructure management and maintenance;
  2. Experiences with new tools to share;
  3. 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.

Theme

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:

  1. Capacity planning.
  2. Deploying microservices, and issues concerning monitoring and reliability of microservices.
  3. Deployment and orchestration of container based infrastructures.
  4. Open tracing.

Topics for Round 1 of the CfP were:

  1. Monitoring strategies
  2. Deployment strategies
  3. Capacity planning
  4. Automation beyond deployment and monitoring
  5. Eliminating toil
  6. On-call outage handling
  7. Postmortem / root cause analysis
  8. Incident response

Format

Rootconf is a three track conference:

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.

Selection Process

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.

Selection Process Flowchart

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.

Travel Grants

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

Important Dates:

  • Deadline for submitting proposals: 10 April, 2017
  • Final conference schedule: 15 April 2017
  • Conference dates: 11-12 May, 2017

Contact

For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com 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

Nandish Madhu

@nandishmadhu

Monitoring – Does it always work?

Submitted Feb 10, 2017

Availability and Uptime of customer Offerings is key to the business. Monitoring forms an important aspect of Business Continuity and is an area that never seems to be as complete as we would desire it to be.

In this talk, I would like to share few effective practices with realtime examples that we have used to significantly reduce Time to Detect an incident.

With the large number of monitoring tools that are available and the features they offer, we tend to map/adjust our requirements based on the capabilities of these tools. Being grounded on what needs to be monitored and nailing the fundamentals will be the key to success. My presentation is going to be focused towards infrastructure monitoring but the approach could be applied to all monitoring efforts. While I cover topics on effective monitoring approach that has worked for me and my team in reducing Time to Detect, I would end the presentation by leaving behind few thoughts with the audience on the next logical step which is Time to Restore.

Outline

Introduction - 5 mins
Introducing myself and setting the context of what would be covered as part of the presentation

Content delivery on Time to Detect - 20 mins
• As part of the main content delivery, I would start by grounding the audience on why monitoring is important.
• Few key topics that would be covered are:
• Commitment/Ownership from the leaders
• Onboarding process for devices to be monitored and workflow definition
• Validation, Validation, Validation (Various aspects of validation)

Closure notes with importance of Time to Restore - 5 mins
Effective monitoring and alerting can help improve Time to Detect. Once we know what went wrong, several factors need to be considered to quickly restore the services. Reducing business impact is the ultimate goal of any monitoring effort. I would to share my 2 cents in this regard as a closure note.

Requirements

Assuming my laptop could be connected to the projector, I do not foresee any other requirements.

Speaker bio

I work for Intuit and lead the group responsible for Datacenter Network Engineering. Having iterated multiple approaches towards effective monitoring in my present and past assignments, I am passionate about sharing my experience – both wins and challenges - with our friends in the industry.

Slides

https://docs.google.com/presentation/d/1uU3YBGFbV-rlPwAPmSSYWg68UXUbcrKYez-EE7Xzv0k/edit?usp=sharing

Comments

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