Nick Ma January 17, 2017
Note: this is Part 4 in a series on building highly resilient workloads. Parts 1, 2, and 3 are available already online.
In Part 4 of this series on running resilient workloads with Docker and Rancher, we take a look at service updates. Generally, service updates are where the risk of downtime is the highest. It doesn’t hurt to have a grasp of how deployments work in Rancher and the options available within.
For this post, instead of focusing on how to setup a continuous deployment/integration pipeline, we’ll instead focus on experimenting and learning with upgrades using rancher-compose files, and reference the great chain of articles by the awesome bloggers. We will skim over the Rancher CI/CD ebook for now, and sprinkle in enough theory to get us start using Rancher upgrades comfortably. Read more
Mike Mackrory January 10, 2017
If you’re anything like me, you’ve been watching the increasing growth of container-based solutions with considerable interest, and you’ve probably been experimenting with a couple of ideas. At some point in the future, perhaps you’d like to take those experiments and actually put them out there for people to use. Why wait? It’s a new year, and there is no time like the present to take some action on that goal.
Experimenting is great, and you learn a great deal, but often in the midst of trying out new things, hacking different technologies together and making it all work, things get introduced into our code which probably shouldn’t be put into a production environment. Sometimes, having a checklist to follow when we’re excited and nervous about deploying new applications out into the wild can help ensure that we don’t do things we shouldn’t. Consider this article as the start of a checklist to ready your Docker applications for prime time. Read more
Will Chan January 4, 2017
Earlier this week, we released Rancher 1.3. It includes several new features: user interface fixes, changes to our DNS engines, and improvements when using Kubernetes and associated tooling. However, Rancher 1.3 also begins addressing a frequent request we receive from users: Windows 2016 support.
Windows support in Rancher 1.3 is purely experimental and limited in scope (you can read more in our docs), but it’s an important step towards serving the needs of our customers as containers become more widely adopted in enterprises. A huge portion of the world’s workloads run on Windows server and client systems, and will continue to do so for the foreseeable future; our goal at Rancher Labs is to make applications truly portable across clouds and infrastructure, and enabling workloads with Windows containers is a key part of that vision. Read more
Sheng Liang January 1, 2017
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. So many of you have posted insightful articles, blog posts, forum questions and answers, and GitHub issues, and seeing how users talk about us on Twitter and other social media platforms drives us to work harder. We are continually inspired by the great stories people have about how they use Rancher, like those by like those by Dispatch, LateRooms.com, and Alertacall. We are grateful to users who are willing to share their experiences using Rancher with the world, and to our friends at Align Technology who are so enthusiastic about our product that they organized the first Rancher user group in the US.
In 2016, our product development was guided by a few key ideas, and our community of users will continue to see us expand upon these in 2017: Read more
Shannon Williams December 27, 2016
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. Read more