Creating a CMS Drupal 7 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).

Note

Although services and service offerings are bundled with the zipkits, you might want to use the procedures to create a service and service offering to create or edit these artifacts.

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 CMS Drupal 7 service blueprint, create a service and service offering based on the available deployment model. The CMS Drupal 7 service blueprint support following deployment models:

Deployment model	Description
Single-tier	In the single-tier deployment model, CMS Drupal will be installed on a single instance of a server along with Apache, Subversion and MySQL.
Multi-tier	In the multi-tier deployment model, CMS Drupal 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

Excerpt named creatingservice was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

To create a service offering

Excerpt named creatingserviceoffering was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45._CSMinclusionsLib._inclusionsLibZipKit._createServiceOfferings.WebHome.

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 in the Submit Request dialog box. To complete the Service Request for CMS Drupal 7, specify the following Parameters:

Parameter	Description
Drupal Database Name	Database Name for Drupal CMS
Drupal Database Password	Database User Password for Drupal CMS
Confirm	Database User Password for Drupal CMS
Drupal Database Username	Database User Name for Drupal CMS
MySQL Port	MySQL User Defined Port No, eg. 3309 etc
MySQL Root Password	MySQL Root User Password to Set
Confirm	MySQL Root User Password to Set
Site Name	Display Name for Drupal CMS at Home Page
Time Zone	Time Zone where the Website belongs to

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 and Requesting cloud services in the legacy console.

To validate the provisioned components

After provisioning the blueprint, you can validate the CMS Drupal 7 components set up in your environment.

Components	How to verify	Results
To verify Apache web server	To verify Apache web server, run the following command: httpd -v	This displays Apache web server version.
To verify MySQL	To verify MySQL, run the following command: mysql -V	This command displays MySQL version.
To verify Drupal	To verify Drupal, run the following command: php -v	This command displays Drupal 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-resources.