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.

Creating service deployment definitions and resource sets

You use the Service Deployment Definitions tab (in the Service Blueprints Definition editor) to specify how resources are assigned to support the functionality that is described in the service definition of a blueprint. For example, you might specify that the web tier of your Medium pet store application is deployed on a virtual machine (VM) with 4 CPUs; 8,192 MB of RAM; and a 20-GB disk.


A resource set defines a VM or a physical machine. A resource set can have multiple instances, to include a pool of VMs.


When defining network resources on the Network Resources tab (for example, NIC details), you can tag the NIC and then use policies to match tags on networks in the container.
Make sure that the network pod configuration allows firewalls and load balancers to be used.
See the BMC Network Automation configuration for valid values in your network provider.

See the following topics for additional information about service deployment definitions and resource sets:

Before you begin

If you are using a Virtual Guest Package (VGP) as an installable resource, you should understand the OS and software present in the VGP before you define the attributes in the Compute Resources tab.

To create service deployment definitions and resource sets

  1. In the Blueprint Definition Editor, click the Service Deployment Definitions tab.
  2. In the Service Deployment Definition Name pane, shown at the left in the following figure, click New .
  3. Enter a name that briefly describes the deployment definition (for example, Large for a large deployment).
  4. In the Details section, select the tags (for example, Service Level[Gold], Tier[Web], Security Level[Low]).
  5. Enter a helpful description (for example, 2 VMs).
  6. In Resource Sets, click New .
  7. In the Resource Set Details dialog box, enter the following information:
    • Name that briefly describes the resource set (for example, Web Server)


      Beginning in version 3.1, resource set names must be unique within a deployment model.

    • Tags that prescribe where to place the VM itself (for example, the hypervisor cluster) or where to place the initial disk of the VM (typically the boot disk, for example, the *C:* drive).
    • Helpful description (for example, Vmware VM with 4CPUs, 8 GB memory).
  8. From the list of available components, add the components to include with this resource set or remove components.


    Beginning in version 3.1, a component can only be added to one resource set within a single deployment model. You can add the same component to multiple resource sets if each of those resource sets belongs to a different deployment model.

Related topics

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

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