Kategorie: Kubernetes

Docker at Microsoft Build 2017

Build is Microsoft’s premier developer event, run annually. This year Docker, Inc. and containers were everywhere, starting with a dedicated container pre-day, then with constant traffic to the Docker booth, and many shared container success stories.

Container Fest Pre-Day
Build is usually a three-day event, but this year saw the very first pre-day – run jointly by Docker and Microsoft. “Container Fest” was a whole-day event focused on containers and Docker, running on Windows and Linux, on-premises and in Azure.
There were 12 sessions throughout the day, presented by engineers and architects from Microsoft and Docker, Inc. They covered everything from the internals of Docker on Windows Server, through modernizing .NET Framework apps with Docker, to the options for running Docker containers on Azure.
A popular first step for modernizing traditional Windows applications is to use Image2Docker, which we demonstrated at the event. Image2Docker can extract existing applications from Windows machines into Dockerfiles, so you can automate the conversion of your app landscape to Docker. You can see Image2Docker in action from our session at DockerCon:

Over 300 people were at the Container Fest pre-day, and when the sessions had finished, they stayed on to run through the Hands-On Labs from DockerCon. Just like at DockerCon, we provisioned virtual machines in Azure for attendees to use for working through the labs, and the experts were available for help and advice.
The DockerCon 2017 labs cover a range of topics, including orchestration and networking, Docker Enterprise Edition and Docker Cloud, and running Docker containers on Windows. The labs are open source on GitHub now, as part of the main Docker labs repo. If you’re looking to get started with Docker on Windows, these labs give you a great roadmap:

Windows 101 – learn the basics of Docker and Windows containers
Modernize .NET Apps, for Ops – see how to package an ASP.NET app as a Docker image
Modernize .NET Apps, for Devs – modernize an ASP.NET by breaking features out into Docker containers
SQL Server – learn how to run SQL Server in Docker containers and package up a custom database schema into a Docker image

Partner Hub
Hundreds of attendees dropped into the Docker booth in the MS Build Conference Hub expo area to ask for help and advice, tell us about their Docker journey, or just to say Hi. The level of Docker experience was everything from complete beginners to folks running production workloads on Docker Enterprise Edition.
We had some videos running on loop, which were people found very useful – and these are on YouTube so you can check them out yourself. To start, there’s the Docker on Windows 101, which introduces you to how containers work on Windows:

And for the journey into production, we have a tour around Docker Datacenter, the Containers-as-a-Service (CaaS) platform available with Docker Enterprise Edition standard and advanced. 

The crack team from Docker were kept busy through the whole event, had a great time, and are thoroughly looking forward to next year.
Learn More:

Try out the DockerCon 2017 Hands-On Labs for yourself
Get the Modernize Traditional Apps kit to plan your MTA program with Docker
Scott Guthrie from Microsoft is on a European tour – Docker will be joining in Amsterdam, London and Dublin
Try out Image2Docker for Windows and Image2Docker for Linux
Learn more about Docker and Microsoft together

Highlights from #MSBuild: Internals of #Docker on Windows, modernizing .NET framework apps &…Click To Tweet

The post Docker at Microsoft Build 2017 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

The Latest Docker Certified Container and Plugins for March and April 2017

The Docker Certification Program provides a way for technology partners to validate and certify their software or plugin as a container for use on the Docker Enterprise Edition platform.  Since the initial launch of the program in March, more Containers and Plugins have been certified and available for download.
 
Certified Containers and Plugins are technologies that are built with best practices as Docker containers, tested and validated against the Docker Enterprise Edition platform and APIs, pass security requirements, reviewed by Docker partner engineering and cooperatively supported by both Docker and the partner. Docker Enterprise Edition and Certified Technology provide assurance and support to businesses for their critical application infrastructure.
Check out the latest Docker Certified technologies to the Docker Store:

Dynatrace provides monitoring Docker applications and Docker clusters out of the box.
{code} by Dell EMC certified a number of REX-ray volume plugins for the following: REX-Ray for AWS EFS, REX-Ray for AWS EBS, REX-Ray for S3FS, REX-Ray for Isilon, REX-Ray for GCE and REX-Ray for ScaleIO.
HPE OpsBridge Agent provides monitoring of Docker applications with HPE Operations Bridge.
CoScale Agent provides a lightweight solution for monitoring the performance of your Docker containers and microservices in production.
NexentaEdge Docker NFS Volume Plug-In for the Nexenta Scale-Out High Performance Multi-Service Solution with Cluster-Wide Deduplication and Compression.
Oracle: As announced at DockerCon, many Oracle products are now available on Docker Store including Oracle Coherence, Oracle WebLogic Server, Oracle Java 8 SE (Server JRE), and Oracle Instant Client.
VMware Vsphere Volume Service for Docker enables the ability to run stateful container applications on VMware vSphere.
Weaveworks Network Plugin provides simple, resilient multi-host Docker networking.

Check Visit Docker Store regularly to browse and download the latest Certified Containers and Plugins. Interested in publishing? Sign up here to start posting to Docker Store.
 

The latest Docker Certified Containers and Plugins on #Docker StoreClick To Tweet

Continue your Docker journey with these helpful links:

Try Docker Enterprise Edition for free
Browse the Docker Store for Certified Containers and Certified Plugins
Sign up to become a Docker Store Publisher

The post The Latest Docker Certified Container and Plugins for March and April 2017 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

DockerCon Hands-on Labs now online

One of more popular activities at DockerCon is our Hands-on Labs, where you can learn to use the Docker tools you see announced on stage, or talked about in the breakout sessions. This year we had eight labs for people to work through, ranging from 20 minutes to an hour in length.

We’ve now moved these apps into the Docker Labs Repo so that everyone can use them. The Docker Labs Repo is where we put a bunch of learning content for people who want to learn Docker, from beginner to advanced security and networking labs.
Here are the new labs:
Continuous Integration With Docker Cloud
In this lab, you will learn how to configure a continuous integration (CI) pipeline for a web application using Docker Cloud’s automated build features.
Docker Swarm Orchestration Beginner and Advanced
In this lab, you will play around with the container orchestration features of Docker. You will deploy a simple application to a single host and learn how that works. Then, you will configure Docker Swarm Mode, and learn to deploy the same simple application across multiple hosts. You will then see how to scale the application and move the workload across different hosts easily.
Securing Apps with Docker EE Advanced / Docker Trusted Registry
In this lab, you will integrate Docker EE Advanced in to your development pipeline. You will build your application from a Dockerfile and push your image to the Docker Trusted Registry (DTR). DTR will scan your image for vulnerabilities so they can be fixed before your application is deployed.
Docker Networking
In this lab you will learn about key Docker Networking concepts. You will get your hands dirty by going through examples of a few basic networking concepts, learn about Bridge and Overlay networking, and finally learning about the Swarm Routing Mesh.
Windows Docker Containers 101
Docker runs natively on Windows 10 and Windows Server 2016. In this lab you’ll learn how to package Windows applications as Docker images and run them as Docker containers. You’ll learn how to create a cluster of Docker servers in swarm mode, and deploy an application as a highly-available service.
Modernize .NET Apps – for Devs
You can run full .NET Framework apps in Docker using the Windows Server Core base image from Microsoft. That image is a headless version of Windows Server 2016, so it has no UI but it has all the other roles and features available. Building on top of that there are also Microsoft images for IIS and ASP.NET, which are already configured to run ASP.NET and ASP.NET 3.5 apps in IIS.
This lab steps through porting an ASP.NET WebForms app to run in a Docker container on Windows Server 2016. With the app running in Docker, you can easily modernize it – and in the lab you’ll add new features quickly and safely by making use of the Docker platform.
Modernize .NET Apps – for Ops
You’ll already have a process for deploying ASP.NET apps, but it probably involves a lot of manual steps. Work like copying application content between servers, running interactive setup programs, modifying configuration items and manual smoke tests all add time and risk to deployments.
In Docker, the process of packaging applications is completely automated, and the platform supports automatic update and rollback for application deployments. You can build Docker images from your existing application artifacts, and run ASP.NET apps in containers without going back to source code.
This lab is aimed at ops and system admins. It steps through packaging an ASP.NET WebForms app to run in a Docker container on Windows 10 or Windows Server 2016. It starts with an MSI and ends by showing you how to run and update the application as a highly-available service on Docker swarm.
So check out these labs, or head on over the Docker Labs repo and check out the other great content we have there. And if that doesn’t satisfy you desire for hands-on learning, come to DockerCon Europe in October, where we’ll have yet more labs for you to try out the very latest in Docker tech.

More Hands-on Learning with the #DockerCon Labs, now available to allClick To Tweet

More Resources

Check out the Docker Labs repo for this and many more tutorials
Register for an upcoming Docker Webinar
Attend an upcoming Docker event near you

The post DockerCon Hands-on Labs now online appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Mentorship in the Docker Community: How you can get involved

Mentorship is an important part of the Docker Community. Over the past few global event series like the Docker Birthday #3 and Mentor week last year, advanced users attended their local event and helped attendees work through training materials. As interest in mentorship continues to grow, we’re excited to grow our programs and provide more opportunities for the community to get involved.

New this year at DockerCon, we organized a Mentor Summit for attendees to learn the ins and outs of being an awesome mentor both in industry and in the Docker Community. Check out the talks below and learn how you can get involved.
Anna Osswoski – How to Mentor and be a Great One

View Anna’s slides here.
Sebastiaan van Stijn – How To Contribute to Open Source

Jérôme Petazzoni – A DockerCon 2017 Recap: give a talk in your local community

Are you an advanced Docker user? Join the Docker Mentor Group!
With over 280 Docker Meetup groups worldwide, the Docker online Community Group + Slack, and other programs, there is always an opportunity for collaboration and knowledge sharing. Mentors should have experience working with Docker Engine, Docker Networking, Docker Hub, Docker Machine, Docker Orchestration and Docker Compose.
Sign up as a mentor!
Learn about Mentorship in the Docker Community:

Join the online Community Mentor Group
Watch the DockerCon Recap Online Meetup recording
Review Docker Meetup Content (DMC) DockerCon 2017 Highlights!

Learn how to be a great mentor in the #docker community! Talks by @jpetazzo @OssAnna16 &…Click To Tweet

The post Mentorship in the Docker Community: How you can get involved appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

DockerCon Europe Registration and Call for Proposals are OPEN

DockerCon 2017 in Austin was amazing! We are still on a high from the energy and excitement that is created when 5,500 members of the Docker Community are in one place. Containers are everywhere, and the learning, inspiration and networking that those four days brings is unrivaled. We welcomed amazing speakers, made tons of meaningful connections and are already geared up to do it again for DockerCon Europe: October 16 – 19th in Copenhagen! Early Bird registration is now open, hurry up and get your ticket before they sell out.
Register for DockerCon Europe!
 

In addition, today we opened the DockerCon Copenhagen Call for Papers. We hope that you were inspired by the Moby Project and LinuxKit announcements and are looking forward to your submissions on the following:
Using Docker
Has Docker technology made you better at what you do? Is Docker an integral part of your company’s tech stack? Do you use Docker to do big things?
By giving concrete, first-hand examples, tell us about your Docker usage, share your challenges and what you learned along the way, and inspire us on how to use Docker to accomplish real tasks. When attendees leave your session, they should understand how to apply your take-aways to their use case.
Deep Dives
Share your code and demo heavy deep-dive sessions on what you have been able to transform with your use of the Docker stack. Entice your audience by going deeply technical and teach them how to do something they haven’t done.
Moby and Friends
Do you have a cool Moby use case? Are you using LinuxKit or Docker plumbing in your projects? Share the ways you are using Docker’s open source components to build technology that solves real problems.
Cool Hacks
Show us your cool hacks and wow us with the interesting ways you are using Moby or Docker plumbing in your projects. Or share the interesting ways you are pushing the boundaries of Docker. DockerCon Austin 2017’s cool hacks included: Play with Docker and FaaS. 
The deadline for submissions is  June 13th at 11:59 PST.
Submit a talk
So, what happens next?
After a proposal is submitted, it will be reviewed initially for content and format. Once past the initial review, a committee of reviewers from Docker and the industry will read the proposals and select the best ones. There are a limited number of speaking slots and we work to achieve a balance of presentations that will interest the Docker community.
We’re looking forward to reading your proposals!
Learn more about DockerCon: 

Check out the DockerCon 2017 website to learn about speakers and sponsors
Watch the DockerCon 2017 videos
Sign up to receive DockerCon News

#DockerCon Europe CFP is now open! Submit your talk before June 13thClick To Tweet

The post DockerCon Europe Registration and Call for Proposals are OPEN appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker Enterprise Edition Brings New Life Back to Legacy Apps at Northern Trust

Many organizations understand the value of building modern 12-factor applications with microservices. However, 90+% of applications running today are still traditional, monolithic apps. That is also the case for Northern Trust – a 128-year old financial services company headquartered in Chicago, Illinois. At DockerCon 2017, Rob Tanner, Division Manager for Enterprise Middleware at Northern Trust, shared how they are using Docker Enterprise Edition (EE) to modernize their traditional applications to make them faster, safer, and more performant.
Bringing Agility and Security to Traditional Apps
Founded in 1889, Northern Trust is a global leader in asset servicing, asset management, and banking for personal and institutional clients. Their clients expect best-of-breed services and experiences from Northern Trust and Rob’s team plays a large role in delivering that. While their development teams are focused on microservices apps for greenfield projects, Rob is responsible for over 400 existing WebLogic, Tomcat, and .NET applications. Docker EE became the obvious choice to modernize these traditional apps and manage their incredibly diverse environment with a single solution.
Containerizing traditional applications with Docker EE gives Northern Trust a better way to manage them and some immediate benefits:

Improved security: As a financial institution, security is a top priority. Containerizing traditional applications helps improve their underlying security posture in a few ways:

Security scanning – Northern Trust is leveraging image scanning to discover vulnerabilities within their existing apps. There were some new vulnerabilities that were previously undetected but with the binary level scan, they are automatically alerted to new issues and can address and resolve them immediately.
Smaller attack surface – With Docker, Northern Trust can reduce the attack surface of their application by only allowing the required access, syscalls and processes needed to run the application.
Faster updates – With the ability to rapidly deploy new containers, Northern Trust no longer patches applications  in place, but quickly deploys a new container with the updates and fixes and removes the previous one.

Improved infrastructure efficiency: Instead of managing unique infrastructure stacks for each application, each with its own challenging dependencies, Docker allows Northern Trust to treat all infrastructure as a heterogeneous pool of resources. Dependencies are not packaged into the containers with the app, thus removing it from the infrastructure problem. This makes the application portable so that Northern Trust is free to explore a hybrid cloud strategy.

Impact and Results
With Docker EE in place, Northern Trust is seeing immediate improvements in the way they do software development. It used to take 30 days to provision infrastructure for new projects. With Docker EE, they experience a 4x improvement in deployment time and it now only takes 7 days. Northern Trust is also seeing 2x improvement in infrastructure utilization, getting more out of their available capacity than before.

By simplifying infrastructure management and making applications more portable, Docker EE is improving the quality of their traditional apps. This enables both their developers and operations team to be more responsive and ultimately, Northern Trust is able to stay a leader in their market by delivering the services that their clients are asking for.
To learn more about how Northern Trust is modernizing their traditional applications, watch Rob’s breakout session with Rohit Tatachar, Sr. Program Manager at Microsoft and Brandon Royal, Solutions Architect at DockerCon 2017:

Next Steps

View all the recorded sessions from DockerCon 2017
Learn more about modernizing traditional apps with Docker EE
Sign up for the Modernize Traditional Apps kit

Traditional Apps at @NorthernTrust are more agile and secure with Docker Enterprise Edition…Click To Tweet

The post Docker Enterprise Edition Brings New Life Back to Legacy Apps at Northern Trust appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

User-guided caching in Docker for Mac

Recent Docker releases (17.04 CE Edge onwards) bring significant performance improvements to bind-mounted directories on macOS. (Docker users on the stable channel will see the improvements in the forthcoming 17.06 release.) Commands for bind-mounting directories have new options to selectively enable caching.
Containers that perform large numbers of read operations in mounted directories are the main beneficiaries. Here’s an illustration of the improvements in a few tools and applications in common use among Docker for Mac users: go list is 2.5× faster; symfony is 2.7× faster, and rake is 3.5× faster, as illustrated by the following graphs:
go list (2.5× speedup)

go list ./.. in the moby/moby repository
symfony (2.7× speedup)

curl of the main page of the Symfony demo app
rake (3.5× speedup)

rake -T in @hirowatari’s benchmark
For more details about how and when to enable caching, and what’s going on under the hood, read on.
Basics of bind-mounting
A defining characteristic of containers is isolation: by default, many parts of the execution environment of a container are isolated both from other containers and from the host system. In the filesystem, isolation shows up as layering: the filesystem of a running container consists of a series of incremental layers, topped by a container-specific read/write layer that keeps changes made within the container concealed from the outside world.
Isolation as a default encourages careful thinking about the best way to bypass isolation in order to share data with a container. For data-in-motion, Docker offers a variety of ways to connect containers via the network. For data-at-rest, Docker Volumes offer a flexible mechanism to share data between containers, and with the host.
The simplest and most common way to use volumes is to bind-mount a host directory when starting a container — that is, to make the directory available at a specified point in the container’s filesystem. For example, the following command runs the alpine image, exposing the host directory /Users/yallop/project within the container as /project:
docker run -v /Users/yallop/project:/project:cached
-v /host/another-path:/mount/another-point:consistent
alpine command
In this example, modifications to files under /project in the container appear as modifications to the corresponding files under /Users/yallop/project on the host. Similarly, modifications to files under /Users/yallop/project on the host appear as modifications to files under /project in the container.
There are many use cases for bind mounting. For example, you might

develop software using an editor on your host, running development tools in a container        
run a periodic job in a container, storing the output in a host directory
cache large data assets on the host for processing in a container

Bind mounts on Linux
Newcomers to Docker are sometimes surprised to discover that the performance overhead of containers is often close to negligible and in many cases, is significantly lower than other forms of virtualization.
On Linux, bind-mounting a directory, like many Docker features, simply selectively exposes host resources directly to a container. Consequently, access to bind mounts carries little-to-no overhead compared to filesystem access in a regular process.
Bind mounts on Docker for Mac
The Linux kernel makes container-style isolation efficient, but running containers on Docker editions for non-Linux operating systems such as macOS involves several additional moving parts that carry additional overhead.
Docker containers run on top of a Linux kernel, and so the Docker for Mac container runtime system runs a minimal Linux instance using the HyperKit framework. Containers running on top of the Linux system cannot directly access macOS filesystem or networking resources, and so Docker for Mac includes libraries that expose those resources in a way that the Docker engine can consume.
Access to filesystem resources is provided by a separate non-privileged macOS process (osxfs) that communicates with a daemon (“transfused”) running on the virtualized Linux. A Linux system call such as open or read that accesses bind-mounted files in a container must be

turned into a FUSE message in the Linux VFS
proxied over a virtio socket by transfused
forwarded onto a UNIX domain socket by HyperKit
deserialized, dispatched and executed as a macOS system call by osxfs

The entire process then takes place in reverse to return the result of the macOS system call to the container.
Each step in the process is fairly efficient, making the total round trip time around 100 microseconds. However, some software, written under the usually-correct assumption that system calls are instantaneous, can perform tens of thousands of system calls for each user-facing operation. Even a comparatively low overhead can become irksome when scaled up by four orders of magnitude. Consequently, although syscall latency has been reduced several times since the initial release of Docker for Mac, and although a few opportunities for further reducing latency remain, optimizing latency alone will not completely address bind mount performance for all applications.
File sharing design constraints under Docker for Mac
The design described above arises from a number of constraints, which in turn arise from the high-level design goals of Docker for Mac: it should closely match the Linux execution environment, require minimal configuration, and involve as little privileged system access as possible.
Three constraints in particular underlie the design of Docker for Mac file sharing.
The first constraint is consistency: a running container should always have the same view of a bind-mounted directory as the host system. On Linux consistency comes for free, since bind-mounting directly exposes a directory to a container. On macOS maintaining consistency is not free: changes must be synchronously propagated between container and host.
The second constraint is event propagation: several common workflows rely on containers receiving inotify events when files change on the host, or on the host receiving events when the container makes changes. Again, event propagation is automatic and free on Linux, but Docker for Mac must perform additional work to ensure that events are propagated promptly and reliably.
The third constraint concerns the interface: bind mounting on Docker for Mac should support both the concise -v syntax and the more elaborate interfaces for bind mounting on Linux.
These constraints rule out a number of alternative solutions. Using rsync to copy files into a container provides fast access, but does not support consistency. Mounting directories into containers using NFS works well for some use cases, but does not support event propagation. Reverse-mounting container directories onto the host might provide good performance for some workloads, but would require a very different interface.
User-guided caching
The design constraints above describe useful defaults. In particular, a system that was not consistent by default would behave in ways that were unpredictable and surprising, especially for casual users, for users used to the Linux implementation, and for software invoking docker on the host.
However, not all applications need the guarantees which arise for free from the Linux implementation. In particular, although the Linux implementation guarantees that the container and host have consistent views at all times, temporary inconsistency between container and host is sometimes acceptable. Allowing temporary inconsistency makes it possible to cache filesystem state, avoiding unnecessary communication between the container and macOS, and increasing performance.
Different applications require different levels of consistency. Full consistency is sometimes essential, and remains the default. However, to support cases where temporary inconsistency is an acceptable price to pay for improved performance, Docker 17.04 CE Edge includes new flags for the -v option:

consistent: Full consistency. The container runtime and the host maintain an identical view of the mount at all times.  This is the default, as described above.
cached: The host’s view of the mount is authoritative. There may be delays before updates made on the host are visible within a container.

For example, to enable cached mode for the bind-mounted directory above, you might write
docker run -v /Users/yallop/project:/project:cached alpine command
And caching is enabled on a per-mount basis, so you can mount each directory in a different mode: 
docker run -v /Users/yallop/project:/project:cached
-v /host/another-path:/mount/another-point:consistent
alpine command
The osxfs documentation has more details about the guarantees provided by consistent and cached.  On Linux, where full consistency comes for free, cached behaves identically to consistent.
Feedback
We have seen significant improvements in the performance of several common applications when directories are mounted in the new cached mode.
For the moment, read-heavy workloads will benefit most from caching. Improvements in the performance of write-heavy workloads, including a popular dd-based benchmark, are under development.
Test cases involving real world applications are a big help in guiding Docker for Mac development. So, if you have field reports or other comments about file sharing performance, we’d love to hear from you.
You can get in touch via the issue tracker. The osxfs documentation outlines the details to provide when reporting a performance issue.

Docker for Mac 17.04 adds flags that speed up file sharing 3x or more on common workloads.Click To Tweet

Learn More:

Get started with Docker for Mac
Check out the detailed osxfs documentation
Send us your file sharing use cases  (See What you can do in the osxfs documentation.)

The post User-guided caching in Docker for Mac appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Docker Enterprise Edition Lights a New Spark of Innovation within MetLife

MetLife, the global provider of insurance, annuities, and employee benefit programs, will be celebrating it’s 150th birthday next year. Survival and success in their space depends on being agile and able to respond to changing market requirements. During the Day 2 General Session at DockerCon 2017, MetLife shared how they’re inspiring new innovation in their organization with Docker Enterprise Edition (EE).
Information Management is Core to MetLife
MetLife offers auto, home, dental, life, disability, vision, and health insurance to over 100 million customers across 50 countries. Their business relies on information – about policyholders, risk assessments, financial and market data, etc. Aaron Ades, AVP of Solutions Engineering at MetLife offers that they’ve been in the information management business for 150 years and have accumulated over 400 systems of record – some apps are over 30 years old.
The challenge for MetLife is that they still have a lot of legacy technology that they must work with. Aaron shared that there is still code running today that was first written in 1982, but they still need to deliver a modern experience on top of those legacy systems.
To hear more about how MetLife is staying ahead of their competition using Docker, watch Aaron’s presentation from the Day 2 general session.

Wrapping Legacy Apps with Docker EE
A key realization for MetLife was that wrapping containerized microservices around a legacy app would make them more easy to adapt and improve. As Aaron shared about breaking up the business logic into smaller pieces, “it makes you more nimble…it makes your systems of record much easier to deal with.” For MetLife, that also means the application becomes more portable. Once containerized, MetLife has the flexibility to host the services in their own datacenter or in the cloud.
With Docker EE, MetLife found a secure container platform that could deliver both objectives around containerization and management across a hybrid cloud. Docker provided them a commercially backed end-to-end container management solution. It was easy for the DevOps team to install and manage and it allowed them to go from concept to production in only 5 months.
Results and Benefits
With Docker in place, MetLife has shipped a new modern UI that allows customers and agents to have a holistic view of their relationship with the company. It can be viewed on a phone, laptop or other mobile device, but it taps into data written in different decades in different languages, running on different systems, successfully integrating the old with the new.

Aaron and his team have also seen significant operational improvements including:

The ability to scale quickly by leveraging Microsoft Azure to handle the 25x increase in traffic during annual open enrollment periods
Increased resource utilization with up to 70% consolidation of their VMs
More automation through orchestration allowing them to easily scale up a service or deal with VM/hardware failures

Adopting Docker EE has, more importantly, sparked a new wave of innovation at MetLife. As Aaron closed out his presentation, he recognized the “Mod Squad”, the team that led the Docker project and was credited with “changing the culture of the company” as “antibodies to the status quo”.  He believes Docker has been transformative for his company and has ignited a spark across multiple businesses at MetLife. In the end, he believes this will allow them to be more agile and more nimble which is a core competitive advantage.
Watch Tim Tyler’s presentation below to learn more about how Metlife uses Docker Enterprise Edition.

Next Steps

Watch the entire Day 2 General Session from DockerCon 2017
View all the recorded sessions from DockerCon 2017
Learn more about Docker Enterprise Edition 

The post Docker Enterprise Edition Lights a New Spark of Innovation within MetLife appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

Introducing Docker’s new CEO

Docker has celebrated a number of important milestones lately. March 20th was the fourth anniversary of the launch of the Docker project at PyCon in 2013. April 10th was the fourth anniversary of the day that I joined Solomon and a team of 14 other believers to help build this remarkable company. And, on April 18th, we brought the community, customers, and partners together in Austin for the fourth US-based DockerCon.

March 20th, 2013

Docker Team in 2013
DockerCon was a great opportunity to reflect on the progress we’ve seen in the past four years. Docker the company has grown from 15 to over 330 talented individuals. The number of contributors to Docker has grown from 10 to over 3300. Docker is used by millions of developers and is running on millions of servers. There are now over 900k dockerized apps that have been downloaded over 13 billion times. Docker is being used to cure diseases, keep planes in the air, to keep soldiers safe from landmines, to power the world’s largest financial networks and institutions, to process billions in transactions, to help create new companies, and to help revitalize existing companies. Docker has rapidly scaled revenues, building a sustainable and exciting subscription business in conjunction with tens of thousands of small and mid sized businesses and over 400 G2000 customers like ADP, the Department of Defense, GE, Goldman Sachs,  Merck,  MetLife, and Visa. And, we’ve created enduring partnerships with the likes of Accenture, Alibaba, Avanade, AWS, Booz Allen, Cisco, Google, HPE, IBM, Microsoft, Oracle, and more. We’ve built the foundations for a lasting and sustainable business.
 

I am incredibly humbled and honored to have been a part of this journey. So, it is naturally with some mixed emotions that I share the news that Steve Singh will become Docker’s new CEO (he is currently chairman of the board),  and that I will be moving to a role on the board of directors. While there is always some uncertainty about changing roles, I am 100% certain that Steve is the right person for Docker.
 
He is an incredible individual and leader, with a broad base of experience that includes founding and growing one of the most successful enterprise companies, Concur. Over the course of two decades, Steve took Concur from startup to public company, successfully navigated the shift from software to SaaS, and built a world class team, customer base, and business model, forging an organization of lasting value. More recently, he has demonstrated his considerable expertise as a member of the SAP Executive Board Member, serving as President of SAP Business Networks  and running SAP’s largest cloud businesses. As I worked with Steve– first as Docker’s chairman, and then as we worked together on the transition– I also saw his incredible qualities as a human being, and heard from the many people who have had the pleasure to work with Steve at Concur and SAP. (the average tenure at Concur was over twelve years). Docker has the potential to become not only one of the most enduring technology companies, but also a transformational platform, technology, and movement; I can’t think of a better or more qualified individual to lead us to that future than Steve.
I’d like to end this note with a few personal thoughts.

My first “Silicon Valley” Job, c. 1982  
 I started my “career” in Silicon Valley cutting apricots in an orchard a stone’s throw from what was to become Apple headquarters. Since then, I’ve had the privilege of working for six startups—three as CEO. Two went public (Avid and Verisign), two became part of larger companies (Gluster and Plaxo) and one was unceremoniously shut down by government officials.  (A “business school” in Uzbekistan ). I think Docker has the potential to far exceed all of them.

Of the Six Startups I’ve worked at/led, Docker stands out (and certainly has the best logo!)
But, all of my startup experiences have been remarkable,  and have taught me that my heart lies in startups. I’ve also learned that great companies are bigger than any individual person, and that a person’s life is defined by much more than any one company. Finally, I’ve seen that different leaders with different skills are needed at different stages in a company’s history. Steve is the right leader for Docker now, and I am confident that his leadership will enable Docker to fulfill its incredible potential.
I’d like to end by thanking a number of people. I’d like to thank Solomon for his vision, passion, brilliance, and willingness to share this journey with me. I’d like to thank our board and investors, our many partners, and especially Docker’s customers for their faith in–and support of–a young company and team with outsized dreams. I’d like to thank the incredibly creative and talented people who are using Docker for everything from finding cures for cancer to searching for earth-like planets to developing new sources of clean energy. Your enthusiasm and passion has made the past four years not only fun, but deeply meaningful. I’d like to thank my incredible family, my wife, and  and three amazing sons for your support, love, patience, and encouragement through the long days, nights, and weekends.
Finally , I’d like to thank the incredible team at Docker. I’d like to thank the early employees ( like Sam Alba, Eric Bardin, Victor Vieux, Yannis Peyret, Ken Cochrane, and Jerome Petazzoni–who met me on my first day) and people like Nick Stinemates and Michael Crosby, who were among the first people I helped to bring into the company, and who have all continued to contribute so much to Docker. I’d like to thank entrepreneurs like Aanand, Anil, Ben, Daniel, Diogo, Evan, Jeff Julien, Madhu, Nathan, and Patrick who were willing to join their dreams and companies with ours. I’d like to thank the incredible members of the Docker executive team who I haven’t already mentioned: the irrepressible Roger Egan, the multi-talented Marianna Tessel, the hard-driving Scott Johnston, the passionate customer advocate Iain Gray, the wildly creative and insightful David Messina, and the unflappable Mike Gupta. Thank you for not only joining us at Docker, but for attracting and building such amazing teams of your own. And, thank you all for persevering through the difficult times. Thank you to Faith Kinyua for keeping me sane and organized.  I could probably go on for at least another 300 names. But, to all of you: you are one of the most passionate, skilled, diverse, and amazing groups I’ve ever known. You have done such inspiring and impossible things already, and I will be cheering from the sidelines as you take Docker to even greater heights.

Docker Team Today
The post Introducing Docker’s new CEO appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/