Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Creating a Subversion 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 Subversion service blueprint, you can create a service and service offering based on the available deployment model. The Subversion service blueprint supports the following service deployment models:

Deployment model

Description

Subversion

In the Subversion deployment model, Subversion is installed on one instance.

Subversion with Apache httpd

In the Subversion with Apache httpd deployment model, Subversion is installed along with httpd (apache) and mod_dav_svn module on one instance.

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 Serviceservicecatalog_newservice_button.png.
  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.
    serviceinstances_request1.png
  2. In the New Service Request dialog box, click the server provisioning service you want to display in the Submit Request dialog box.
    serviceinstances_request_submit.png
  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 Subversion components setup in your environment.

Component name

How to verify

Results

Check whether Subversion has been installed.

To check whether Subversion has been installed, run the following command:

rpm -qa | grep -i subversion

You receive a successful command output.

  Create a demo Subversion repository.

To create a demo Subversion repository, run the following command:

svnadmin create /tmp/test

The repository is created with no errors.

Check the contents of /tmp/test directory.

To see the list of content, run the following command:

ls -l /tmp/test

This command displays the following output:

rwxr-xr-x 2 root root 4096 May 28 16:01 conf
drwxr-sr-x 6 root root 4096 May 28 16:01 db
-r--r--r-- 1 root root 2 May 28 16:01 format
drwxr-xr-x 2 root root 4096 May 28 16:01 hooks
drwxr-xr-x 2 root root 4096 May 28 16:01 locks
-rw-r--r-- 1 root root 229 May 28 16:01 README.txt

 

 

Check whether Apache has been installed.

To check whether Apache has been installed, run the following command:

rpm -qa | grep -i httpd

This command displays the following output:

httpd-2.2.15-15.el6_2.1.x86_64
httpd-2.2.15-15.el6_2.1.x86_64

Check whether the Subversion module for Apache has been installed.

To check whether the Subversion module for Apache has been installed, run the following command:

rpm -qa | grep -i mod_dav_svn

You receive a successful command output.

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*