Kumolus has deployed a new release to its Cloud Management Platform.
Build and Manage (Environments) Improvements
Build:
Toggle icon or list mode / Added ability to add Descriptions
Note: Toggle button highlighted in red box
Edit AMI on Template Designer
We’ve implemented the ability to change the existing AMI on the Template Designer page. This allows you to keep you existing relationships with other objects (like security groups) but modify the AMI in use.
Click on your AMI on the template and use the Change link under the AMI, you will then be able to Select other available SoE options from the drop down.
Template Designer- Provision – Automatically start environment when provisioning
Previously, when provisioning environments would go to a pending state, we’ve added an option on the Provisioning screen to allow it to be started automatically. We’ve made then selected by default.
Environment
Show related Schedules & Backup policies from the environment
From the individual environment page you are now able to view / modify the related scheduled environments.
General
Backup Policy – Add create AMI from Instance
Naming Conventions: Added support for RDS and EBS snapshots and Private AMI’s
In addition to the existing Naming Convention / Tagging variables, we’ve added the following variables for Volumes, EBS and RDS Snapshots.
When completed as part of an automated policy, they will be prefixed with “a_”.
Variables Supported:
Volumes:
— %hostname%
EBS Snapshots:
— %hostname%
— %volumename%
RDS Snapshots:
— %dbname%
Both
— %currentdate%
Settings: Tagging: Kumolus AWS limit increased to from 8 to 48 per object
Inline with AWS changes, we’ve increased the number of tags available per object.
Platform: Improvements to Subnet Group
Build: Specify existing Subnet Group from Template
Platform: Improvements to Security Group
Show environment count on VPC listing page for SG
Ability to Delete SG from VPC listing if that SG is not present in any environment
Settings: SoE: Userdata, add support for %servername% variable
Ability to use the %servername% variable in “Userdata”. On provision of an instance we will send the hostname as part of the userdata sprint.
