Released: Calm v1.7.0

The next big release of Calm is here - and boy, are we proud of it!

Calm v1.7.0 brings you a host of new features that are sure to take you a giant leap closer to achieving DevOps nirvana. We've bundled in new integrations, an enhanced UI, improved service management, upgrades, autoscaling, resiliency and a host of other features that make DevOps and IT automation a breeze.

We've also squashed a handful of bugs to make using Calm more efficient and effortless for you.

New Terminology

We've made a couple of changes in terminology with Calm v1.7.0.

Resources will now be known as Services.

Applications will now be known as Deployments.

New Policies

We've introduced a new set of Policies in Calm that lets you upgrade your deployments, triggers event-based autoscaling and triggers resilience on services in your deployment that have malfunctioned. Here they are in detail:

Resiliency Policy for Services

Calm now includes a Resiliency policy for your services that brings up services that have gone down abruptly. You can configure your own monitoring system to trigger resiliency or use Calm's own API-based monitoring.

Autoscale Policy for Array Services

We've introduced an Autoscale policy for arrays that lets you run an autoscale up or an autoscale down on your array, whenever required. You can configure your own monitoring system to trigger autoscale on your arrays on detecting high or low loads. You can also configure a pre-autoscale and a post-autoscale flow as part of this policy to run tasks before and after an autoscale event occurs.

Introducing, Rolling and Canary Upgrades

Calm now includes a new Deployment policy that lets you upgrade the services in your deployment on the fly. You can opt to run either a Rolling upgrade or a Canary upgrade on your services.

Upgrade button for services with an active deployment policy

The Services tab on your deployment details page now includes an Upgrade button for upgrading arrays. This button is available only when a Deployment policy is configured for an array and when there are no critical flows running on the application.

What's New?

A brand new Blueprint Editor

We've overhauled the Blueprint Editor to make it more fun and easy to use than it already is. You will no longer see buttons as they have been replaced with attractive and self-explanatory icons across the UI. We've also changed the visibility of Flows and Services into separate layers thereby letting you pick and view the layers that you'd like to see. The Blueprint Editor also includes a Blueprint summary screen that gives you an Overview of your blueprint, its Topology, associated Flows, Policies and Credentials.

First-time setup wizard

Calm now comes with a first-time setup wizard that lets you setup up your Calm account, upload your license key and configure Calm to work with your existing virtualisation, build and deployment tools.

Re-run support for flows

You can now re-run flows that have failed on existing deployments directly from the Deployments dashboard. You can also use this feature to re-run flows after you've made changes to tasks or other flows in your deployment. Re-running create, delete and VM start/stop/restart flows are currently not supported in this version. Support for re-running these flows will be included in our next release.

New User Roles in Calm

We've made changes to the user roles in Calm. The user roles that you can create are:

Admin: An Admin has complete admin, execute, read and write permissions over every action and item in Calm.

Author: An Author has read, write and execute permissions over blueprints and applications in Calm.

Consumer: A Consumer account normally has read and execute access that is limited to the team that the user is a part of and the inventory, blueprints and applications that the user has been assigned to use.

Operator: An Operator account only has read permissions over blueprints and read and execute permissions over applications that are part of the inventory assigned to the team that the operator belongs to.

You can know more about these user roles by visiting docs.calm.io/using_calm/#people.

Debug information for failed tasks

The deployment page now includes debug information for failed tasks.

Array IPs are now accessible

You can now access the IPs for every individual service in an array by expanding the array view and clicking on each individual service. You can also access these individual IPs using properties and variables while configuring tasks and flows for your deployment using the macros in the format @@{property_name [x]}@@ where property_name denotes the property that you've drawn a dependency to and x denotes the Calm Array Index of the service in the array.

Improved Service Management

Calm now comes with an enhanced Services tab that lets you view the managed and unmanaged services from your virtualization providers. We've also built in an option that lets you start, stop and restart services that are listed in this view.

A new Global Policy page

Calm now comes with a new page on the menu for Global Policies. You can use this feature to set Global Policies to govern over every action in Calm. You can set Approval, Notification and Expiry policies for a variety of action including VM actions, autoscaling, flow runs, upgrades and rollbacks. For more information on Global Policies and how to use it, visit docs.calm.io/using_calm/#global-policies.

Auto-generate blueprint flows

All start, stop, restart and delete actions on your services on a blueprint are automatically generated based on service-level dependencies.

A new grid-view on the Services page

The Services page now comes with a grid view with services displayed in the form of tiles. Clicking on a service tile opens a panel on the right of the page that has more information about the service and buttons for service actions.

Share Blueprints with Users and Teams

We have also introduced a Blueprint Share feature that lets you share your blueprints on Calm with other users and teams and invite them to edit blueprints.

Docker Hub Integration

Calm now supports integrations with Docker Hub. You can now configure Calm to work with images from Docker Hub.

Import images from Docker Hub as a blueprint

We have included the ability to import images from Docker Hub as a Calm blueprint.

Update and upgrade your license from the UI

We've included a new License section on the Calm UI that gives you a snapshot of your Calm usage, based on the number of nodes that are a part of your license. You can also sign up for an Enterprise license or add a new license key, in case the one you're using has expired.

What's Changed?

• We have fixed issues that cropped up while importing existing services into a Calm blueprint. This feature now supports the selection of multiple services, selection of services from the list view and the retention of the original service name after it is imported into a blueprint.

• We fixed an issue where approval emails would contain noreply@calm.io as the Sender Email Address even though your own email providers were integrated with Calm.

• We have fixed an issue where Eval task properties ignore content after '=', whenever '=' is used in the property value.

• We have changed the labelling of Critical flows on the UI to avoid confusion.

• We have simplified the Calm installer. Installing and configuring Calm now requires a minimal set of steps, helping you get started with Calm, that much faster.

• We've enhanced the grid view of items to contain more information pertaining to the item within the item tile.

• Calm now does not allow the deletion of provider settings that are already in use in a deployment or a blueprint.

• We've reduced the size of the Calm installer to one-third of the size of its predecessor.

• We've added tooltips on tabs and buttons on the blueprint editor to help improve your experience in using Calm.

• We fixed an issue that occurred while adding new users where a team that was selected by mistake and removed, would lead to all other team names not appearing on the list of teams that are present in Calm.

• We fixed an issue where text pertaining to service details would overlap in the service view.

• We have increased the timeout values so that slower machines don't end up facing connection errors.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk