There is a huge disconnect between the DevOps world and most current enterprise IT organizations. One element in the gap is that developers do not want to know about infrastructure. Another is that the operations team does not trust developers to make changes to the production infrastructure. Developers want to focus on their application and the value it delivers to the organization. Developers want to know the characteristics of the infrastructure but do not want to build it or operate it. As a result, DevOps does not mean the end of the operations team. In fact, I see the reverse as being essential. The operations team is absolutely critical to the success of DevOps methodologies. The developers must be able to trust that the infrastructure has specific characteristics: characteristics like performance, connectivity, availability, and uniformity. To enable this trust, I believe that the operations teams are going to need to become more like developers. I call this OpsDev.
Andy Jassy, SVP of AWS, made a ton of new announcements in his keynote speech yesterday at the 4th annual AWS re:Invent conference in Las Vegas. The conference has grown to nearly 20,000 attendees with around 38,000 watching the live streaming event. Continue reading AWS re:Invent Keynote: 7 Basic Freedoms
In this ever-changing world of IT, the legacy of today was once the future of yesterday: namely, hypervisors. Hypervisors are now considered legacy, even though they are seriously underutilized due to issues with fear, uncertainty, and doubt around using these resources to their fullest. The new technology is containers. However, where are the operational tools to support containers? Where are the procedures? Where are the developers who understand distributed systems? We are moving toward containers at lightning speed without answers to those questions and many more. To move to containers today, we need a strategy.
Docker, Kubernetes, and Mesos are generating a lot of discussion as the future of application development. We are seeing significant progress towards having these methodologies adopted by enterprises for application development. We have even been hearing that VMware is the new legacy, since containerised applications don’t always need a hypervisor. These “modern application” methods are replacing older client server and early web architectures as the preferred way to develop applications. Some people are saying that this means the end of the road for the old applications and the infrastructures that run these applications.
In all of life, we try to avoid the difficult things and handle the easy things first. Sometimes, leaving the hard things is a good idea. We sometimes realize there is an easy way to deal with the hard problem, or someone else deals with it. Sometimes it’s a bad idea. Leaving a sore tooth until it needs a root canal is a bad idea that causes lots of pain.
I have been following containers for quite some time now. A year ago it was safe to say that container technologies like Docker were far from production ready when it came to security. What I have seen over the past year is a ton of development towards closing that gap. For this post, I’ll focus on Docker. Continue reading The Container Security Gap is Rapidly Closing