Containers for Dummies

Issue link: https://insights.oneneck.com/i/1293607

Contents of this Issue


Page 52 of 76

CHAPTER 6 Ongoing Management, Advanced Deployment, and Tips for the Future 49 These materials are © 2017 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. Aiming for Reasonable Rollout Go for a crawl, walk, run approach to container adoption. Start small (crawl) with simple, well-known or proof-of-concept applications or processes. Then expand (walk) by ensuring all operations procedures work with containers. And finally (run), look at implementing modern application architecture design using containers. Getting the Culture Right Containers are often adopted to increase agility. In a traditional environment, technology teams often operate in silos. This means there are many handoffs between teams, which causes delays and often misconfiguration. When using containers, adopt cross- functional teams to minimize handoffs and to increase the over- all awareness of the environment that the applications are being designed, developed, deployed, and operated in. When creating cross-functional teams, make sure that the team understands — and is measured on — the outcomes that you're trying to achieve. HPE POINTNEXT: CULTURE CAN'T BE OVERSTATED The entire team needs to be involved from the outset when adopting containers. Bringing team members in halfway through the adoption leads to confusion, because the wider teams (Dev/Projects and Ops) requirements need to be considered throughout. Consider using communication techniques used by Management of Change practices to share information regularly. It has been widely recognized that as teams (especially cross-functional teams) grow, communication becomes harder. A technique used by some high-performing organi- zations is the two-pizza team concept. This approach states that no team should be larger than what two pizzas can feed (typically, eight people). This approach ensures that communication between team members is effective. However, it also requires that team members have a broad skill set and learn rapidly from each other in order to consider every level of an application and infrastructure stack within a cross-functional team.

Articles in this issue

Archives of this issue

view archives of eBooks/eGuides - Containers for Dummies