Creating or modifying a service blueprint

When creating or modifying a service blueprint, you must specify its components:

• Service definition (for example, the web tier of the pet store application)
• Service deployment definition (for example, the web tier is deployed on a VM with 4 CPUs; 8,192 MB of RAM; and a 20-GB disk).

To create the service definition component in a service blueprint, you must specify the OS and software packages (from the Product Catalog) and optional actions needed for the service definition to run correctly. For example, the web server tier in the pet store application might use AO Workflow to contact the Apache server after it is installed. If the Apache server is running, then you can install the PHP software package.

This topic includes the following sections:

To create the service blueprint (including the service definition)

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Blueprints.
2. In the Service Blueprints workspace, click New .
   The Service Blueprints Definition editor is displayed.
3. Define the general information:
   1. Enter the name of the new service blueprint that describes the application or server type (for example, LAMP Gold or MediaWiki).
      
   2. If needed, select or create tags, as described in Managing service blueprint tags.
   3. Enter a helpful description of the components of the service blueprint or other helpful information (for example: Redhat 5.4, Apache, mySQL, PHP).
   4. Enter the author of the service blueprint.
      
4. In the the Service Definition tab, click New in the Components table.
   The Component Details editor is displayed:
   
5. Enter a name that briefly describes the component (for example, Application Web Server).
6. If needed, select or create tags, as described in Managing service blueprint tags.
7. Enter a helpful description (for example, Application web server).
8. In the Operating System tab, add an OS to install with this component.
   1. Select an available OS from the list (consisting of BMC Server Automation packages or Amazon AMI files) and then click Add.
      To filter the list, type a letter, word, or phrase in Search. The search operation is based on all the fields that compose the OS names.

      Note

      You must select one OS per component.

      To modify the OS, select it, and click Remove. You must then add a different OS.
   2. (optional) For the OS, specify the post-installation type of action to run.
      You can select an NSH script or AO Workflow that runs a particular action. For example, you can run AO Workflow that checks the hardware configuration on your VM.

      Note

      If you select an AO Workflow that uses a BMC Server Automation object, you must first define that object in BMC Server Automation.

   3. (optional) Enter the action to perform.
      Enter the name of the script (for example, open_port_windows.nsh) or AO Workflow (for example, MyModule:).

      Note

      If you enter a BLPackage or NSH script, the values must exactly match the local properties of your BLPackage or the parameters of your NSH script in BMC Server Automation. You must ensure that the script or AO Workflow is actually available in BMC Server Automation.

   4. (optional) Click Set after you specify the package actions and their order.
      
9. (optional) In the Software Packages tab, add or remove the software packages to install with this component.
   
   You can select from a list of available software packages (consisting of BMC Server Automation packages or Amazon AMI files). To filter the list, type a letter, word, or phrase in the Search field. The search operation is based on all the fields that compose the software package names.
   1. Rearrange the software packages into the required order of installation by selecting the package and then dragging it to its new order in the column.
   2. For each software package, specify the preinstallation and post-installation type of action to run.
      You can select an NSH script or AO Workflow that runs a particular action. For example, you can run a AO Workflow that checks the hardware configuration on your VM before installation, or you can run a script that sets the Apache administrator password after installation.
   3. Enter the type of action to perform.

      Type of action	Format and description
      NSH script	Do not enter the full path. For example: set_apache_admin_password.nsh
      AO Workflow	Enter the delineated path. For example: MyProvisioningActions:UpdateDNS

      You must ensure that the script or AO Workflow is actually available in BMC Server Automation. The NSH scripts and AO Workflow are defined in BMC Server Automation.

      Note

      If you do not define the install actions for the software packages, you cannot define start and stop operations for the Component. For more information, see Creating or modifying an operation

   4. Click Set after you specify the package actions and their order.
      
10. (optional) Click the Operations tab to define the start or stop operations to perform on the software packages in their correct sequence.
    For example, in a three-tier system, you might specify to start the OS first, the database second, and the web server third.
    
    1. In Actions to perform on deployed software, click New .
    2. Select a package (for example, Apache Version 2.2 for Windows).
    3. Select the action type (for example, Script).
    4. Enter the action (for example, start).
    5. Click OK.
    6. Rearrange the actions into the required order by selecting the action and then dragging it to its new order in the column.
11. (optional) Click the Requirements tab to define the planned allocation of resources.
    
    1. Set the minimum number of CPUs, minimum memory (MB), and minimum storage (GB).
       You can define constraints for a particular location — for example, an application web server in San Jose CA must have 2 CPUs, 2,048 MB of RAM, and 10 GB of storage.
    2. (optional) Under User Defined Requirement, document any additional requirements for the component.

       Note

       The information is for documentation purposes only, and it currently has no effect on the service deployment; BMC Cloud Lifecycle Management does not enforce these requirements.

12. Click OK to finish the service definition of the blueprint.

To modify the service blueprint

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Blueprints.
2. Select an existing service blueprint and click Edit .
3. Modify the settings as needed.
   You can modify components and resource sets directly in the graphical editor.
4. Click Save.

Related topics

Creating and managing requestable services
Building service blueprints
Creating cloud services
Navigating the Service Blueprints window
Copying a service blueprint