Creating a Trac-Bug tracking tool on RHEL 5.9 service offering
This topic describes the tasks that you must perform in BMC Cloud Lifecycle Management to create the service offering that the end user can then use to provision the application infrastructure (for example, an OS and an application package). It includes the following topics:
To create the service and the service offering
In the BMC Cloud Lifecycle Management Administrator console, you must add a service and a service offering.
For Trac service blueprint, create a service and service offering based on the available deployment model. The Trac Content-Pack supports single-tier service deployment model. In the single tier deployment model, Trac is installed on one instance of a server.
For Trac service blueprint, you can create a service and service offering based on the required deployment model. Trac service blueprint supports the following service deployment models:
Deployment model | Description |
|---|---|
Single-tier | In the single-tier deployment model, Trac will be installed on a single instance of a server along with Apache, Subversion and MySQL. |
Multi-tier | In the multi-tier deployment model, Trac will be installed on a single instance of a server along with Apache, Subversion and MySQL will be installed on another instance of a server. |
To create a service
To create a service offering
To make the provisioning request
- Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
In the New Service Request dialog box, click the server provisioning service you want to display the Submit Request dialog box.To complete the Service Request for Trac-Bug tracking tool, specify the following Parameters:
Parameters
Description
tracproject
Trac Project Name
tracadmin
Trac Admin User
tracdb
Trac Database Name
mysqlrootpass
MySQL root user password
mysqlport
MySQL User Defined Port
httppass
Password Authentication for Trac Admin User
dbserver
Database Server in case Mutitier, IP address will be automatically chosen while installation
- Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
- Enter the data in the required fields to complete the request for an instance of the service request. You can click Next to review the details.
- Click Submit. The request is added to the Pending Activity list in the Service Instances window.
The request status is displayed in the Pending Activity list of the Service Instances window. You can double-click on the service request to see its detailed information.
For more detailed procedures, see Requesting cloud services.
To validate the provisioned components
After provisioning the blueprint, you can validate the Trac components setup in your environment.
Components | How to verify | Results |
|---|---|---|
To verify Trac | To verify Trac, visit following URL: http://ServerIP or Hostname/etrac Note: update the URL as per your environment. | This URL displays default page of Trac-Bug tracking tool. |
To verify Apache Web Server | To verify Apache Web Server, run the following command: httpd -v | This command displays Webserver version. |
To verify SVN | To verify SVN, run the following command: svnadmin --version | sed -n 1p | This command displays SVN version. |
To verify MySQL | To verify MySQL, run the following command: mysql -V | This command displays MySQL version. |
Where to go next
After you have created the service offering, the cloud end user can request a service offering from the My Cloud Services console. To view a list of tasks that the cloud end user can perform to manage your cloud services, see Managing cloud services.