Miniconf on Cloud Server Management

On costs, scaling and securing cloud servers

##About the event

Cloud server management brings with it as many challenges as it offers conveniences. It is time to unbundle questions about:

  1. Resource allocation: how best to allocate manpower, time, money and infrastructure capacity?
  2. Scaling: how best to utilize capacity in the present, and factors involved in planning for the future?
  3. Security: which scenarios must you plan for, and how best to secure your data, applications and systems?

##Who should submit a talk

If you:

  1. Work with cloud servers,
  2. Plan and manage infrastructure,
  3. Make decisions on technology and architecture for your organization,

submit a talk for any of the three events in this series.

##Format

Each event is single-day, with about 4-5 short and long talks, 2-3 demos, one BOF, and a three-hour workshop on configuration management.

We are accepting proposals for:

  • 30-minute talks – which cover conceptual topics and case studies.
  • Crisp 15-minute talks – on new tools and techniques in cloud server management.
  • 5-10 min demos.
  • Birds of Feather (BOF) sessions, led by 1-3 persons from the community, on a relevant topic.
  • 3-hour hands-on workshops on configuration management.

##Selection process

Proposals will be shortlisted and reviewed by an editorial team consisting of practitioners from the community. Make sure your abstract contains the following information:

  1. Key insights you will present, or takeaways for the audience.
  2. Overall flow of the content.

You must submit links to videos of talks you have delivered in the past, or record and upload a two-min self-recorded video explaining what your talk is about, and why is it relevant for this event.

Also consider submitting links to the following along with your proposal:

  1. A detailed outline, or
  2. Mindmap, explaining the structure of the talk, or
  3. Draft slides.

##Honorarium for selected speakers; travel grants

Selected speakers and workshop instructors will receive an honorarium of Rs. 3,000 each, at the end of their talk. Confirmed speakers and instructors also get a pass to the conference and networking dinner. We do not provide free passes for speakers’ colleagues and spouses.

Travel grants are available for 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, mention this in the field where you add your location. Rootconf Miniconf is funded through ticket purchases and sponsorships; travel grant budgets vary.

##Important dates

Cloud Sever Management Miniconf in Chennai: 25 November, 2017

Cloud Sever Management Miniconf in Mumbai: 8 December, 2017

Cloud Sever Management Miniconf in Delhi: 20 January, 2018
Call for proposal for Delhi Miniconf closes on 15 November

##Contact details:
For more information about speaking, Rootconf, the Miniconf series, sponsorships, tickets, or any other information contact support@hasgeek.com or call 7676332020.

You can propose a talk in the relevant edition below

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Ambarish KC

@ambrishkc

FireStorm - An alerting system for your infra

Submitted Nov 1, 2017

We are living in the era of microservice and serverless architecture. More the moving parts in a system higher the probability of unhandled bugs/errors. We have numerous services like sentry, datadog etc to monitor our infra and log our excpetions, but most of the times developers get 100s of notification per day from these services. Naturally some of the critical notifications might get lost or would be seen at a later point in time. So the best option to react and fix these mission critical issues is to alert the respective team members by making phone calls. In this talk we’re gonna discuss and build a robust alerting system which would give instantaneous alerts.

Key takeaways would be any web or back-end developer can set up an alerting system (make phone calls, push to slack and send sms & emails) at almost negligible COST

Outline

  • Setting up of AWS alarms and twilio
  • Write a Django API server which accepts POST calls for different types of triggers
  • How to integrate AWS cloudwatch alarms with the Django API server
  • Code to trigger phone calls, push slack message, send sms and email
  • Demo of the product
  • How this project can be extended for various other functionalities like pager duty, modify auto scaling policies, run play books, predict crashes etc

Note: All the code will be written in Python

Speaker bio

Ambarish is a back-end engineer @ MadStreetDen building robust scalable systems serving millions of users. Designed, built and deployed back-end systems from scratch.

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 community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more