Overall, Dockercon did a good job connecting Docker users with information. In some ways, it was a very “let’s get down to business” conference without the open source collaboration feel of previous events. For enterprise customers and partners, that may be a welcome change.
Unlike past Dockercons, the event did not have major announcements or a lot of non-Docker ecosystem buzz. That said, I miss that the event did not have major announcements or a lot of non-Docker ecosystem buzz.
I think there’s a lot of pieces we’re still wishing away that aren’t really gone. (at 4:50)
Rather than repeat TheNewStack summary; I want to highlight the operational and integration gaps that we continue to ignore.
It’s exciting to watch a cluster magically appear during a keynote demo, but those demos necessarily skip pass the very real provisioning, networking and security work needed to build sustained clusters.
We dove into a discussion around significant trends in the container space, how open technology relates to containers and looked toward the technology’s future. We also previewed next month’s DockerCon, which is set for June 19-21 in Seattle.
Highlights! We think containers will be considered MORE SECURE next year and also have some comments about the linguistic shift from Docker to CONTAINERS.”
Here are my notes from the recording with time stamps if you want to skip ahead:
00:35 – What are the trends in Containers?
Rob: We are still figuring out how to make them work in terms of networking & storage
Dan: There are still a lot of stateful work moving into containers that need storage
Phil: We need to use open standards to help customers navigate options
2:45 – Are the changes keeping people from moving forward?
Phil: Not if you start with the right guidelines and architecture
Dan: It’s OK to pick one and keep going because you need to build expertise
Rob: RackN experience changed Digital Rebar to microservices was an iterative experience
5:00 Dan likes that there is so much experimentation that’s forcing us to talk about how applications are engineered
5:45 Rob points out that we got 5 minutes in without saying “Docker”
There are a lot of orchestration choices but there’s confusion between Docker and the container ecosystem.
7:00 We’re at OSCON, how far has the technology come in being open?
Phil thinks that open container initiative (OCI) is helping bring a lot of players to the field.
Dan likes that IBM is experimenting in community and drive interactions between projects.
Rob is not sure that we need to get everyone on the same page: open source allows people to pursue their own path.
10:50 We have to figure out how to compensate companies & individuals for their work
Dan: if you’ve got any worthwhile product, you’ve got some open source component of it. There are various ways to profit around that.
13:00 What are we going to be talking about this time next year?
Rob (joking) we’ll say containers are old and microkernels are great!
Rob wants to be talking about operations but knows that it’s never interesting
Phil moving containers way from root access into more secure operations
Dan believes that we’ll start to consider containers as more secure than what we have today. <- Rob strongly agrees!
17:20 What is the impact of Containers on Ops? Aka DevOps
Dan said “Impact is HUGE!” > Developers are going to get Ops & Capabilities for free
Rob brings up impact of Containers on DevOps – the discussion has really gone underground
19:30 Role of Service Registration (Consul & Etcd)
Life cycle management of Containers has really changed (Dan)
Rob brings up the importance of Service Registration in container management
20:30 2016.Dockercon Docket- what are you expecting?
Phil is speaking there on the contribute track & OCI.
Rob is doing the hallway track and looking to talk about the “underlay” ops and the competitive space around Docker and Container.
Dan will be talking to customers and watching how the community is evolving and experimenting