At RackN, we’re huge fans of Docker. We’ve been using the engine for years (since v0.8!) and you can read about our lessions from when we rearchitected around Docker Compose. Now we’ve built “one-click” hybrid cluster automation for Kubernetes, Docker Swarm and others.
However, I’m concerned that Docker installs reveal a lack of cluster operation focus. These platforms are evolving very rapidly exposing users to both breaking upgrades and security risks. This drives a requirement for cluster automation.
What are cluster operations? It is the system level activity of creating an integrated platform that is repeatable, secure, networked and sustainable. As use of Docker transitions from single node activity into multi-node and hybrid clusters, we need to approach the install and configuration as a system activity.
Cluster configuration requires system activity because there are so many moving pieces and necessary pre-configurations of networking, security, storage and roles. These choices need to be implemented before the actual cluster software is installed because they drive how the cluster is configured and managed. They continue to be a major factor as we grow, shrink and ugprade the cluster.
Why don’t people do this already? Because cluster configuration requires additional setup and planning. Operators are struggling just to keep up with API changes between quarterly updates.
Our mission is to eliminate the overhead of cluster operations so you can focus on using the Cluster not building it.
The RackN team has been working on deployment of Docker Swarm (and container orchestration more generally) to make sure Cluster Operations and underlay are robust and automated on every platform from cloud to metal.
The video below (and others in my channel) show how we’ve made it “one click” easy to create container clusters in nearly any environment. While this is an evolving process, we believe that it is critical to start with cluster automation.
Let us show you how we’ve made that both fast and painless.