Cloud Computing Made Easy®
IBM 2-Tier Sample
From Cloud Computing Wiki - Kaavo
Contents |
Overview
Like other templates provided with IMOD, Apache-Jira-2-Tier Sample template 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 user has 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. 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
- Note: When configuring the System Definition please pick 32-bit Red Hat Enterprise Linux image for Web Tier(web_tier) and 32-bit SUSE Linux Enterprise Server image for App Tier(jira_tier). Other combination may work, however, we haven't tested them. By default this System Definition template has images configured for the RTP location and if you select the RTP location the image information is automatically filled for you in the IMOD UI, if you are launching the system in any other location you must select the images manually from the drop down for that location.
What does it do?
Brings online a 2 tier system with Apache web server in the web tier and JIRA issue tracking system in the app tier. First the servers are provisioned and then JDK, Tomcat, Apache are installed on the servers and JIRA and Apache are started, and JIRA servers in the app tier are added to the Apache loadbalancer. After the system is up and running go to http://ip-address-of-launched-server/jira. To view the configuration of the load balancer go to http://ip-address-of-launched-server/balancer-manager
What deployment time actions/workflows are included in the System Definition?
- install-jdk
- start-jira
- reset-apache
- start-apache
- configure-apache-balancer
- install-apache
What run-time actions/events are defined in the System Definition?
Three run-time custom actions for events are defined:
- system-scaledown to shutdown a server in the app tier and remove it from the load balancer
- system-scaleup to add a server in the app tier deploy and configure JIRA on it and register it with the load balancer
- server-recovery start a new server as replaced to the server that died, deploy and configure JIRA on it and register it with the load balancer
Note: You need to go configure the triggers for the events. Refer to the Quick Start Guide for how to configure triggers.
![[Wiki Home]](/skins/common/images/wiki.png)