Cloud Computing Made Easy®

Release Notes

From kaavo wiki
Jump to: navigation, search

Sign-up for IMOD free trial

Visit Kaavo Website for more information


Release 5.2.0 (August 20, 2014)

  • Added support for gp2 volume types.
  • In hpcloud introduce workaround for volume attachment api issue.
  • In hpcloud made region available to actions.
  • In hpcloud introduce workaround for volume attachment api issue.

Release 5.1.0 (May 12, 2014)

  • Allow passing of parameters as part of scale up.
  • Added support for creating server tags.
  • Automatically syncing actions from svn.
  • Added support for hp cloud new architecture.

Release 4.9.0 (Feb 7, 2014)

Release 4.8.0 (October 7, 2013)

  • Showing more information in the application centric log: Added the columns Server Name and Server IP to the existing application centric log.


  • Ability to export logs: See the figure above
  • Added support for new EC2 instance types: You can now launch m3.xlarge and m3.2xlarge instances.
  • Added support for executing actions in pseudo terminal: With this feature you can execute sudo command on images that require a tty for it. This can be done using

a new flag on actions called use-pty. See examples here

  • Added support cleaning up old scripts before action execution: When creating script/configuration for an action if a file with the same name exists,

it is deleted before creating it.

  • Added UI support for VPC security groups: We can now select VPC security group for a servers from server configuration dialog.
  • Added Wizard support for empty server types: Sometimes we have to create server types without any initial servers to which we add servers later. For example,

we may need to have servers running in one zone(zone1 say) and need to start replacement servers in a different zone(zone2) only when the servers in the first zone fails. For such a use case, we create one server type for each zone with the zone2 server type having zero start-up count. Now, we can create such server types form wizard.

Release 4.7.0 (June 5, 2013)

  • Ability to Add Running Servers to Systems: Sometimes users may want to import their existing servers which weren't launched by Kaavo within Kaavo IMOD for better management. Web services API is extended to let us add existing servers to systems, refer addServer.
  • Enhancement for Patch Management and Executing Adhoc Commands/Workflows on Multiple Servers in Parallel: Added API to execute an action on a given set of IPs refer executeAction. As of this release, this feature is available for EC2 and OpenStack only. See example here

Release 4.6.0 (March 27, 2013)

  • Added support for Openstack v2.0 API: It is Tested for HP Cloud and Rackspace Open Cloud. To setup HP Cloud using Openstack API. Specify the details as shown in figure below. In the host field specify the host name for the identity service followed by /v2.0. Use compute for the compute service name and 15 for public IP prefix. Refer to OpenStack private cloud setup for details.


After setting up the provider create an account as shown below. For Account ID use the account user name and for the Access Key field use the account password. These user id and password are the same as used in logging on to the console.


For setting up Rackspace Open Cloud use specify the details as below. Leave public ip prefix blank.


Release 4.5.0 (February 12, 2013)

  • Added support for pagination of large systems: If a system contains large number of servers, IMOD UI automatically paginates the tiers in the system and shows six servers per page for each tier. Previous and next button appear on the tier rectangle to allow users to go to next or previous page. This feature will allow users to view systems having very large number of servers.


  • Introduced new flags for controlling Amazon ELB behaviour: Introduced new flags update and removeExternalInstances to override the default behavior of removing existing servers from ELB. The update flag prevents IMOD from updating properties of an existing ELB. removeExternalInstances flag is useful when an existing ELB with some servers already attached is used in an N-Tier system. Specifying removeExternalInstances="false" ensures that N-Tier keeps existing servers attached to the ELB when attaching new servers to it.
   <awsloadbalancer name="TestBalancer" update="false" removeExternalInstances="false">
  • Creating name tags for EC2 servers: When IMOD launches a server in EC2, it automatically creates a name tag using the IMOD name for the server.
  • For Amazon VPC launch servers in a particular security group: This feature removes the limitation of launching vpc instances in default security group. Specify the vpc security group using its id e.g. sg-34a4f623.

Release 4.4.0 (December 7, 2012)

  • Enhanced support for Multi-Cloud Templates: Users can now provide alternate definitions for servers to easily port applications across various clouds and regions in the same system definition file. This feature combined with the Common Server Attribute Names feature enables users to efficiently capture information for deploying and managing applications on all supported clouds in one place. Refer to n-tier guide section on Server Types for more details. For additional info watch this webinar Porting Applications Across Cloud Providers and Regions.
  • Configurable Email Notification for Scheduled Events: Added ability to get email notification anytime a scheduled event is executed. This notification can be configured while setting up scheduled events on the Manage page for the system. Users can select the individual scheduled events they want to receive notification for.
  • Logging of Triggers Creation and Deletion: Audit logs for creating and deleting triggers for events are now recorded in the corresponding system logs.
  • Configurable Sign-up Page for Private Clouds Deployment: As an improvement to our support for white-labeling onsite or private deployment of Kaavo IMOD, we now allow admins to customize the text for the sign up page. This customization can be done by super admins from the configuration section.

Release 4.3.0 (October 15, 2012)

  • White-Label Solution for Onsite Deployment: Kaavo now also provides white label solution for cloud management. Customers using onsite version of Kaavo IMOD can now private-label their deployment from the configuration section after logging in as super admin. Watch short demo at
  • Scheduling of Reports: From the Accounting section users can schedule to received weekly and monthly cost accounting reports via emails.
  • Reporting Enhancement: We now allow cost tracking for departments. Costs reports are generated with the department information. This allows users to better track the total cost of ownership for individual applications and departments. We now also allow exporting of cost accounting data in CSV format. For details see Tracking Costs for Individual Departments or Business Units in the N-Tier System Definition Guide.
  • Support for AWS LoadBalancers in VPC: Users can now launch and manage AWS LoadBalancer within VPC. To use LoadBalancers within VPC users just have to add the xml element with the subnet information to the LoadBalancer definition in the System Definition file. The subnets tag should be added between lbnodes and listnerconfigs xml tags. A LoadBalancer can support servers in multiple subnets, just add a comma separated list of the subnets. E.g. <subnets>subnet-dd97fcb6,subnet-aa97fcb6</subnets> . For details refer to the N-Tier Guide section on LoadBalancer within AWS VPC
  • AWS VPC configuration for Onsite Deployment: If the onsite or private Kaavo IMOD deployment is part of a network connected to AWS VPC, to communicate with the servers in the VPC IMOD should use the private IPs within the VPC instead of the public IPs. This can be configured by selecting a check box under the configuration section for the super admin. Without this configuration IMOD will launch servers within AWS VPC but wouldn't be able to connect to the servers for configuring them.

Release 4.2.0 (August 20, 2012)

  • Deployment Cost Reporting: One of the use cases we have been hearing from customers is ability to track total infrastructure cost of applications running on cloud. To support this use case, in addition to metering the Cloud usage, we allow users to track total cost for each of their deployments in US dollars. For the cloud providers who provide pricing information via API we use that information for calculating the cost. This feature is also useful for software companies looking to distribute their software on various cloud providers and are looking for metering and billing functionality to charge customers for their software in addition to the infrastructure charges by cloud providers. For details checkout the Tracking Costs for Individual Departments or Business Units section of the N-Tier Guide.
  • Eucalyptus UI Enhancement: We now have new UI for configuring the servers for Eucalyptus Cloud. Among other things, UI now supports mapping of Elastic IP, storage volume, and creating a new volume from the specified snapshot and attaching it to the server automatically after the launch. UI also support security groups and configuring of firewall rules. See the screenshot below for more details.
Eucalyptus Cloud New UI
Eucalyptus Cloud New UI

Release 4.1.0 (July 10, 2012)

  • Free trial download for onsite deployment of IMOD: Usually organizations use SaaS version of Kaavo IMOD hosted at, however, some companies prefer to install IMOD on premise for various reasons. Kaavo IMOD trial version for onsite deployment is available at:
  • Validation of Velocity Template format: IMOD Actions use Velocity engine for dynamically generating configuration files and scripts. Starting this release IMOD performs Velocity template syntax validation every time an Action is edited or System Definition is updated. Velocity templates are used for dynamically generating configuration files or scripts for automatically deploying and managing applications and workloads on public, private, and hybrid clouds.
  • Email Notification in case of Event Timeout: Starting this release we will be sending email notification to the users in case any of their event times-out during processing.
  • Engine Improvements: We made some internal engine improvements, especially around distributed event processing and transactions.
  • Better Error Reporting in case of Action Failure: Action execution can fail for various reasons, e.g. wrong path, bad credentials, or connectivity issue. Starting this release we provide more detailed error messages to the users to help them resolve issues.
  • Zabbix Installation System Definition: Zabbix is a popular open source enterprise monitoring solution. In this release we have published the System Definition for automating the deployment of Zabbix in our catalog. Please refer to Zabbix System Definition documentation for details.

Release 4.0.0 (June 7, 2012)

In this release we fixed some minor bugs and made some usability related changes. Following are two notable changes in this release:

  • Separation of Servers and Workflows States: IMOD tracks two different types of states, state of the servers running in the cloud and the state of the workflows executed by IMOD. In past we were showing the consolidated view of the two states for showing the status of the deployment. So for example is the server was running but the start-up workflow on the server was not completed the state of the server was shown as pending. Starting this release we show the workflow state for the server on the bar on top of the server icon and server state below the server icon, see the figure 1. below. The state for the server level workflows is now shown similar to how we have been showing the state for the tier level workflows. Doing mouse-over on the workflow state provides additional information about the workflow.
Figure 1: State of Workflows
Figure 1: State of Workflows
  • Provider Specific Server States: In past to maintain consistency across providers we were translating the provider server states to common IMOD states. E.g. a properly running server state on IBM cloud is defined as Active whereas on Amazon cloud it is defined as running; we were showing the IBM active state as running. This was causing some confusion among users as state information displayed in IMOD was different than the state of the server shown in the provider console. Starting this release we show the same state for the server as defined by the cloud provider without any translation to common state.

Release 3.9.0 (April 24, 2012)

  • Ability to share, reuse, and import actions: This allows users to quickly and easily create complex deployments by reusing best practices scripts from the script library as a part of their deployments. Users can publish and search scripts and configuration files as reusable actions to the library. Click on the Import Action link when configuring actions to import a reusable action.
  • Support for Chef: Kaavo IMOD now provides support for running chef solo or chef hosted recipes as actions. Conceptually chef recipes are similar to dynamic scripting supported by Kaavo as a part of actions for configuring and automating the low level configuration and management tasks. So similar to Actions which are subset of Kaavo System Definition, Chef recipes are integrated as actions in the System Definition. The Kaavo System Definition captures both the low level and high level deployment and run-time orchestration and workflow information needed for deploying and managing applications and workloads across public, private, and hybrid clouds. To learn more please check out the examples for using Chef Solo and Chef hosted with Kaavo IMOD. Actions for using Chef are also included as reusable actions that can imported in any system.
  • Support for HP Cloud Services: Check out HP Cloud Services Support for details
  • UI Enhancement for configuring OpenStack servers: Added ability to map Elastic IP addresses to OpenStack Server and to configure groups for server firewalls.

Release 3.8.0 (February 24, 2012)

  • Design and Manage Page: In this release we have split the functionality of the "N-tier" page into two new pages "Design" and "Manage". On the Design page users can select solutions from catalog, or create their own custom deployment. Manage page is for run-time management of deployments. All run-time management activities for the system including monitoring is available on the management page. Since monitoring information is now available on the Manage page we have removed the monitoring page.
  • Historic Monitoring Data: In addition to real-time monitoring data, users can now see the history data for their deployments. This information is available from the monitoring tab for the System on the Manage page.
  • Support for OpenStack EC2 API: Previously we were supporting OpenStack native API, in this release we have also added support for OpenStack EC2 API. When registering their private cloud, users can select the type of OpenStack API supported by their OpenStack Cloud Provider (Native or EC2 style).
  • Rackspace and AWS Load Balancer Support: Ability to add and manage Rackspace and AWS Load Balancers. This enables users to bring up the entire deployment including load balancer from AWS or Rackspace with a single click. New tags for load balancers are supported as part of Kaavo System Definition. In this release ability to configure load balancer using UI is only available for AWS Load Balancer, for the Rackspace Load Balancer users have to manually edit the System Definition from the Manage page for their deployments. For information on these Rackspace and Amazon Load Balancers are defined in the Kaavo System Definition, please checkout the Rackspace LB and Amazon LB section of the n-tier guide.
  • Support for vCloud Director 1.5 API: Added support or vCloud Director version 1.5 API. This support is currently in beta.
  • Support for AWS Virtual Private Cloud: Added support to launch and manage servers in the AWS VPC. Currently we don't provide UI support for this so to launch and manage servers in VPC you have to update the corresponding System Definition from the definition tab of the System on the Manage page. You have to add the VPC related XML tags and info to your AWS server definition in the Kaavo System Definition for your deployment. For information on adding the tags please see the AWS VPC section of the n-tier guide. If you want to use VPC please contact us as you have to establish connectivity for IMOD to communicate with your servers in the VPC; currently this is a one time manual setup, we are planning on automating this setup in the future.

Release 3.7.0 (December 9, 2011)

  • OpenStack Support: Added beta support for OpenStack. For details on how to configure your OpenStack private cloud for management checkout the setup documentation
  • Enhanced Reporting: Added support for adhoc reporting, users can download the generated reports from IMOD or can have IMOD email the reports to them.
  • Improved State Update for Servers: Some cloud providers were returning cached results for the state of the servers, resulting in delayed state update in the IMOD UI. Implemented mechanism to bypass the cached results to get the latest state for the servers.
  • IE Memory Leak Fix: We found and fixed some memory leaks for the IE browser. As a result of these leaks application response used to become slow over the period of time for the IE users. The leaks occurred only in IE because of JQuery package we were using in the UI.
  • System Definition for CloudFoundry: Added sample system definition for automatically deploying the CloudFoundry PaaS. For additional details please review the documentation for VMware CloudFoundry template

Release 3.6.0 (October 18, 2011)

  • Logicworks Integration: GA support for Logicworks' Public Cloud (infiniCloud), checkout Logicworks Cloud Setup for details
  • Ability to Update Scheduled Events: In addition to adding and deleting scheduled events, users now have the ability to update scheduled events.
  • Ability to use AWS Flexible Payment Service for Subscription: In addition to Paypal, customers can also use AWS Flexible Payment Service for paying Kaavo IMOD subscription fees.
  • Support for AWS EC2 cg1.4xlarge Instance: Added support for AWS EC2 Cluster GPU Quadruple Extra Large Instance (cg1.4xlarge).
  • Automatic Port Configuration for Eucalyptus: Starting this release anytime a server is launched in Eucalyptus cloud using Kaavo IMOD, the IMOD engine will automatically give access to IMOD to ports 22, 10050, and 10051 for configuring and monitoring. Previously users had to do this manually using the euca-authorize command. Note IMOD engine communicates with the servers over port 22 using SSH. If IMOD engine fails to connect to port 22 of the server, the server will appear in pending state.

Release 3.5.0 (August 23, 2011)

  • This is mainly a maintenance release and includes some bug fixes and back-end improvements.
  • Individual Edition: We introduced a new entry level individual edition of IMOD for individual users who want to use IMOD for personal use or very small deployments.
  • AWS Micro Instance Support: Added support for AWS Micro Instance.

Release 3.4.0 (July 5, 2011)

  • Support for subscription upgrade/downgrade: IMOD supports four subscription plans. Users who have already subscribed to any one of them may upgrade their plan or downgrade them by picking a plan higher or lower respectively than the current plan. As of the current release, when a plan is changed a notification is sent to the support team and they perform the actual plan change so the plan change is not immediate.
  • IBM template for WebSpehere and DB2: This is a two-tier template that automates configuration of IBM WebSphere and DB2. Out of the two tiers, the app tier contains WebSphere and the db tier contains DB2. A sample application is run inside the application server. For details check out IBM WebSphere and DB2 template
  • GA release for 2.2 API: In the previous release 2.2 support was in beta. The beta label was taken off in this release. Users have to put right version and endpoint url while registering a provider. Old systems running on 2.1 may need to be reconfigured on the N-Tier page to make it work. Security group support is still in beta.

Release 3.3.0 (May 31, 2011)

  • New Pricing Scheme: We have introduced a new subscription based pricing scheme, customers can subscribe to appropriate editions of IMOD based on their needs. Existing customers can continue to use their existing subscription or switch to the new pricing model. For additional details on the new pricing model please checkout the pricing page or contact us for additional information. Users can manage their subscription following the "Manage Subscription" link on the Profile page.
  • PayPal Integration: We have integrated IMOD with PayPal to give customers another option to pay for IMOD monthly or annual subscriptions
  • Improved UI for Server Configuration: For improved user experience we replaced the pop-up server configuration for the server with in-line configuration similar to EC2 servers.
  • Support for 2.2 API(in Beta): Integrated with Cloudstack ( 2.2 api and added support for security groups and public IP mapping. At present we are supporting version 2.1 and 2.2 of the API. At the time of configuring private cloud in IMOD users can select the version of the API. In future we will deprecate the support for version 2.1 of the API.

Release 3.2.0 (April 26, 2011)

  • Cloud.Com Support: Added support for version 2.1 of API, refer to Private Cloud Setup for setup information. All the functions like monitoring, scheduling, accounting, etc. are available for integration. After bringing up the server we use port forwarding for connecting to the server on the private cloud network, we do this using one-to-one mapping between public ip and the cloud server. This means that each server in your system will need a public ip. Before starting the system you need to edit the system definition file and enter public ip for the server, e.g. replace the <ip/> with <ip>yourip</ip> and update the system. We have also provided a single server Jira System Definition for integration as an example of how to automate application deployment. To use the template, select Deploy From Template option on the n-tier page and search for cloud, then give name to the system and click deploy. Configure the system before clicking on start. After bringing up the jira system example go to ipaddress:8080 to see the application welcome page, refer to JIRA Single Server for for details. Note: If you deploy IMOD within your own network, you wouldn't need public ip addresses, as IMOD can communicate with the servers via private IP. In the release next month we are planning to release support for version 2.2 of API.
  • Improved UI for Setting Triggers: Users can now configure thresholds for triggers from the trigger tab for the system without going to the monitoring page. In addition we also simplified the UI for setting triggers.

Release 3.1.0 (March 22, 2011)

  • Ability to add running Server to a running System: Users can now add a running server to a running System without restarting the system. We added this functionality as users sometimes want to add their existing running servers to a system managed by IMOD. Note you can't add the same server to multiple systems. Currently we are only allowing to add servers to an existing serverType and role in the running System. Hint: Remember you can always add actions and events to launch additional servers or execute various automation tasks on a running system using the UI wizard. We allow you to add new actions and events to a running system.
  • Trigger Tab for the System: We now have a tab to view configured triggers for the system. Each system has its own tab, allowing users to quickly check the triggers for events in the system.
  • IMOD Virtual Appliance for the IBM Cloud: Released virtual appliance to allow users to tryout launching and running their own instance of IMOD. Note this is a single server appliance and is provided for trial use only. Please contact us if you want to host your own instance of IMOD in production for public, private, or hybrid cloud management. Note this appliance will be available on the IBM Cloud in all regions on March 29, 2011.
  • System Definition Template for Hadoop: Released System Definition Template for automatically configuring Hadoop and processing big data in the cloud on-demand. The sample template is for EC2, however, it can be easily modified by changing the serverType to have the same functionality on other supported clouds. Checkout Apache Hadoop Deployment for details. If you have questions or issues on how to modify the template to run on other supported clouds please contact us or post your question on our message board.
  • Support for AWS Tokyo Region: Added full support for the newly announced AWS Tokyo region.

Release 3.0.0 (February 16, 2011)

  • IBM Private Cloud Support: In addition to existing support for IBM Public Cloud in all locations, users can now register private IBM Cloud in IMOD and seamlessly manage applications across the IBM public and private clouds. We fully support the IBM Cloud REST API for the IBM Cloud, and users can register any private Cloud that is compliant to the IBM Cloud REST API.
  • Detailed Logging for Permissions Framework: Added detailed log messages for the security framework and connectivity issues to give better visibility to users in case an operation is denied or if there is any connectivity issue.
  • Enhanced Notification: To give better visibility around event triggers for a system users now will get email notification anytime a system is launched with details on all the triggers for all the defined events in the system. In addition users will also get notification anytime a system event is triggered.
  • Ability to View Trigger Values: Added ability for users to view the values of the thresholds and details for the configured event triggers for their systems.
  • Easier Eucalyptus Private Cloud Deployment: Released EMI image for IMOD to make it easy for Eucalyptus private Cloud users to deploy IMOD on the private Cloud for managing applications on private or hybrid Cloud environments. Note this image is available for trial only to customers implementing large private Clouds using Eucalyptus.

Release 2.9.0 (January 17, 2011)

  • Fine-Grained Permissions Framework: Released application centric authorization framework. Administrators can create custom groups to control user access to any deployed system, operation on the system, or the configured cloud provider accounts. For example if multiple systems are deployed, admin can restrict any user from viewing or performing operations like start, stop, or editing any of the systems. In addition if there are multiple cloud provider accounts, IMOD admin can restrict users from using any of the configured cloud provider account. To learn more about this new functionality register for this short webinar. Note, for backward compatibility all permissions are allowed by default.
  • Deprecated Observer Role: For delegate users we were supporting two roles, "observer" and "user", as result of new permissions framework we are deprecating the observer role. Going forward all delegate users will be assigned the "user" role by default and administrators can assign custom permissions group to users for fine-grained permissions management. E.g. to give a user an observer access to a system create a group and deny all permissions for the system except for the "view" permission.
  • UI Improvement: AWS servers have several configuration parameters, to improve user experience we replaced the pop-up server configuration for the AWS server with in-line configuration. Please clear your browser cache before using the new version for best experience.

Release 2.8.0 (December 1, 2010)

  • Enchanced N-tier support for EC2: In this release we have removed the Dashboard page. The Dashboard page was causing confusion as it was a legacy from our beta release in 2008 and the users had to leave the n-tier page and go to the Dashboard page for some of the EC2 related functions. All the Dashboard functionality is now available from the n-tier page. Please checkout the enhanced UI and give us feedback.
  • SSH Connectivity Enhancement for Physical Servers: For physical servers users sometimes use ports other than the default port 22 for the SSH connectivity. Users can now specify the custom port for SSH connectivity on physical servers by adding the following optional tag in the System Definition for the physical servers:
  • Streamlined New System Deployments: To simplify the deployment from template and deployment from the UI Wizard, after clicking on the deploy button, users are taken to the Runtime tab of the system for completing the configuration before starting the system. Note deploy button creates an instance of the system that can be customized before actually requesting the resources from the cloud provider. Clicking on the start button after completing the configuration actually get the resources from the cloud provider/s and configures them to run the application or workload per specifications in the system definition file.
  • 64-bit MySQL Cluster Deployment on EC2: Added System Definition Template for deploying 64 bit MySQL cluster on EC2, please refer to MySQL Cluster documentation for more details.
  • Liferay Deployment on Rackspace and EC2: Added System Definition for deploying community edition of Liferay portal version 6 on Amazon EC2 and Rackspace. For more information see the documentation for Liferay System Definition.
  • Simplified Pricing: We support multiple cloud providers and each provider has different server sizes and types, making it difficult for customers to understand the Kaavo usage pricing based on CPU hours. Going forward we will use server hours managed for pricing. This change only apply to the Kaavo pricing for managing the cloud resources, you still need to pay the applicable charges to the cloud provider for the use of cloud resources. For more details on pricing please visit the pricing page.
  • Easier Access To The IBM Cloud: In addition to the IBM specific URL for IMOD, IBM Cloud configuration and management is also available along with other cloud providers from the standard IMOD URL.

Note: We have made some major UI changes in this release, for best experience please clear your browser cache before using the new version. In future releases will try to handle the browser cache automatically, however, it is best to clear the cache as different browser may treat headers and Etags differently.

Release 2.7.0 (October 29, 2010)

  • Easier Interface for Deploying Single Server Systems: We have streamlined the Define New System UI Wizard, now only the users deploying multi-server systems have to answer questions like number of tiers in the system
  • 3-tier Tomcat System Definition Template: Released best practice System Definition Template for a single click deployment of a 3-tier Tomcat system on EC2 and Rackspace Cloud. The system uses Apache in Web tier, Tomcat cluster in the App tier, and MySQL cluster in Database tier. For more information checkout 3-Tier Tomcat
  • HA MySQL Cluster: Released best practice High Availability MySQL Cluster System Definition Template for a single click deployment on EC2. MySQL Cluster is a multi-master database with a parallel architecture. MySQL Cluster allows high volumes of both read AND write operations to be executed concurrently. Note there are separate System Definitions for 64 bit and 32 bit machines. For more information checkout MySQL Cluster
  • Documentation Update: Updated documentation for Quick Start Guide and N-Tier System Definition Guide
  • Windows Password for EC2 from the N-Tier page: Users can now get MS Windows admin password from the server drop down menu on the RUN TIME tab of the deployed System on the n-tier page. There is no need to go the Dashboard page.

Important upcoming change in the next release (version 2.8) In the next release we will remove the Dashboard page. The Dashboard page is a legacy from our very first beta release (April 2008) and supports only Amazon EC2. In January 2009 we released the n-tier dashboard page for providing uniform interface to all the integrated cloud providers. We will continue to enhance the n-tier dashboard page to make it easier for users to deploy and manage applications and workloads in the cloud

Release 2.6.0 (October 1, 2010)

  • Ability to Publish and Share Best Practice Deployments: Starting this release users can now easily publish and share System Definitions for deploying and managing simple single server or complex multi-server, multi-tier applications and workloads. This will allow developers, ISVs, and Managed Hosting partners to deliver one click deployment and run-time autopilot capabilities to their customers. Any user can publish system definition and share it with any or all users of Kaavo IMOD. The description of the System Definition is limited to 200 characters, however, publishers can include a URL to external websites for additional documentation. Any deployed system can be published. For versioning the templates we recommend using naming convention e.g. appending the name with -v1 for version v1, or -v2 and so on, this way you can have multiple versions available to users and if you don't want old versions to be available, you can delete any System Definition template owned by you.
  • Ability to Manually Override the Autopilot: During run-time IMOD engine automatically execute specified actions/workflows in response to defined events. In some circumstances actions/workflows may timeout or get stuck during execution due to external factors e.g. intermittent network connectivity issue. For complex deployments not all actions can be idempotent, therefore we now allow users to manually override the state of the system to running after addressing rare situations of timeouts/exceptions during the execution of run-time actions. In addition we also allow users to clear events from their system queue. Note each system has its own event queue and whenever a system is shutdown or aborted all the events in the queue for the system are cleared. Two new buttons "Reset" and "Clear Queue" are added. Reset button is for manually resetting the state of the system to running in case for any reason event execution is not completed or is timed-out, Clear Queue button is for clearing all the events on the event queue for the system. Note if multiple events are fired for a system they are placed on the event queue for the system and are sequentially executed.
  • Service Monitoring: In addition to monitoring virtual server metrics like CPU, Memory, I/O, Bandwidth, Diskspace, etc. users can now monitor services. In this release we have added support for monitoring Apache HTTP service and MySQL database service. To enable the service monitoring you need to specify the services in the newly added <monitor></monitor> tag in the serverType for the server role on which service is running. Please refer to the service monitoring section of the n-tier guide for details. Also refer to the monitoring agents page for the list of OSs we have tested for service monitoring.
  • System Definition for Cassandra: As an example we released System Definition for deploying and managing NoSQL Apache Cassandra database on EC2. The same System Definition can be easily edited to deploy Cassandra on other supported clouds. Please refer the Cassandra System Definition template documentation for additional details.
  • System Definition for Enterprise Java Application: Released example System Definition for deploying and managing Enterprise Java application in a 3-tier system with JBoss cluster, MySQL cluster, and Apache load-balancer. Please refer to 3-tier Jboss System Definition template documentation for additional details.

Release 2.5.0 (August 31, 2010)

  • Web Service API Enhancements: Added following additional APIs to the IMOD Web Services interface, for details please review the Kaavo Web Services Documentation
    • getSystems(userId, password)
    • getNTierDetail(systemName, userId, password)
    • getTierDetail(systemName, tierName, userId, password)
    • getServerTypeDetail(systemName, tierName, serverRole, userId, password)
    • getEvents(systemName, userId, password)
  • Enhanced Event Processing: Multiple concurrent events on a system are now processed sequentially in order and the IMOD engine executes the corresponding actions. Duplicate events are ignored
  • Speed Up Shutdown process: During Shutdown tier level workflows don't wait for servers to be terminated, they continue after the server shutdown request has been sent to the provider
  • Dynamically Defined Event Triggers are now Persisted: Previously only the event triggers defined prior to starting a system were persisted and any event trigger defined while the system was running (dynamic event) was not persisted. To simplify the usage, we removed the distinction of dynamic events and now event triggers defined on a group of servers when the system is running are persisted as well as automatically configured. As these events are persisted, they are automatically configured every time the system is restarted too.
  • Improved Disaster Recovery: Improved disaster recovery for the SaaS version of IMOD. Our current SaaS version of IMOD is running in the cloud. In the case of an extremely unlikely event of all datacenters of the cloud provider becoming unavailable, we now have the ability to bring IMOD SaaS version online at an alternate cloud provider in less than 2 hours
  • Key Authentication for Terremark: Added support for public key authentication for servers on the Terremark cloud
  • Deployment Error Handling: Added ability to customize responses to error conditions during deployment and server configuration by adding onError attribute in the server startup workflow tag <startup timeout="300" onError="Continue"/>
    • onError="Continue" means if error occurs the rest of the system will continue ignoring the error

If we do not specify any onError attribute, it will act according to the current default behavior, i.e. the tier and the system deployment will be in error state and users have to manually abort the system and retry the deployment after addressing the issue responsible for the error. See the following example of how to configure this within the serverType tag:

serverType role="loadbalancer" min="1" max="8">
             <startup timeout="1200"  onError="Continue"></startup>

Release 2.4.0 (August 2, 2010)

  • Terremark Cloud Support: Released support for Terremark vCloud Express, enabling users to deploy and manage applications on the Terremark Cloud. We have not tested the Windows OS on Terremark cloud yet; for jump start please refer to the Sample Terremark System Definition provided with this release. Refer to Terremark Account Setup for getting started.
  • UI Wizard Support for Physical Servers: Users can now perform hybrid deployments including the physical servers using the Multi-cloud deployment UI wizard. This eliminated the need to manually edit the system definition for adding Physical Servers to deployments.
  • Support for EC2 Cluster Compute:: Added support for Amazon EC2 Cluster Compute instance. Cluster Compute Instance has Quadruple Extra Large 23 GB memory, 33.5 EC2 Compute Units, 1690 GB of local instance storage, 64-bit platform, 10 Gigabit Ethernet. Amazon currently support the cluster compute instance for AMI ami-7ea24a17. When configuring the server pick the instance type cc1.4xlarge. You also need to pick EBS as the root device. Following is the snippet of the System Definition XML for the Cluster Compute Instance.
  • UI Validation Improvement: Added friendly error messages for validating the syntax when editing the Events and Actions from the UI.
  • Gluster Deployment System Definition: Released sample system definition for deploying and configuring and running multi-server Gluster on EC2.
  • Fine-grain Action Execution: Added, ability to Execute Actions on Individual Servers, i.e. if there are more than 1 server in a group of servers (server roles) users can now specify the actions to be executed on a specific server in the group. This is currently supported in the System Definition XML, in the next release we will add support for this fine grain control in the Action UI. The syntax for executing actions on specific server is [tier=app][serverrole=jira][index=2] e.g. if there are 5 jira servers in the app tier, specifying index=2 will execute the action on the second app server. In previous release the action was executed on all the servers in the group. Users can still execute actions on all servers in the group by not adding the index, e.g. [tier=app][serverrole=jira] will execute actions on all 5 jira servers in the app tier.

Release 2.3.0 (July 2, 2010)

  • Physical Server Support: Released support for physical servers, allowing users to manage complex hybrid deployments for workloads using physical servers, private cloud, and public cloud resources simultaneously. For details refer to the Physical Server Section of the n-tier guide. Note in this release UI wizard for configuring physical servers is not supported, so you have to directly add/edit the System Definition XML for physical servers.
  • UI for Custom Events: Users can now define custom workflows to be executed in response to pre-defined events using the UI wizard. Making the UI easy to use is very important to us, so please keep on providing the feedback so we can continue to improve it. We appreciate your feedback and hope you like the new improvements.
  • Encryption of System Definition: Before this release we were only storing the user sensitive information in encrypted format in the cloud. Starting this release we have started to store the entire System Definition in encrypted format as complex system definition files could have sensitive deployment information.

Release 2.2.0 (May 31, 2010)

  • Kaavo Web Services: Released Web Services to allow developers to programatically interact with Kaavo IMOD to manage and deliver on-demand custom apps, SaaS, and PaaS offerings to their customers. Register for the free one hour webinar to learn how to use Kaavo Web Services. For additional information on using Kaavo Web Services please checkout Kaavo Web Services Documentation
  • Event UI: Added additional Event tab for deployed systems to allow adding and configuring events using graphical interface. Currently the graphical interface support lifecycle events like pre-shutdown, post-startup, etc. Graphical interface in this release doesn't support custom events, for now please use the online XML editor for the custom events. Currently we support few provider specific commands in pre-shutdown and post-startup tags for Amazon EC2; we are planing on deprecating this support and replacing these commands with common actions. Graphical interface doesn't recognize provider specific commands, please use the XML document for editing them and it is better to write reusable actions instead of these commands. We are continuously improving the user interface to make it easy to create and edit the System Definition so please keep on providing the feedback.
  • Forums: Added Forums site for related discussions and issues please sign up at and start using it
  • Post Execution Delete: Simplified the ability to delete generated file on the server side after executing an action by setting delete-on-exit flag on the action. This is helpful in case there is sensitive information like username or password in the file which shouldn't be left on the server. See the example below.
<action name="start-apache" execute="true" delete-on-exit="true" target="[tier=web_tier][serverrole=default]">
       <scriptTemplate type="inline">
               /etc/init.d/httpd start
  • Common Server Attribute Names: To allow reuse of actions we have implemented common names for server attributes which are supported by all integrated cloud providers but in some cases have slightly different names, e.g. imageID vs. emiImage. If you want to reuse your Actions using dynamic server attributes across providers we recommend using the common name for the attributes. Check out the Common Server Attribute Names section in the n-tier guide for the listing of common names for the server attribute.

Release 2.1.0 (April 29, 2010)

  • Actions UI: Added ability to edit actions for deployed systems from the Actions tab. This makes it easy for users to find the relevant actions and edit them or add or delete the actions to a system without having to look at the entire system definition. We are working on simplifying the editing and creation of system definitions and in future release we will be provide similar support for editing events and commands
  • Users can now reconfigure servers in a deployed system using UI interface instead of editing the XML
  • Ability to add additional servers of same type in a running system using the server drop down menu in the n-tier UI
  • Custom Images for Rackspace: Added support to query and launch custom images on Rackspace from the UI. During the configuration of servers in a system, users can select images from the drop down menu for launching the server
  • Added support for elastic IP for Eucalyptus
  • An un-configured deployed system now shows all the servers in each server type, previously we were only showing one server for each server type for a system during un-configured state. As reminder serverType is a way to group and configure a set of servers the same way, so configuring any server in the group of servers applies the configuration to all other servers in the group, e.g. group of load balancers running on same cloud provider. If you want to configure servers independently, define them as different serverTypes
  • Pre-Shutdown Workflow: Added support for pre-shutdown workflow in the server lifecycle for handling things like backing up files, flushing I/O, etc. Here is the format of pre-shutdown tag:
<serverType role="ndbd" min="1" max="2">
             <startup timeout="10000">
             <shutdown timeout="1000"> 
                 <command type="action" name="backup-phpcollab-database"/>
  • Support for EC2 Asia: Added support for deploying and managing apps on EC2 Asia Region (Singapore)

Release 2.0.1 (March 31, 2010)

This is a maintenance release with some performance improvements:

  • Improved deployment time for applications by provisioning the servers in parallel for all tiers. Now all the servers in the multi-tier systems are provisioned before the execution of the workflows for configuring servers and tiers. This reduces the overall deployment time for multi-tier applications by 40% to 50%

Release 2.0.0 (March 16, 2010)

  • Implemented fast format to improve peformance for disk formatting for encryption of the persisted data
  • IBM Cloud Support: IMOD edition for IBM is available at to switch back to the regular edition of IMOD go to Watch the 5 minute overview video for details. The video is also available on the Kaavo YouTube channel. Some of the key capabilities for the IBM Cloud support in IMOD are:
    • One Click Deployment: With a single click, IMOD automatically brings online one or multi-server systems, configures middleware, deploys applications and workload and initiates all dependent services in a specified order. This allows users to setup and tear down test and development environments within minutes.
    • Scheduling and Automation: IMOD executes complex workloads at a designated time without manual intervention.
    • Best Practice Deployment Templates: IMOD simplifies the creation and sharing of complex configurations and n-tier deployments using a single system definition file. This provides a consistent environment for development and testing.
  • Provided instructions for installing monitoring agents on custom Window images
  • Private Cloud Support: Enchanced support for Eucalyptus and released documentation for configuring the private cloud. Note use the N-TIER page for Eucalyptus, the DASHBOARD page is for Amazon EC2 only, it is legacy dashboard and will be deprecated in future. Some of the key capabilities for the Eucalyptus support are:
    • One click deployment
    • Monitoring, alerts, and auto-pilot
    • Scheduler
    • Hybrid deployments across public and private clouds
  • Improved the performance for updating the state machine for large scale deployments
  • Documented supported OS for auto-installation of monitoring agents. Non supported OSs may require manual installation of agents or custom installation scripts to enable monitoring. Please contact Kaavo support if you face any issues.
  • Schedule volume backup for EC2 now use volume-id as a unique identifier, allowing multiple users sharing the EC2 volumes to view and manage scheduled backups

Release 1.9.0 (January 29, 2010)

  • AWS EC2 West Region Support: Added support for AWS EC2 West Region
  • Color Coded XML Editor: Added online color coded editor to simplify the editing of system definition files by advance users
  • AWS EC2 EBS Boot Instance Support: Added support for EC2 instances using EBS for booting. EBS boot instances, can be included in the n-tier system by adding optional information to the awsServer tag. Setting terminateOnStopInstance false ensures that the server is stopped and not terminated
<serverType role="default" min="1" max="2" >
    • Note if you specify an EBS instance in the system definition and start the system, by default instance is launched the first time (i.e. new instance id and IP is assigned). On subsequent starting of the system EBS boot instances in the system are started with the same instance id that was assigned during the first time launching of the system. If you want to terminate or bundle the EBS boot instance you have to use the DashBoard. Unlike stopping, terminating the instance results in the releasing of the IP and instance ID for the instance. Current support of EBS boot instances doesn’t support scale up or auto-recovery
  • Monitoring support for custom images (images not provided by Kaavo): Added automatic installation of monitoring agents on servers with Linux OS. This will allow users to use custom Linux images without being limited to the use of Kaavo provided images. Please refer to monitoring agent installation agent installation page to get a list of supported Linux versions. By default, any time a Linux OS based server is launched from IMOD N-Tier, IMOD N-Tier Engine checks if the monitoring agent is installed on the server, if the agent is not installed IMOD N-Tier Engine installs the agent. If users don’t want the monitoring agent to be installed on the server, they can disable the default behavior by adding the optional flag agentSetup="manual” for the serverType
<serverType role="default" min="1" max="4" agentSetup="manual">
    • Note it is not possible to set flags on individual servers. serverType(a group of servers of the same role) is the lowest granularity to specify flags
  • Updated Rackspace sample System Definition: Updated the Kaavo provided sample Rackspace system definition by removing the action for installing the monitoring agent. As IMOD now support automatic installation of monitoring agents on all flavors of Linux for all integrated cloud providers, install monitoring action for installing and configuring the monitoring agent is no longer required in the system definition file
  • Enhanced support for debugging custom actions: IMOD now logs exit code for the actions executed on the servers over SSH in the application centric system logs accessible from the LOG tab for the deployed systems. This gives users more visibility to the configuration and run-time management tasks. Also for debugging users can add the verbose flag to display up to last 10 lines of the message generated from the actions executed on the servers in the application centric logs. Detailed messages are logged on the servers in the same directory where the actions were executed in the log files for the corresponding actions (<action-name>.log)
<serverType role="default" min="1" max="4" logMode="verbose"> 
  • Ability to connect to servers as a non-root user: Some images don’t allow users to connect as root user over SSH. The non-root username can be configured for IMOD engine to connect to the server by setting the sshUser attribute in the server tag.
<serverType role="default" min="1" max="2" >
  • Ability to manage servers without SSH connectivity: Sometime users only want to launch the servers and don’t want to connect to the server over SSH or have firewall rules to not allow IMOD to connect to certain servers over SSH. Users can now bring up multi-server systems using IMOD without IMOD engine waiting for SSH connectivity by just adding the optional checkSSH=”false” flag to the startup timeout in the server tag
<serverType role="default" min="1" max="2">
    <startup timeout="300" checkSSH="false">
  • List of server attributes available to the velocity engine: Published the list of server attributes that can be used within the velocity templates for dynamically generating scripts, code, or configuration files in any programming language. Please refer to the n-tier guide List of Server Attributes Available to Velocity Templates section for details.

Release 1.8.0 (December 10, 2009)

  • System Definition Schema: On popular request we have released the XML schema for the IMOD System Definition File. Please note as we add new providers and functionality we will continue to enhance the XML schema, we will maintain the latest production schema at For additional information on System Definition also refer to the N-tier System Definition Guide
  • UI Wizard: Added UI Wizard to make it is easy to define and configure a system from scratch, view the video tutorial for more information
  • Import/Export Deployments:Added Ability to export and import System Definitions to and from the local drive
  • Monitoring Enhancements:
    • Added ability to view monitoring data for free swap memory and used swap memory
    • Added ability to view monitoring data for last 15 minutes, 30 minutes, and 1 hour
  • Deployment Timeout Handling:Added ability to handle timeout conditions during deployment and server configuration by adding onTimeout attribute in the server startup workflow tag <startup timeout="300" onTimeout="Continue"/>
    • onTimeout="Abort" means the server will be shutdown and the rest of the system will continue
    • onTimeout="Continue" means the server will not be shutdown but still the rest of the system will continue
    • If we do not specify any onTimeout attribute, it will act according to the current default behavior, i.e. the tier and the system deployment will timeout and users have to manually abort the system and retry the deployment after addressing the issue responsible for the workflow timeout. See the following example of how to configure this within the serverType tag:
<serverType role="loadbalancer" min="1" max="8">
              <startup timeout="1200"  onTimeout="Continue"></startup>

Release 1.7.0 (November 2, 2009)

  • Added ability to search application-centric system logs
  • Added ability to schedule events to allow users to automatically execute application centric complex workflows for n-tier systems at the scheduled time; the scheduler basically triggers the event at the scheduled time and IMOD engine execute the corresponding workflow associated with the event
    • Ability to schedule complex or simple maintenance tasks to be performed automatically at the scheduled time, e.g. application specific backups, execution of application specific batch jobs, etc.
    • Ability to start/stop complex n-tier systems at the scheduled time

Release 1.6.0 (October 14, 2009)

  • Added support for Rackspace Cloud, IMOD now supports following for Rackspace:
    • Application Centric n-tier configuration: With one click, IMOD automatically brings online one or multi-server systems, configures middleware, deploys application/workload, and starts all dependent services in a specified order
    • Automation: Ability to automate complex workflows to handle run-time production exceptions without human intervention
    • Monitoring and alerts: Users can monitor resources used by their applications and set up alerts to proactively manage application service levels
    • Application Centric Accounting: Ability to track usage of all servers used by an application so app owners know exactly the usage of resources for their application.
    • Example system definition for managing deploying and managing applications on Rackspace cloud
  • Example system definition for deploying and managing Bitnami Images
  • Added support for specifying Kernal Images and Ram Disk for Amazon EC2 servers. This will allow users over-ride Kernel (AKI) and RamDisk (ARI) for an image without having to rebundle the image. Following optional tags can be added to the Amazon Server type definition in the System Definition:
    • <kernelImage>aki-20c12649</kernelImage>
    • <ramDisk>ari-21c12648</ramDisk>

Release 1.5.0 (August 31, 2009)

  • Custom Events: Event definition for triggering scale-up scale-down, recovery, or custom events can be defined from the drop down menu on the monitoring page even when the system (Application infrastructure) is not running. Events can be persisted, i.e. no need to redefine them on restarting the system
  • Enhanced the format for defining automation (custom workflows) to give more flexibility to users. Going forward use this new format for defining, scale-up, scale-down, recovery, and any custom workflows as we will deprecate the older format
  • Application Centric Logging: Added system level logging to have seperate logs for each deployed application infrastructure by adding new tab for system logs. This gives more transparency to each application owner on SLAs of the resources used by their application
  • Application Centric Accounting: Added ability to track infrastructure usage for each managed application individually. This allows application owners to know the usage of resources by their application when multiple applications are deployed in the same account

Release 1.4.6 (July 09, 2009)

  • Signed the code for SSH applet to prevent the unsigned warning message
  • Implemented upper and lower limits on the number of servers based on server type in each tier to allow users to prevent auto-scaling up or auto-scaling down beyond the specified range
  • Enhanced the 3 tier LAMP stack example system template to include auto-recovery event to recover the server and configure it automatically in the context of the application in case any of the servers dies
  • Added quick start user guide for beginners

Release 1.4.5 (June 03, 2009)

  • Automation for run-time service level management
    • Ability to add system level alerts
    • Ability to define custom events at system level
    • Ability to automatically execute custom actions in response to custom events
  • Additional images for EU location
  • Updated n-tier documentation
  • Added example system definition template for Ruby on Rails

Release 1.4.4 (April 15, 2009)

  • European region support
  • Windows support
    • 256-bit encryption of elastic block storage for windows
    • monitoring support for windows
    • Kaavo public windows images (with out-of-the-box support for encryption and monitoring)
  • Billing/Accounting system
    • Track your instance usage
    • View monthly billing information
  • A LAMP stack example NTier system defintion file is available as a new Template. This example uses the php-colab application as an example. In this system, we have two Apache based front-end load-balancers (load-balanced via DNS round-robin), a php based application-tier, and a MYSQL cluster database back-end.

Release 1.4.2 (Feb 17, 2009)

  • Added support for scale-up/scale-down in the system definition files. Now you can setup scale-up and scale-down actions to dynamically add more servers to a running system when the needed, and also to reduce the servers when the demand goes down.
  • Kaavo public images are shown at a separate tab on the dash-board.
  • Significant Performance improvements for the Graphical User Interface

GA Release - 1.4 (January 12, 2009)

  • N-Tier: World's first application-centric, n-tier cloud computing automation
    • Ability to define a complete n-tier system in XML system definition file (SDF)
    • Launch a multi-tier system consisting of many servers using a single-click
    • Clone an entire system via single-click (e.g. clone DEV system to QA system)
    • Easily deploy a system starting from a template. Half a dozen system templates are provided as examples, ranging from a simple single-tier system with a java application on it, to a 3-tier system consisting of a MYSQL Cluster database, a JBOSS application server tier, and an Apache web-tier.
  • Security: Full 256-bit security
    • Full volume level encryption, with elastic block storage volumes. You can create dynamic encrypted volumes, and attach them to running instances. All data on these volumes is encrypted.
    • Support for delegated users. Users in different roles have different access-levels to the application.
  • Monitoring: Out-of-box support for monitoring your instances.
    • Monitor real-time graphs of the vitals (CPU, Memory, Disk Space, Bandwidth etc.)
    • Setup rule-based trigger alerts (e.g. "Notify me when used Disk Space goes above 70%")
  • Automated Backups: Support for automated backups
    • Backups are scheduled via a scheduling service to backup automatically (daily, weekly, monthly etc.)
    • Support for automatic rotation of the backups, to limit the total snapshots.
  • Kaavo Images: More than a dozen Kaavo images, that provide out-of-the-box:
    • 256-bit encryption
    • Pre-installed monitoring agents
    • Various flavors of Linux, both 32-bit and 64-bit versions
  • Other:
    • Built-in secure command-shell to connect to any instance over ssh.
    • Built-in secure ftp (s-ftp)
    • Fully functional tradition dashboard for instance-level management

Fully Functional Trial

Free access to Kaavo's IMOD is available via fully functional trial. You can self-register anytime at to take advantage of this.