Illumina Innovates with Rancher and Kubernetes
This article covers some of the major advantages and disadvantages of two of the most popular container orchestration tools: Kubernetes and Docker Swarm. We describe each piece of software and then dive in to compare across different features.
For teams building and deploying containerized applications using Docker, selecting the right orchestration engine can be a challenge. The decision affects not only deployment and management, but how applications are architected as well. DevOps teams need to think about details like how data is persisted, how containerized services communicate with one another, load balancing, service discovery, packaging and more. It turns out that the choice of orchestration engine is critical to all these areas.
Since Docker launched in 2013, it has brought a level of excitement and innovation to software development that’s contagious. It has rallied support from every corner—enterprises to startups, developers to IT folk, plus the open source community, ISVs, the biggest public cloud vendors, and every tool across the software stack. Since the launch of Docker, many major milestones have served to advance the container revolution. Let’s look at some of them.
We’ve just returned from DockerCon 2017, which was a fantastic experience. I thought I’d share some of my thoughts and impressions of the event, including my perspective on some of the key announcements, while they are still fresh in my mind.
New open source projects Container adoption for production environments is very real. The keynotes on both days included some exciting announcements that should further accelerate adoption in the enterprise as well as foster innovation in the open source community.
If you’re going to successfully deploy containers in production, you need more than just container orchestration Kubernetes is a valuable tool Kubernetes is an open-source container orchestrator for deploying and managing containerized applications. Building on 15 years of experience running production workloads at Google, it provides the advantages inherent to containers, while enabling DevOps teams to build container-ready environments which are customized to their needs. The Kubernetes architecture is comprised of loosely coupled components combined with a rich set of APIs, making Kubernetes well-suited for running highly distributed application architectures, including microservices, monolithic web applications and batch applications.
Open source container management company exceeds revenue goals by twenty percent, reports 19 million software downloads. Cupertino, Calif. – January 25, 2017 – Rancher Labs, a provider of container management software, today announced momentum in 2016, doubling its employees, exceeding revenue targets by twenty percent and surpassing 19 million software downloads. This growth underscores the heavy demand for its popular open source software that simplifies the deployment and running of containers in production, on any infrastructure.
As we start a new year, I’d like to thank the Rancher community for a great 2016. 2016 was an awesome year for Rancher Labs, and we’ve been fortunate to have a deeply engaged community of open source users and developers, customers, and partners. In March, [we shipped our 1.0 GA release], and since then Rancher has established itself as a leading product in the container ecosystem. 2016 was especially rewarding because of the tremendous amount of support we received from our users and customers.
2017 Predictions: Rapid Adoption and Innovation to Come Rapid adoption of container orchestration frameworks As more companies use containers in production, adoption of orchestration frameworks like Kubernetes, Mesos, Cattle and Docker Swarm will increase as well. These projects have evolved quickly in terms of stability, community and partner ecosystem, and will act as necessary and enabling technologies for enterprises using containers more widely in production.
Greater innovation in container infrastructure services Free eBook: Comparing Kubernetes, Mesos, and Docker Swarm Though there’s a strong set of container storage and networking solutions on the market today, more products will emerge to support the growth and scale of production container workloads, particularly as specifications like Container Network Interface (used by Kubernetes) continue to mature.
One of the great things about microservices is that they allow engineering to decouple software development from application lifecycle. Every microservice:
can be written in its own language, be it Go, Java, or Python can be contained and isolated form others can be scaled horizontally across additional nodes and instances is owned by a single team, rather than being a shared responsibility among many teams communicates with other microservices through an API a message bus must support a common service level agreement to be consumed by other microservices, and conversely, to consume other microservices These are all very cool features, and most of them help to decouple various software dependencies from each other.
In less than a week, over 24,000 developers, sysadmins, and engineers will arrive in Las Vegas to attend AWS re:Invent (Nov. 28 - Dec 2). If you’re headed to the conference, we look forward to seeing you there! We’ll be onsite previewing enhancements included in our upcoming Rancher v1.2 release:
Support for the latest versions of Kubernetes and Docker: As we’ve previously mentioned, we’re committed to supporting multiple container orchestration frameworks, and we’re eager to show off our latest support for Docker Native Orchestration and Kubernetes.
Note: You can find an updated comparison of Kubernetes vs. Docker Swarm in a recent blog post here.
Recent versions of Rancher have added support for several common orchestration engines in addition to the standard Cattle. The three newly supported engines, Swarm (soon to be Docker Native Orchestration), Kubernetes and Mesos are the most widely used orchestration systems in the Docker community and provide a gradient of usability versus feature sets.
Prometheus is a modern and popular monitoring alerting system, built at SoundCloud and eventually open sourced in 2012 – it handles multi-dimensional time series data really well, and friends at InfinityWorks have already developed a Rancher template to deploy Prometheus at click of a button.
In hybrid cloud environments, it is likely that one might be using multiple orchestration engines such as Kubernetes and Mesos, in which case it is helpful to have the stack or application portable across environments.
View the Rancher 1.1.0 release notes on GitHub After a very exciting DockerCon last week where the bulk of the engineering team was able to see all the latest and greatest innovations surrounding the Docker ecosystem, our team was able to squash the remaining issues for our Rancher 1.1 stable release. If you have been following our dev builds, we have been shipping tech preview features with each release for our open source community members who want to play with the latest Rancher has to offer.
[We just came back from DockerCon 2016, the biggest and most exciting DockerCon yet. Rancher had a large and well-trafficked presence there - our developers even skipped attending breakout sessions in favor of staffing the booth, just to talk with all the people who were interested in Rancher. In only two days, over a thousand people stopped by to talk to us!]
[Docker-Native Orchestration] [Without a doubt, the biggest news out of DockerCon this year is the new built-in container orchestration capabilities in the upcoming Docker 1.
The only container management platform that supports Mesos, Kubernetes and Docker Swarm
GRC SinoGreen, with participation from existing investors, funding will help Rancher Labs maintain momentum, and meet sales and marketing goals
This week we shipped Rancher v0.63. With this latest release, we are dramatically expanding the capabilities of Rancher, by including a complete distribution of Kubernetes as a container orchestration framework, within Rancher. Beginning with this release, when you create an environment, you’ll be able to launch a Kubernetes environment with a single click and you within 5-10 minutes have access to fully deployed Kubernetes cluster. The work we’ve done, however, goes beyond simply launching a Kubernetes cluster on top of the existing Rancher platform.
Docker Compose is a great framework for deploying application stacks, and at Rancher we’ve been working hard to make it possible to leverage that framework to create a catalog of application blueprints that can be repeatably configured and deployed. In this recording of our January online meetup, we demonstrated the new Catalog feature in Rancher and how to create catalog items. In the meetup we demonstrated: - Using the Rancher catalog to configure, deploy and upgrade an application - Creating a private app catalog linked to a git repo - Best practices for building catalog templates - Inserting application configuration into templates We demonstrated all of this live, and answered dozens of questions about Docker, Rancher, and building application templates.
*This post is now a bit out of date. Since posting this article we’ve added full support for Mesos environments directly into Rancher. You can read more about it at rancher.com/mesos. * Hi, I’m Sidhartha Mani, one of the engineers here at Rancher Labs. Over the last few months I’ve been working with Apache Mesos, an open source resource manager and scheduler, which can be used to deploy workloads on infrastructure.
Today we announced the beta availability of Rancher, our open source Docker infrastructure and management software. It is an exciting day for our team, and a great opportunity to say thank you to all the people who have worked on the open source Rancher project, blogged and tweeted about using Rancher, and helped other new users on our support groups. For the last seven months, Rancher has been an alpha project, and throughout that time we’ve had a wonderful group of early users and testers trying out the product, suggesting enhancements, documenting bugs, and contributing code.
Hello, my name is Alena Prokharchyk and I am a part of the software development team at Rancher Labs. In this article I’m going to give an overview of a new feature I’ve been working on, which was released this week with Rancher 0.16 - a Docker Load Balancing service. One of the most frequently requested Rancher features, load balancers are used to distribute traffic between docker containers. Now Rancher users can configure, update and scale up an integrated load balancing service to meet their application needs, using either Rancher’s UI or API.
Nagios is a fantastic monitoring tool, and I wanted to see if I could get the agent to run as a system container on RancherOS, in order to monitor the host and any Docker containers running on it. It turned out to be incredibly easy. In this blog post, I’ll walk through how to launch the Nagios agent as system container in RancherOS. Specifically, I’ll use two vagrant boxes to cover:
*This post is now a bit out of date. Since posting this article we’ve released the Rancher container management platform, and added full support for Mesos environments. You can read more about it at rancher.com/mesos. * In this tutorial, I will explain how to deploy a Mesos cluster in containers running on RancherOS and then make our deployment portable across different cloud platforms and virtualization systems. If you’re not familiar with Apache Mesos, it is an open-source project that provides an elastic and highly available clustering framework.
Thanks to Docker, Orange and Blumberg Capital for hosting a great meetup last night in San Francisco. Darren Shepherd, Chief Architect of Rancher Labs introduced RancherOS for the first time, and answered questions from the audience. Learn more about
RancherOS, or download it from GitHub. If
you’d like to learn more, Darren will be presenting RancherOS at an online meetup on March 31st, 2015.
RancherOS Demo at Docker Meetup from Rancher Labs on Vimeo.
Hi Everyone, I’m Will Chan, the new VP of engineering here at Rancher, and I wanted to post an update about some of the things we’re working on here at Rancher for release later this quarter. I started at Rancher in early December, and since then I’ve been thrilled to see how many people have downloaded Rancher and are using it to manage and implement networking around Docker. I’m really excited about some of the features we’re working on, and wanted to give you a sneak peek of what’s coming over the next two months.