About the event
Cloud server management brings with it as many challenges as it offers conveniences. It is time to unbundle questions about:
- Resource allocation: how best to allocate manpower, time, money and infrastructure capacity?
- Scaling: how best to utilize capacity in the present, and factors involved in planning for the future?
- Security: which scenarios must you plan for, and how best to secure your data, applications and systems?
Who should submit a talk
- Work with cloud servers,
- Plan and manage infrastructure,
- Make decisions on technology and architecture for your organization,
submit a talk for any of the three events in this series.
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.
Proposals will be shortlisted and reviewed by an editorial team consisting of practitioners from the community. Make sure your abstract contains the following information:
- Key insights you will present, or takeaways for the audience.
- 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:
- A detailed outline, or
- Mindmap, explaining the structure of the talk, or
- Draft slides
along with your proposal.
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, request it when you submit your proposal in the field where you add your location. Rootconf Miniconf is funded through ticket purchases and sponsorships; travel grant budgets vary.
Cloud Sever Management Miniconf in Chennai: 25 November, 2017
Cloud Sever Management Miniconf in Mumbai: 8 December, 2017
Cloud Sever Management Miniconf in Delhi: 9 December, 2017
For more information about speaking, Rootconf, the Miniconf series, sponsorships, tickets, or any other information contact email@example.com or call 7676332020.
Lessons scaling operations to everyone @indix
At Indix we collect and process lots of data. As our data size grew so were the operational difficulties surronding them. When we were a team with small number of developers and a single ops person, using a centralised configuration management system made a lot of sense. Any changes would go through him resulting in a very less overhead. As we scaled our team that single person became a bottleneck for different teams. He wasn’t able to cope up with new things that individual teams wanted to try for their respective set of challenges. This lead to individual teams stepping up to manage their own infrastructure parts on AWS.
That’s when we realised we needed a more de-centralised, respective team owned configuration management across the organization. While most teams welcomed the change, some teams with no prior operational experience found this transition very hard. After a lot of attempts we started using a self-serviced, resource based scheduling for individual services for these teams.
Self managed infrastructure is a dream to any operational team in an organization, but it does come with it’s fair share of challenges.
In this talk, I’ll cover our problems, mistakes and learnings over the years on scaling the operations to everyone at Indix and how some our technology choices were influenced by them.
- Problems, mistakes and learnings
- When we were 5+ member team
- Focus on keeping infrastucture sane
- When we were 30+ member team
- Focus on scaling the infra knowledge and not the ops team
- When we were 60+ member team
- Focus on abstracting away the infra knowledge
- Tech Radar(s)
- Operability Checklist
- Current un-solved challenges
Ashwanth Kumar is a Principal Software Engineer working in Data Ingestion Team @indix. While he’s not fiddling with distributed Systems and data. He contributes to Open Source and helps organises meetups and tech events in the City. He writes Scala at work and Go at home.
- List of all the talks - https://github.com/ashwanthkumar/talks
- OSS - https://github.com/ashwanthkumar/