Containers Survival Guide for Infrastructure
Containers are coming! Get ready now (if you haven’t already).
- The major impediments to containers in a production environment adoption are concerns over security and management at scale.
- Organizations have already made significant investments in machine virtualization (virtual infrastructure) and are unlikely to abandon that investment.
- Non-containerized applications and services will continue to need to be hosted and serviced into the future.
Our Advice
Critical Insight
- Containers don’t replace VMs, yet: It will be beneficial for all near term to adopt containers on virtualized infrastructure.
- The future of software packaging: You will need to adopt containers in the near future. Software will soon begin to ship in containers, and you will be required to host them.
- Not just a technology change: Containers require a change in people and process, with different/new development and operations roles and responsibilities in new agile processes.
Impact and Result
- IT infrastructure groups should resolve to create container-ready infrastructure that will meet both the requirements of developers and apps managers and the availability, recoverability, and security requirements of the enterprise.
- In the short term, the best solution is likely to be hosting containers on container-ready VMs running Linux and a container engine like Docker. This may not be optimal for performance but will be optimal for securing and assuring availability for the underlying infrastructure.
- Longer term, enterprises should pilot running containers on bare metal to become familiar with the emerging tools for managing containers. The future is likely a hybrid of virtualized infrastructure and bare metal container infrastructure.
About Info-Tech
Info-Tech Research Group is the world’s fastest-growing information technology research and advisory company, proudly serving over 30,000 IT professionals.
We produce unbiased and highly relevant research to help CIOs and IT leaders make strategic, timely, and well-informed decisions. We partner closely with IT teams to provide everything they need, from actionable tools to analyst guidance, ensuring they deliver measurable results for their organizations.
What Is a Blueprint?
A blueprint is designed to be a roadmap, containing a methodology and the tools and templates you need to solve your IT problems.
Each blueprint can be accompanied by a Guided Implementation that provides you access to our world-class analysts to help you get through the project.
Need Extra Help?
Speak With An Analyst
Get the help you need in this 3-phase advisory process. You'll receive 8 touchpoints with our researchers, all included in your membership.
Guided Implementation 1: Analyze the business case for containers
- Call 1: Identify key stakeholders, and explore how containers can benefit your organization.
- Call 2: Assess your need for containers by examining the deployment needs of your applications and workloads
Guided Implementation 2: Develop a container adoption strategy
- Call 1: Explore the differences between the various application and workload deployment models.
- Call 2: Develop a plan for piloting containers on bare-metal infrastructure.
- Call 3: Assemble the ideal container software ecosystem.
Guided Implementation 3: Develop and communicate the roadmap
- Call 1: Establish best practices between development and operations; build a collective agreements document.
- Call 2: Build roadmap and identify container adoption timeline for milestones.
- Call 3: Assemble and executive communications report for stakeholder communication.
Contributors
- Brandon Philips, CTO, CoreOS
- Daniel Walsh, Consulting Engineer – Containers/Docker Team Lead, Red Hat
- David Aronchick, Product Manager, Google
- David Messina, VP Marketing, Docker
- Kim Weins, VP Marketing, RightScale
- Mathew Lodge, COO, Weaveworks
- Sean Chittenden, Engineering Manager, HashiCorp
- Shannon Williams, VP Sales and Marketing, Rancher Labs
- Sheng Liang, CEO, Rancher Labs
- Tim Miller, VP Engineering, RightScale
- 1 anonymous contributor