Dec 2017
4 Mon
5 Tue
6 Wed
7 Thu
8 Fri 09:00 AM – 05:40 PM IST
9 Sat
10 Sun
Dec 2017
4 Mon
5 Tue
6 Wed
7 Thu
8 Fri 09:00 AM – 05:40 PM IST
9 Sat
10 Sun
##About the event
Cloud server management brings with it as many challenges as it offers conveniences. It is time to unbundle questions about:
##Who should submit a talk
If you:
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:
##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:
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:
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.
##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: 9 December, 2017
##Contact details:
For more information about speaking, Rootconf, the Miniconf series, sponsorships, tickets, or any other information contact support@hasgeek.com or call 7676332020.
Srujan A
@acsrujan
Submitted Nov 6, 2017
Key take-aways:
First 5 minutes: Assumptions of the applications running behind. Key metrics to be observed per application; Setting up all the requirements.
Next 5 minutes:
What’re the metrics to look at, how to measure them and how to validate your decision of allocation.
Recommended infrastructure code practices.
Handling production failures due to under-provision and how to solve the incident quickly.
Next 2 minutes: Buffer for above topics.
Next 3 minutes: QnA.
I’m submitting for 15 minutes. However, if the organizers consider topic to be good for 30 minutes, I can expand topics.
I’ve worked with AWS and Google Cloud for the past 3 years and developed various strategies, to minimise manual interruption on managing cloud infrastructure.
WebEngage, where I currently work, handles communication and engagement of > 45 million users. Having this scale on several microservices and calculating how much each micro-service is costing us, to find out ROI, made me experienced in understanding the requirements and nearly automate the resource allocation.
Dec 2017
4 Mon
5 Tue
6 Wed
7 Thu
8 Fri 09:00 AM – 05:40 PM IST
9 Sat
10 Sun
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}