One of the most common situations in software development lifecycle is the maintenance and the development of new features. Docker users can handle this by creating an image for their software product and a tag for each release, so you can quickly deploy a container with any tagged version of your product.
In Tutum, we have recently introduced a new feature to approach this use case: Redeploy. With this new tool, you will be able to change the image tag that your running Tutum application is using and point it to the new tag (new version). This is all accomplished without managing the destruction of the old Tutum application holding the old image, and having to create the new one. Furthermore, new containers will have the same configuration as the one being replaced. This includes having the same endpoints, custom environment variables, and custom ports so you have access to your application or your containers, with no configuration required!
Let’s see a quick example.
Imagine that we have containerized our web page in the repository bernardo/tutum-web and we are running it in Tutum. Since we only have one version of our web page, we deployed the tag v1, which matches the first version of bernardo/tutum-web.
Now we want to update our web page, so we build our new image and push it with another tag called v2 into the same docker repository (bernardo/tutum-web) to hold these changes. This way, we can manage the two versions of our web page: v1 and v2. We want to update our running Tutum app with the new image version v2, so … Redeploy!!!
By clicking the Redeploy button, we’ll be taken to a pop-up menu. Clicking on the drop-down menu allows you to choose which tag to redeploy, in this case v2.
After a few seconds your Tutum application will be updated with the new image, automatically destroying the old containers and creating new ones with the same configuration and endpoints.
Try it out and let us know how it works for you!