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

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
2. In the Service Catalog, click Create a New Service.
3. Enter the service name.
4. 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.

     Note

     After you select the type and save the service, you cannot change the type.

5. Enter a description of the service.
6. 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

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
2. From the Service Catalog, edit or create a service.
   In the Service Offering tab, a default service offering is available, which you can edit.
3. Click Create a New Service Offering.

4. 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.

5. Add a Base Customer Price to define the amount charged to the customer for the service offering.
6. Add a Base Deployment Cost to define the amount that it costs to provide the service offering.
7. 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

1. Access Workspaces > Service Instances to display the Service Instances workspace, and click New Service Request.
   

   

2. In the New Service Request dialog box, click the server provisioning service you want to display in the Submit Request dialog box.
   
3. 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.
4. 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.

rpm -qa | grep -iw ntp

ntp-4.2.2p1-15.el5_7.1

service ntpd status

ntpd (pid  30927) is running...

netstat -apun | grep -i ntp

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

ntpdate -b ntpserverip
or
ntpdate -b 10.129.62.26

ntpdate[31346]: step time server 10.129.62.26 offset -0.003250 sec

ntpdate[31260]: the NTP socket is in use, exiting

service ntpd start

service ntpd stop

rpm -qa | grep -i tftp-server
rpm -qa | grep -i xinetd

xinetd-2.3.14-17.el5.x86_64
 
tftp-server-0.49-2.x86_64

netstat -aunp | grep 69

udp        0      0 0.0.0.0:69                  0.0.0.0:*       xxxx/xinetd

service xinetd status

xinetd (pid xxxx) is running 

tftp tftp-server-ip
 
for ex
 
tftp 10.128.76.237

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.