Creating a RHEL 6.2 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.
To create a service
- From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
- In the Service Catalog, click Create a New Service
.
- Enter the service name.
- For Type, select a service type.
- Business service — Services that customers use and that show the customer view of services, such as email or an online store.
Technical service — Supporting IT and infrastructure resources required to support business services that are not visible to customers, such as servers, applications, and network CIs.
- Enter a description of the service.
- Do one of the following actions:
- To create the service offering, click Apply.
- To create the service offering later, click Save to save your selections and close the window.
To create a service offering
- From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
- From the Service Catalog, edit or create a service.
In the Service Offering tab, a default service offering is available, which you can edit. - Click Create a New Service Offering.
In the General Information tab, define the options described in the following table.
Option
Description
Default Service Offering
Enable this option to make the selected service offering the default for the service. Unless users select a different service offering, the default service offering is used.
Name
A short, descriptive name for the service offering.
Description
A more detailed description of the service offering.
Service Blueprint
Specify the software and hardware to associate with the service offering by selecting one of the available blueprints.
Reference Definition
Specify which version of the blueprint to use for this offering. Choose one of the following:
Latest version—Use the latest version of the specified service blueprint.
Specific Version—Use the version of the service blueprint that you select.
Identified by Tag—Select the tag that is used to identify a version of a service blueprint. Because no two versions of a service blueprint can have the same tag, if the association of the tag to a version changes, your blueprint will use whichever version makes use of that tag.Definition
Specify how to deploy the selected service blueprint. From the list, select a definition that is available for the chosen service blueprint.
- Add a Base Customer Price to define the amount charged to the customer for the service offering.
- Add a Base Deployment Cost to define the amount that it costs to provide the service offering.
- Click Apply.
This action activates the Options tab. You now also can create a requestable offering (for example, a request definition or a post-deploy action). For additional information, see Creating-a-requestable-offering in the BMC Cloud Lifecycle Management online technical documentation.
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.
- 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 NTP and TFTP components setup in your environment.
Component name | How to verify | Results |
---|---|---|
NTP installation | To check if NTP rpm has been installed successfully, run the following command: rpm -qa | grep -iw ntp | It displays following output: ntp-4.2.2p1-15.el5_7.1 |
NTPD service | To check if NTPD service is running, run the following command: service ntpd status | It displays following output: ntpd (pid 30927) is running... |
NTP listening port | To check if NTP is listening on port 123 with UDP protocol, run the following command: netstat -apun | grep -i ntp | It displays the following output: udp 0 0 10.129.62.82:123 0.0.0.0:* 30927/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 30927/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 30927/ntpd udp 0 0 :::123 :::* 30927/ntpd |
NTP client server communication | To check if NTP client is able to able to communicate with NTP server, run the following command: ntpdate -b ntpserverip or ntpdate -b 10.129.62.26 | If communication is established, it displays the following output: ntpdate[31346]: step time server 10.129.62.26 offset -0.003250 sec If communication is not established, it displays the following output: ntpdate[31260]: the NTP socket is in use, exiting |
Start NTP service | To start NTP service, run the following command: service ntpd start | Starts the NTP service. |
Stop NTP service | To stop NTP service, run the following command: service ntpd stop | Stops the NTP service. |
xinetd and tftp-server installation | To check xinetd and tftp-server installation, run the following command: rpm -qa | grep -i tftp-server rpm -qa | grep -i xinetd | It displays the following output: xinetd-2.3.14-17.el5.x86_64 tftp-server-0.49-2.x86_64 |
xinetd service port | To check if xinetd service port is listening on port 69, run the following command: netstat -aunp | grep 69 | It displays the following output: udp 0 0 0.0.0.0:69 0.0.0.0:* xxxx/xinetd |
xinetd service status | To check if xinetd service is running, run the following command: service xinetd status | It displays the following output: xinetd (pid xxxx) is running |
Verify TFTP server | To verify TFTP server, run the following command from TFTP client: tftp tftp-server-ip for ex tftp 10.128.76.237 | It displays the TFTP server status. |
Where to go next
Once 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 the cloud end user can perform to manage your cloud services, see Managing-cloud-resources in the BMC Cloud Lifecycle Management online technical documentation.