工作中的 DevOps：协作和容器如何增强我们的集成平台.pdf

1、DevOps at Work:How Collaboration and Containers Supercharged Our Integration PlatformNathalie Gholmieh,Paul Jamason,Ashish Pandit,Sven-Olov Lindqvist,Rockford Mankini,Naval PatelCollaboration in IT ServicesA Story of Developer EmpowermentVSEmpower Developers by-Providing Enterprise-Grade Infrastruct

2、ure and Platform Services-Providing a Standard build and release process across all technologies-Central Architecture council to govern the technology stack-Collaboration on generating standard reusable development PatternsGoverning the COSTCross team collaborationIT Services-Before CollaborationIT

3、Services divisions were siloed,resulting in:Duplication of workLack of common development standards&best practicesVarying adherence to security requirementsUC IS-3,Secure Connect mandates require us to improve No organization-wide web application or integration platforms,CI/CD toolsEach division use

4、d their own technology stack(s)Programming language and platform decisions sometimes based on individual developers preferenceCan result in resource contention and technical debt IT Services-Before ContainersFirst:What is a Docker container,and why use them?Virtualized environment that runs at the o

5、perating system levelNo dependency conflicts between applicationsHigh scalability across multiple nodes,via container orchestrators like Kubernetes Improved security via isolation at user space level(e.g.,Jupyterhub user pods)Challenges IT Services faced before containers:Example:Java webfarm for en

6、terprise-level applicationsDependency conflicts from multiple applicationsDevelopers making direct changes in production environmentsDifficult to keep multiple(local)developer environments consistent;missing packages/libraries;versioning issuesAcademic Technology Services:Collaboration&Containers Em