Containers@Bayer DevOps in action The next level of virtualization Sep. 18, 2018 / Oliver Treichel / 1.0 /// Bayer 16:9 Template /// June 2018

Infrastructure is currently optimized for cost efficiency, not speed or flexibility Ordering new or changing existing infrastructure requires involvement of several specialized teams VMware, Operating System, Database, Middleware, Backup Every team processes requests sequentially, causing delays in the overall process Most standard tasks are out-sourced New demands need to be standardized before being made available Chicken-and-egg problem Infrastructure lifecycle does not match application lifecycle Infrastructure updates are disruptive Infrastructure configuration is not version controlled Different D, Q and P servers Lack of scalability, reusability and agility Today Goals /// Containers@Bayer /// Oliver Treichel /// September 2018

What is a container? Containers in logistics … Containers in IT … Store goods for transportation Logistics company does not care about content Protect goods while in transport Containers are locked during transport Standardized format for different vehicles One size fits all Containers in IT … Package applications for execution Contains everything to run the application Run applications in isolation No dependency on other components Run containers on different platforms On premise Cloud Available since more than 10 year /// Containers@Bayer /// Oliver Treichel /// September 2018

What is the difference between Containers and Virtual Machines? Container Runtime (i.e. Docker) provides isolation Hypervisor provides isolation App Containers are lightweight Virtual Machines are heavyweight OS level Virtualization Hardware level Virtualization Currently mostly Linux (limited support for Windows) Many Operating Systems to maintain Any Operation System possible Only one Operating Systems to maintain https://www.docker.com/resources/what-container  /// Containers@Bayer /// Oliver Treichel /// September 2018

The Application Lifecycle with Containers is different Container Images are immutable No patching, no updates, no backup Images are provided by a registry Container data is destroyed on shutdown Persistent state is stored in volumes Log files Database files New Containers are started using updated images e.g. new version of Tomcat Persistent state is still available Container writable Layer persistent Storage (Volume) Temp State Container Image V2 (immutable) Container Image V1 (immutable) Container Registry Container Image V2 (immutable) V1 V2 /// Containers@Bayer /// Oliver Treichel /// September 2018