Docker container technology the world of application development has taken by storm by simplifying and accelerating the development, implementation and maintenance of server-side applications ,
What started as a way of resources single host computer started (or VM), has become the technology now for managing container workloads across a cluster of hosts / VMs. [1945005gereiftzupartitionierenundzuverwalten]
Among the most popular manager container clusters are Kubernetes (originally by Google), Apache Mesos and Docker Swarm (from the creators of Docker). Each cluster management technology has something unique and different to offer.
- Apache Mesos is mature and can not containerized workloads (such as Hadoop) are executed.
- Kubernetes opinionated tends to be. It offers little customization (for now) and the cross-linking can be a challenge. But it moves fast and the settings can be a quick way to get started.
- Docker Swarm is Docker, Inc and offers the usual Docker (single host) API. It is the easiest to start with, but also the least mature (at time of writing).
As a developer / architect infrastructure, it can be hard to decide on the right technology for your needs. The only way is to evaluate, they actually implement in your infrastructure and test it with your workloads. This is not easy for several reasons:
- During the Cluster Manager manage the container workloads, someone else has to manage the group of VMs - using the Cluster Manager, scale the cluster and to monitor the cluster ,
- Cluster Manager also rely on a supporting host infrastructure that must be managed: Mesos requires Apache Zookeeper, requires Kubernetes DCE
- your infrastructure is probably a mix of clouds and data center. each cluster manager has a different set script for different clouds and hypervisors.
- You do not containerized with the Cluster Manager as Citrix NetScaler load balancer to manage in concert infrastructure / orchestrate.
Citrix Lifecycle Management (CLM) is an Application Lifecycle Manager that you, scope and maintain can use this Cluster Manager help :. either in your data center or in the cloud CLM has plans that you get up and running with these cluster manager very quickly:
The image below shows all three cluster Manager on the same pool of XenServer hosts in use. It is worth noting that Citrix XenServer itself clustering technology to the group used a similar set of hypervisors!
You can see that I have the XenServer Docker Supplemental Support Pack installed to get a view of the container in the various clusters
The next figure shows below a Kubernetes cluster and a mesos cluster running on AWS executed -. started from CLM, configured and monitored - the same blueprint used starting with the cluster on XenServer.
in all cases all it takes is the published plans in Citrix Lifecycle Manager to use and give some inputs. You can start it before lunch and again to have a productive day manager hacking on cluster. CLM accepts the undifferentiated heavy lifting of this Cluster Manager to set up so that you can focus on your workload!
For those developers who are not able to create VMs or cloud instances, CLM provides the ability deploy these clusters Pre -created VMs / hosts BareMetal
Tips .:
- you noticed a virtual appliance NetScaler have the list of virtual machines running (VPX) on XenServer. This instance was also of CLM in use. After implementation, the VPX instance be used to your containerized load balancing workloads.
- The Plan steps include several goodies that can be reused in other contexts. For example, there are installed a step that Apache Zookeeper. Another step will help you Docker engine reliably in a VM.
I hope that this note will help to begin install you in your clustered container history. Let me know in the comments if you have any ideas / questions / feedback. Happy Clustering / container-ing!
0 Komentar