Infrastructure platforms have evolved from a phase of mean-time-to-recovery to mean-time-to-service availability. They include features that run across the entire stack to enable resiliency, monitoring, dynamic orchestration of capacity and easy deployment fabric for application workloads.
We are inviting full-length and crisp talks to share problem-solution approaches:
- What problems did you solve with one platform which you couldn’t solve with any other technology? Why was it the case?
- What features have worked for your use-case? Why?
- Which features did you build on top of available platforms? How can they work for others?
Content for DevConf is intended to be a “from-the-trenches approach”.
The theme of DevConf is aligned with the general theme of Rootconf 2017. The objective is to provide an initial set of topics around the broad notion of infrastructure platforms for the audience. This is expected to set the course for an extended series of expert sessions during 2017-18.
Who should attend?
DevConf will be of importance to developers building application architecture around burst capacity. The discussions focusing on storage, orchestration, scalability and monitoring using on-going technologies available upstream provide viable options of components to choose from and include in software designs.
The track will be of interest to developers and contributors in the following domains:
- Elastic deployment fabric.
- Scaled storage.
- Software defined networking.
- Containerized workload deployment teams.
Why DevConf at Rootconf
The technology space in India has been working for the past couple of years around workload deployment in containers; elastic infrastructure fabric; scaled storage; software defined networking. There are sizeable communities which span from developers to DevOps roles as consumers of the feature improvements.
Red Hat and the Linux Foundation have a history of close collaboration in organizing domain specific conferences such as Vault to address the issue of new problems in infrastructure platforms.
Rootconf, Red Hat and Linux Foundation have partnered to organize and co-host DevConf at Rootconf 2017 to pull together a cohesive group that is working at the edge of technology - by contributing to development conversations and deployment scenarios.
DevConf is part of Rootconf. Tutorials and talks under this track will be held in the banquet hall:
- Day 1: tutorials and 101 sessions.
- Day 2: short and full length talks + flash talks on use cases and problem-solution case studies.
We are inviting proposals for:
- Deep-dive tutorials and 101 sessions on platform technologies.
- Full-length 40-minute talks on case studies.
- Crisp 15-minute how-to talks.
- Flash talks for 5 mins showing a demo or explaining tips and tricks.
Proposals will be filtered and shortlisted by the Editorial Panel of the Platforms track.
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 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 one week of submitting your proposal.
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.
Deadline for submitting proposals: 10 April, 2017
Final schedule for the Platforms track: 20 April 2017
Conference dates: 11-12 May, 2017
For more information about speaking proposals and tickets, contact firstname.lastname@example.org or call +91-7676332020.
Microservices infrastructure using Docker + Mesos + Marathon
Microservices help in breaking large software projects into loosely coupled pieces, which then communicate with each other. It has its own pros and cons but the challenges come while building an infrastructure for the same. The easier it gets to understand the system and interactions as a result of such an architecture, harder it gets in making sure deployment strategies mimic the understanding since they have multiple deployables having different levels of interactions and dependencies.
This topic revolves around defining way/s of deploying microservices.
I would like to share my experience/s which our team/s had while building and deploying microservices.
1. Strategies we used for designing the infrastructure.
2. Challenges we had while doing so and how did we solve them.
3. The composition of services for running functional tests across, running contract tests, orchestrating them for deploying on an environment, on demand deployment of a single service without getting the environment down
I am an application developer at ThoughtWorks. Over these past 3.5 years of my experience, I have got to work in completely different domains and technologies. While setting up continuous integration and continuous deployment for my last two projects based on microservices, I have evolved through the knowlegde, understanding and ideas of doing these things better.
Owning to the challenges that arise while building and deploying these systems, I intend to share my experince. The audience will get to understand diffferent ways of acheiving infrastructure setup in such an architecture.