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

Amit Raj

@amit894

Efficient way to manage environments in AWS

Submitted Feb 14, 2017

While AWS makes it extremely easy to build and manage environments, it can still consume considerable amount of time to manage environments especially for teams which have not optimized and automated all the key steps needed in managing environments thru various phases. In this talk we aim to share our experiences in managing one such fairly complex environment servicing few 100K requests per day in production, the optimizations we have put in and the lessons we have learned.

Outline

00-02 Setting up the context why managing environments the right way is important

Managing an environment means, first we need to build it, deploy code + configuration on it for various prod and pre-prod needs, operate it seamlessly across multiple parallel releases and monitor and recover from various failures/alerts. Next few sections highlight few of the key aspects that one should focus during various phases identified above which come as part of managing an environment efficiently.

03-09 Building Environment :- Best Practices using Cloud Formation

Build: This phase revolves around setting up the building blocks of any environment i.e servers, databases, storage etc. Using the following Cloud-formation techniques we can add the ability to build, configure and changes these environments rapidly.
• Use of Single Master Template

• Ability of Same Template to scale differently according to traffic.

• Use of user-data to setup the right meta-data and deployment triggers.

10-13 Deploying Code :- Efficient Techniques to boot up instances

Deploy: The key to successful code deployment is the ability to deploy applications at scale with less boot time, configurability of the deployment code as per environment needs. While technologies behind this deployment code vary, the implementation follows these principles:
• Custom baked Machine Images (AMI’s) for each type of server in the environment

• Using chef roles to break-down deployments into logical flows (cookbooks and recipes).

• Ability to over-ride the deployment as per environment configurations.

14-17 Operate :- Rollback and Promote Techniques

Operate: Successful operational model thrives on maintaining the right states of the application and associated load-balancers. To achieve efficiencies in releases, it is vital that the following capabilities are integrated as part of infrastructure of and effectively automated without any human intervention

• Blue- Green Deployment for high availability.

• Promotion plan for releases.

• Rollback plan for any failures

18-20 Monitor :- Building the right set of Alarms and triggers.

• Defining Cloudwatch metrics which triggers these alarm systems e.g. Free Space on Databases, Healthy EC2 instance count etc.

• Defining level of alarms depending on the level of CloudWatch metrics failure

• Default Auto-scaling

o Time-based scaling

o Based on triggers of alarms.

In summary, approaching the environment management with mindset of building right capabilities for each of the above elements will lead to shorter delivery cycles, better predictability into failures, time-saving for customer releases and eventually more reliable dynamic infrastructure. Hence with this presentation we have discussed the building right muscles into our environments and the long term benefits of the seeding the same.

Speaker bio

Amit Raj, Software Engineer at Intuit, has a decent track record of being part of teams which have moved the right needle on the dimensions of operational excellence through Non-Functional Testing using Automated Systems, DevOps model, Data Integrity. Through each of the teams and role he has has followed the give key principle of “Reducing the time for a single commit to be delivered to the customer” and “Efficiently building applications and environments to scale”

Slides

http://www.slideshare.net/amii894/efficient-way-to-manage-environments-in-aws-72345800

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