Comments
Containers + DevOps: Power Couple
Threaded  |  Newest First  |  Oldest First
Charlie Babcock
100%
0%
Charlie Babcock,
User Rank: Author
9/3/2014 | 3:56:06 PM
Why not update an existing container without creating a new one?
Isn't possible, Langdon, for a developer to update an application tier inside Docker, without disturbing the layers around it? That is, a silver bullet update, affecting one layer in a production system and leaving others unchanged? Granted such a change must be tested in staging before going back into production. You appear to recommend generating a new point release of the application in development, then swapping in the new container. Isn't there a way to work with the existing one? 
Stratustician
100%
0%
Stratustician,
User Rank: Ninja
9/4/2014 | 9:10:38 AM
Re: Why not update an existing container without creating a new one?
From a security perspective, you would need to get security blessing during the app creation stage, which in many cases might work provided you have a security rep on the DevOps team.  For other organizations, I wonder if using containers, and having to create new containers (in a sense) if you are updating/patching the application might mean more frustration from the security team if they have to go ahead and test again that the security policies are in place.  Is there a way to embed security controls in the container as a default as part of the container certification process so that any new containers would carry the same policies?
zerox203
100%
0%
zerox203,
User Rank: Ninja
9/8/2014 | 11:15:01 AM
Re: Containers + DevOps
It is true that DevOps is changing the way we look at pretty much everything. In a way, it's like a lot of new methodologies: "agile", BYOD, etc. It's not about adding something new, it's about taking down barriers and letting people do their jobs the way they've always wanted. Seems simple enough, but it took as a while to get there in terms of security policies and business, and as you point out, it comes with some headaches of it's own. There is a reason many businesses are apprehensive about these policies, but I think the benefits are starting to far outweigh any downsides.

Containers seem like a great solution for developers wanting things just how they like them, and it's not something I'm too read up on. Thanks for the primer! It's good to see some disclosure too - the full version of the article on Dr. Dobb's (a good read!) notes that it's not 'all sunshine and rainbows' with containers. That's kind of a rarity in the IT-hype blogosphere. To be honest, this sounds a little heady for my software dev needs, but I'll be sure to pass it on!


Register for InformationWeek Newsletters
White Papers
Current Issue
Video
Slideshows
Twitter Feed
InformationWeek Radio
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.