Weave is Live at Tutum
We are very pleased to be able to report another public production case at scale! Congratulations and thanks are due to our friends at Tutum who announced a major upgrade to their Docker cloud service yesterday. The Tutum team have...
How to Configure your Repos for Multi-Tenancy and GitOps: Zscaler’s Use Case
Automating Weave deployment on Docker hosts with Weave Discovery
Using Weave and Scope with Convox
We are very pleased to be able to report another public production case at scale! Congratulations and thanks are due to our friends at Tutum who announced a major upgrade to their Docker cloud service yesterday.
The Tutum team have used Weave to deliver a set of killer features for Docker users on the Tutum cloud. And best of all, these are already available to the thousands of happy Tutum users.
Keep reading to learn about some of the most important features, including service discovery and dynamic links, round robin services, automatic redeployment, and more!
Service Discovery and Dynamic Links
Tutum has always supported internal service discovery and static Docker links, but until now these have not worked seamlessly together. This meant that certain changes required a stack to be redeployed. Now, by using the Weave software network to generate persistent IPs (i.e. reusable & global), Tutum can now transparently access remotely linked services via Weave and Tutum’s internal DNS. This enables much more ‘seamless’ application scale on Tutum.
Round Robin Services
The same service discovery and linking mechanism means that multiple services can share a name (or key). This enables round robin request scheduling across your services, even as you scale to more and more nodes.
From the Tutum blog post – “With dynamic links, if you redeploy a service, scale it, or deploy a new linked service, hostnames will automatically be added/updated on all running containers, removing the need to redeploy any of them.”
All Your Application Nodes are Connected – Anywhere
All nodes deployed using Tutum are now connected to one another .. regardless of the geographical location, IaaS provider, or type of node (bring-your-own-node works too!). … This private network is encrypted and .. only nodes belonging to a specific account can connect and communicate with each other.
From Laptop to Cloud
And best of all, this is 100% compatible with Docker links, so if your stack runs in your laptop, it will seamlessly run at scale in Tutum without any modifications.