ECMWF is starting to provide some of its web and data services based on applications deployed on a new IT platform. For the migration of ECMWF’s data centre to Bologna, we are transforming several applications to run as Docker containers on Kubernetes‑managed platforms. This article explains what Docker/Kubernetes are, why they are increasingly being used at ECMWF, and what this means to users.
Reasons for the change
Developing IT‑based applications historically means having to know a lot about the technical environment. Software code can be developed and run perfectly in a limited environment (like a laptop, desktop or workstation) but it can then be hard to transition, maintain and run in other environments. The traditional approach is to develop services and applications based on common shared code/libraries which are deployed onto dedicated infrastructure to ensure that the applications get the IT environment and resources they need to run. This approach is not sustainable as services grow and does not scale in terms of infrastructure or effort. Looking for alternatives, ECMWF web application analysts became aware of two new technologies: Docker and Kubernetes.
What are Docker and Kubernetes?
Docker is a generic environment for running software without having to know details about the infrastructure. Docker uses operating system virtualisation to enable development and delivery of software applications consistently in runnable packages called containers. Kubernetes is a tool for managing Docker applications that are running on clusters of infrastructure. Kubernetes solves the problem of scaling and operating services composed of containers. General market adoption of Docker and Kubernetes, for application development, has been substantial, supporting accelerated development, rapid release of updates to production and efficient scaling. They are key technologies for development. ECMWF has aligned itself with these technologies, realising that they are beneficial for our services.
What does it mean for users?
ECMWF is currently using Docker and/or Kubernetes successfully to provide several services, including Atlassian, EFAS-IS, GloFAS, the RMDCN website, FTP, the Data Services Costing Application, Accounts and Nexus. There are other services in the pipeline for deployment on Kubernetes in Bologna, including the www.ecmwf.int website, ecCharts, and webapi.
The key improvements users of these services should see as ECMWF adopts Docker and Kubernetes are:
- improved turnaround time for fixes/updates/improvements
- more robust services as applications are even more comprehensively tested during their development.
As illustrated in the diagram, the use of Docker/Kubernetes also improves our workflows as development can be undertaken in relative independence. In addition, the transition of applications to production is facilitated as application containers do not need to be changed for operations.
The current setup
Our current Kubernetes Cluster consists of virtual machines (VMs) from our VMWARE VSPHERE and Network Attached Storage for data persistence. The infrastructure can be scaled transparently by adding new VMs and/or bigger VMs using Kubernetes to orchestrate containers across VMs. In production, the cluster also provides many operations-ready functions by default and using it significantly reduces the effort needed to implement commodity application components, such as web servers, application servers or databases.
It is important to realise that Docker and Kubernetes are not the only technologies used. To efficiently and robustly deploy applications, we have implemented Continuous Integration/Continuous Deployment (CI/CD) tooling. We use Atlassian Bitbucket, Harbor, Nexus and Atlassian BAMBOO. With these tools, we have a pipeline system that enables rapid and robust development, with a light touch, through to operations. We have also integrated automated functionality to test and ensure the quality of code and the security of underlying platforms.
If you are interested in learning more, please feel free to get in touch with Andrew Brady (firstname.lastname@example.org).