计算机安全移动互联网软件编程技术DockerCon课件报告Efficient Parallel Testing with Docker.pdf

Efficient Parallel Testing with Docker Laura Frank Engineer, Codeship Agenda 1. Parallel Testing: Goals and Benefits 2. DIY with LXC 3. Using Docker and the Docker Ecosystem Parallel Testing GOAL Create a customizable, flexible test environment that enables us to run tests in parallel Why? • Deploy new code faster • Find out quickly when automated steps fail If you’re still not sure why testing is important, please talk to me at the Codeship booth. Where? • For local testing, e.g. unit and integration tests run by a development team • On internal CI/CD systems • As part of a hosted CI/CD solution (like Codeship) How? • Performance optimization for serial testing tasks is limited • Split up testing tasks • Use containers to run multiple tests at once TASK PARALLELISM Run tasks across multiple processors in parallel computing environments Distributed Task Parallelism A distributed system of containerized computing environments takes the place of a single multiprocessor machine A container is a process, not a small VM Goal: Shorter Feedback Cycles Spend less time waiting around for your builds to finish. • Ship newest code to production faster • Be alerted sooner when tests fail Goal: More User Control Developers should have full autonomy over testing environments, and the way tests are executed. • Move testing commands to separate pipelines • Designate commands to be run serially or in parallel • Declare specific dependencies for each service Why not VMs? • Isolation of running builds on infrastructure • Challenges with dependency management • No clean interface for imposing resource limits • Infrastructure is underutilized which makes it expensive Containers, duh! • Impose resource limits and utilize infrastructure at higher capacity • Run customer