Cloud Computing Made Easy®
Terremark Jira Sample
From Cloud Computing Wiki - Kaavo
Contents |
Overview
Like other templates provided with IMOD, the Terremark Sample System Definition is provided as an example to help users develop their own custom System Definitions. Users are expected to develop their own system definitions or customize the provided solutions for their own needs. The information assumes that the users have basic understanding of deploying and starting systems in IMOD. Please refer to the Quick Start Guide to learn the basics of deploy and starting a system.
Before starting this please make sure Terremark Account is Setup
- Watch this webinar to learn more about Kaavo integration with Terremark
- For uploading files or your custom code to the server refer to the FAQ on how to upload/download file to and from servers in the cloud
What does it do?
Brings online a fully functional JIRA issue tracking system online with a single click. After the JIRA system is up and running go to http://ip-address-of-launched-server:8080 note you have to enter the port in the url to access the JIRA software. Note IMOD has the capability to deploy and manage applications with servers/resource running across multiple cloud providers. Watch the following video to learn how to deploy across multiple cloud providers
- Note: We selecting server for this deployment for testing we used CentOS 5.2 1 cpu 1.5GB memory. If you select an unsupported OS, monitoring may not work automatically. Please refer to the installing monitoring section for more details. Also look at the following reference for selecting the server and OS.
- In the sudo password field please enter the password for the image. This is the password required for executing the sudo command. You will get the password from the description of the image in the Terremark console. You can see the description field by bringing up the 'Create server' window and selecting the image.
What deployment time actions/workflows are included in the System Definition?
Installs the JAVA, installs Tomcat with JIRA and starts the Tomcat server to bring the JIRA online
What run-time actions/events are defined in the System Definition?
Three run-time custom actions for events are defined:
- Scale up, scaling up
- Scale Down, for scaling down
- Server Died, for auto recovery
Note: You need to go configure the triggers for the events. Refer to the Quick Start Guide for how to configure triggers. Actions/events are reusable across templates and cloud providers as long as you avoid using cloud provider specific attributes in custom actions. For more information on this refer to the common server attributes section of the N-tier guide
![[Wiki Home]](/skins/common/images/wiki.png)