DevConf 2017

Scaling platforms and services. Co-hosted by Rootconf, Red Hat and the Linux Foundation.

Theme

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.

Format

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.

Selection Process

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.

Selection Process Flowchart

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.

Important Dates:

Deadline for submitting proposals: 10 April, 2017

Final schedule for the Platforms track: 20 April 2017

Conference dates: 11-12 May, 2017

Contact

For more information about speaking proposals and tickets, contact info@hasgeek.com or call +91-7676332020.

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Dipak Pawar

@dipakpawar

Integration testing of apps deployed on Kubernetes using Arquillian-Cube & Forge

Submitted Apr 10, 2017

Arquillian is highly extensible testing platform that enables developers to easily create automated integration, functional and acceptance tests for Java services.

Arquillian Cube is an extension of Arquillian using which you can manage Docker containers,
Kubernetes Deployment as a part of your test life cycle. No more containers lifecycle and deployment hassle. let’s focus on test logic, not infrastructure boilerplate.

Kubernetes is production grade container orchestration system. It’s quite difficult to do integration testing for your apps deployed on Kubernetes cluster.

How can a developer make sure that required Pods, Services, Replica Sets are up & running & integration between them is working fine?

It’s hard for developer as he has to deploy app on cluster using resources config manually, then he has to verify manually that all required resources are up & running. Another possible solution is to write some shell scripts to verify your expected output, so he can add it as a build step for CI pipeline.

Developers need something simple using which
- He can create & manage temporary namespace for your tests.
- He can deploy all Kubernetes resources required to create your environment.
- Once everything is ready, run your tests.
- He can access all resources like KubernetesClient, Pods, Replica Sets, Services as a part of tests. So developer can make sure that all resources are up & running as per expectation.
- Once all resources are available, he can verify integration between them is working fine. If not send the logs of what’s going on.
- After test completion make sure to cleanup namespace & all created resources.

So we need a solution that is simple to use for developers. And that is what we are building using arquillian-cube.

I would like to show how can developer create simple test within few minutes using Forge,
working demo and examples that will showcase the problem space and how arquillian-cube will help you to solve this problem?

Outline

This talk will showcase that What will happen if you don’t have integration testing of apps deployed on Kubernetes cluster?

Forge Addon for getting started to write a test within few minutes.

How can arquillian-cube will help you for deployment & to make all resources available to your tests?

How can you make sure everything is integrated properly for apps deployed on Kubernetes?

Speaker bio

Dipak Pawar contributes to project Arquillian-Cube, Forge Addon for Arquillian. He has presented in local meetups.

He is involved in these projects from last 9 months. He is active in the local meetups like Core Java, BangloreJUG, Kubernetes Bangalore meetup group.

He works as Software Engineer at Red Hat, in Developer tools team where he builds tools around testing feature area.

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 forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more