Containers have shaken the IT world providing a totally new concept of a virtualization solution for cloud PaaS and IaaS due to their lightweight virtualization, increased density, elasticity, and rapid provisioning.
Using containers within public, private or hybrid clouds give users a new degree of freedom in placing their workloads and changing their location at any time during load peaks, maintenance windows or data center availability problems. Containers are much smaller in size than virtual machines (VMs), so moving them from one cloud to another is far easier. This makes applications more mobile in a cloud setup and easily managed saving the time and efforts of the DevOps teams.
In this three-part blog series we’ll explore the main benefits of the Docker® template implementation within Jelastic platform. We will describe how Jelastic have used containers since 2011 and why we believe that our solution provides advanced containers orchestration, probably one of the best on the market at the moment.
The container system in the Jelastic Cloud goes hand in hand with the microservice architecture pattern. Each environment within a large, complex and enterprise-ready application represents a service that can be scaled, configured and monitored separately. And if any change is required in the project, it can be easily made in the specific service without any need to rebuild and redeploy the entire application (as it is demanded in the monolithic apps). With such structure, the application can even be managed by different teams, when each is responsible only for a certain part.
One of the recent technologies underlying microservices are Docker® templates, a technology for packaging applications and deploying them in containers. The fact that they became a perfect match inspired us to implement these templates within Jelastic.
Basically, Docker® technology addresses application assembly, delivery and portability, while Jelastic provides orchestration and management for hosting applications. And in order to meet the requirements of enterprise production-ready applications, Jelastic delivers such packaged templates support on top of highly secure and stable Virtuozzo containers.
Currently Docker® uses LXC and libcontainer for creating containers by default. These containers work based on namespaces and cgroups. The same kernel isolation mechanisms are used by containers into Jelastic. That’s why we can ensure that all required processes of the packaging standard are covered in a proper “native” way.
With Jelastic implementation, users will now have more flexibility and options while installing any stack, application or system using public Hub Registry or their own private registry based on Quay Enterprise Registry. When a new template is requested for installation, it is placed to a special Shared Cache Storage (to make it easily and quickly available for further installations) and after that, already distributed as independent and isolated Virtuozzo containers among hardware nodes. As a result, each template is provisioned in secure containers virtualization and can be easily managed using full SSH root access or via Jelastic dashboard.
In addition, Jelastic technology provides improvements and extra functionality in the areas of density, management tools, recovery, etc. Let’s cover some benefits of the containerized applications hosted within Jelastic Cloud.
In the first part of our blog series we are providing the detailed information about two important benefits: high availability and live migration.
Jelastic provides high availability for microservices on two levels:
- application topology
- containers virtualization
Load balancing within an application ensures high availability through the distribution of workload across multiple components. Using multiple components with load balancing, instead of a single component, may increase reliability through redundancy. Jelastic uses two types of load balancing: TCP and HTTP.
In addition, Jelastic provides an ability to use multi-cast session replication between instances of web-servers. When session replication is enabled in a cluster environment, the entire session data is copied on a replicated instance. Session replication provides high reliability, scalability, and perfect failover capabilities.
Jelastic Cloud lets you easily set up two different types of database replication – master-slave and master-master – in order to solve a number of different problems with performance, to support database backups, to alleviate system failures and much more.
Also integrated software defined storage is specifically designed for high availability of containers virtualization in the cluster. The distributed storage with built-in replication and disaster recovery ensures a fast and automatic recovery in case of a hardware node fail. In other words, if any hardware node fails all the containers will be automatically recovered on the other existing hardware nodes.
Live Migration and Offline Migration
It is one of the key features that is very important for an enterprise-ready cloud platform. Cloud service providers can easily migrate containers with applications from one physical server to the other with zero downtime and that is a key requirement to maintain overall performance and quality. This increases operational efficiency during the maintenance of the hardware, provides better load balancing and data center utilization and allows moving customers to more powerful nodes, without service interruption.
Jelastic’s unique automatic vertical scaling uses live migration to ensure that applications can scale within a server without downtime. As an application scales within a server, other applications can be automatically migrated to another server to make room. Live migration allows Jelastic to deliver all the needed resources for applications without restarting containers and causing application downtime.
In addition, during maintenance or other planned downtime of hardware the live migration feature can perform automated evacuation of containers from one hardware node to another. This makes Jelastic platform the right choice for hosting even stateful applications. During live migration, applications keep working without downtime and get the required resources.
Also the ability to migrate containers provide the devops teams with additional different and in many cases more efficient flow of application lifecycle. In the original version to go through all the steps of delivery lifecycle all pipeline delivery stages should be connected to the Hub Registry. Every time you should recreate containers and sometimes the whole multi-container environment. In other words you repack and rebuild your containers every time during migration Dev => Test, Test => Stage, Stage => Prod. In Jelastic with live or offline migration of containers, you can easily migrate the application from one lifecycle stage to the other with no need to rebuild your containers and redeploy the application, and without the need to connect each stage to the Hub Registry anymore after initial template provisioning.
These application lifecycle workflows require more deeper analysis and clarification and we are going to write a separate blog post about the different issues related to this topic.
High availability and live migration are just the first two benefits that you get while using a containerized application on top of Jelastic’s platform. In our next publication you’ll find out more about isolation and security, smart distribution of containers among physical servers, high density and maximum utilization of server resources and hibernation and memory de-duplication technology that you gain within our system.
Have you already tried Docker® containers on top of Jelastic? Please provide your feedback in the comments below.