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: 20 January, 2018
For more information about speaking, Rootconf, the Miniconf series, sponsorships, tickets, or any other information contact email@example.com or call 7676332020.
Setting up a CI/CD pipeline with Jenkins
Are you the person in your team who gets called in for deploying applications?
Have you ever had to sacrifice your sleep because someone fixed a minor typo and CEO wanted you to deploy the changes right then?
Have you wondered what if … the application could deploy itself?
Or perhaps, why can’t everyone deploy the damn thing themselves?
Here we shall spend a couple of hours learning how to configure a CI/CD pipeline using the time tested Jenkins CI server to help you automate the deployment process such that code pushed goes straight to the server wihout you having to move your finger.
Of course its a tad bit more complicated than what the pitch makes it sound like, but then we can get to it in the last hour of the workshop.
- Jenkins terminologies and jargons
- Outline of the workshop
Part 1: Primarily
Participants configure a simple web application for automated deployment.
- gain access to the jenkins server setup for this very workshop.
- gain familarity with various console panels.
- configure the pipeline, to trigger deployment upon code change in their repository.
- make changes in the forks of the repo and see the changes get deployed on server.
Part2: If time permits
Setting up a jenkins server.
Post hands-on discussions:
- need for continuous deployment
- cost of setting up the CI/CD pipeline in terms of effort involved.
- need for automated tests and how to get the dev-team to write them
Participants should be able to launch a small VM to deploy the application to.
Basics like how to setup ssh keys and how to login to the server shall not be covered during the workshop.
Developer who automates himself off his job.