Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Initiating the server provisioning request in BMC Cloud Lifecycle Management

This topic provides high-level guidelines for initiating the server provisioning request of a bare-metal virtual machine (VM), a physical server, or a VM with template. The topic includes the following sections:

This topic covers tasks that you perform in the following BMC Cloud Lifecycle Management workspaces:

  • Service Blueprints
  • Service Catalog
  • Service Instances

The workflow is similar to that for creating any other service request:

  • Define your Service Blueprint parameters.
  • Select your service offering details in the service catalog.
  • Select your service offering instance and then submit your request.

The chief distinction among the server provisioning requests of the different server types lies in their Service Blueprint definitions, specifically the Compute Resources attributes (Service Deployment Definition > Resource Set Details).

Characteristics of server types

The following table summarizies the characteristics of the different server types:

Server type

Characteristics

Physical server

  • Physical Type option
  • operating system (OS) package. It does not use a virtual guest package.

Bare-metal virtual machine

  • Virtual Type option
  • virtual guest package from the list of installable resources. This package does not contain an operating system.
  • able to install an operating system on bare-metal VM

VM with template

  • Virtual Type option
  • virtual guest package from the list of installable resources. This package does contain an operating system.

Default software packages and software packages with options

You add the software packages that you want to be installed by default to the Service Blueprint. These are the software packages that will automatically be deployed to the target system during provisioning. For example, when you select the service offering LAMP stack, you also select the default packages that are associated with it.

If you add option choices to packages, these packages display in the corresponding list of available packages or resources. They are not added to the Service Blueprint and they are not installed by default. Instead, they are appended to the selected packages in the Service Blueprint at run-time and are installed sequentially.

To create options for the packages, see Service Catalog options and option choices. To configure the Service Blueprint to accept the option selections, see Configuring end-user Option Choices in service blueprints.

To define the Service Blueprint for the OS, software, or virtual guest package

In the Service Blueprint workspace, you define the Service Blueprint for the specified operating system, software package, or virtual guest package that the Publish Product Catalog job makes available to BMC Cloud Lifecycle Management. The package retains the name that it was assigned in BMC Server Automation.

  1. From the BMC Cloud Lifecycle Management Administration console, choose Workspaces > Service Blueprints to display the Service Blueprints workspace. Then click the New icon to display the Service Blueprint Definitions editor.

  2. In the Service Blueprint Definitions editor, enter a descriptive name for the server type. You may want to distinguish the server by prepending or appending an appropriate prefix or suffix: for example, "ps" for physical server, "bm" for bare-metal server, or "vmt" for VM with template.
  3. Add tags and descriptions to further distinguish the Service Blueprint.
  4. Click New in the Components table to display the Component Details editor.

  5. Select an operating system package to install.

    Note

    While the VM with template does not require an operating system package, you must make this selection to complete the Service Blueprint processing.

  6. Optionally, you can specify post-install actions, add software packages to install in the Software Packages tab, and define stop/start operations in the Operations tab. In the Requirements tab, you can specify CPU, memory, and storage requirements.
  7. Click OK to complete this part of the Service Blueprint definition.

For a more detailed procedure, see Creating or modifying a service blueprint.

To define Compute Resources attributes

Defining Compute Resources attributes distinguishes the different server types. It is important that you specify the appropriate attributes.

  1. If you have not already done so, complete the steps in To define the Service Blueprint for the OS, software, or virtual guest package.
  2. In the Service Blueprint Definition editor, click the Service Deployment Definitions tab.
  3. In the left pane, click the New icon and enter a Server Definition Deployment Name.
  4. Under Resource Sets, click the New icon to display the Resource Set Details.
  5. In the Components tab, add any components to include with the resource set.
  6. Click the Compute Resources tab to select the resource set details.

  7. Use the guidelines in the following table to help distinguish attributes for the different server types:

    Resource set attribute

    Description

    Instances

    Number of server instances that you intend to provision with the specified attributes

    Tags

    Identifying tags for placement purposes

    Associated technical services

    Technical services associated with the resource set

    Type

    The options are physical or virtual. Choose the Physical option for the physical server type. Choose the Virtual option for bare-metal VMs and for VMs with templates.
    If you choose the Virtual option, the Installable Resource and Install OS Package fields are displayed.

    CPU Count

    The number of CPUs for this instance. Your provisioning request must exactly match the value in the CPU Count field.

    Memory Size (MB)

    The amount of RAM for this instance. Your provisioning request must exactly match the value in the Memory Size field.

    Hardware Architecture

    Designates the machine type. Your provisioning request must exactly match the value in the Hardware Architecture field.

    Install Software

    Installs optional software, apart from the OS, that is already part of the Service Blueprint definition. It does not affect optional software that is not a component of the Service Blueprint.

    Installable Resource

    This resource is available when you select the Virtual type. It accesses a list of selectable virtual guest packages for bare-metal VMs and VMs with templates:


    The Product Catalog populates this list of software packages from the job run in BMC Server Automation. The installable resource can be a template package with an operating system for VMs with templates. Or it could be a package without an operating system for bare-metal VMs.

    Install OS Package

    This resource is available when you select the Virtual type. Select this option for physical servers and bare-metal VMs (the virtual guest packages of bare-metal VMs do not contain operating systems).
    The virtual guest packages for VMs with templates already contain operating systems. De-select this option for VMs with templates.

    Note

    Currently, because your provisioning request must match exactly the values in the CPU Count and Memory Size fields, you cannot increase or modify the values of the specified configuration. If you have the need for more CPUs and greater memory, you have to create multiple instances of the server configuration.

  8. Continue by completing the information in the Network Resources tab, and then click OK when done.

For a more detailed procedure, see Creating service deployment definitions and resource sets.

To add a service to the Service Catalog, create a service offering, and create a request definition

After you have completed your Service Blueprint definition, you can add the new service to the Service Catalog and specify its parameters.

  1. Choose Workspaces > Service Catalog to display the Service Catalog workspace.
  2. Click the Create a New Service icon, and enter the service name and type.
  3. Complete the details on the General Information tab.

  4. Add details about price and cost, and click Save.
  5. To create the request definition, double-click the service offering to display the Edit Service dialog.
  6. Click the Create request definition icon .


    After defining the service offering and request definition, you can make a provisioning request.

For more detailed procedures, see Creating new services for the Service Catalog, Creating a service offering, and Creating a requestable offering.

To make the provisioning request

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

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

Was this page helpful? Yes No Submitting... Thank you

Comments