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 Cisco HCS service blueprints

Service blueprints describe the functional structure of a given service offering, including its functional components and communication paths. They also define how a service offering is to be deployed under different circumstances. Each service offering in the service catalog has a set of service blueprints used for its instantiation.

This topic provides the following information for creating Cisco HCS blueprints:

 

Service blueprint guidelines for the Cisco HCS Provider

Be aware of the following guidelines that are specific to the Cisco HCS Provider service offering.

Cisco HCS entities

Cisco HCS has the following entities, which are mapped with the service blueprints in the BMC Cloud Lifecycle Management and tagged for the placement rules:

Application type

Following are the sample application types that are supported in the current release:

  • CISCO Unified Communications Manager (CUCM)
  • CISCO Unified Presence (CUPS)
  • CISCO Unity Connection (CUCXn)

Following are the sample Cisco HCS packages that would be mapped to the service blueprints:

Basic

Foundation

Standard

CUCM (Voice)

CUCM (Voice)

CUCM (Voice)

CUPS (Presence)

CUPS (Presence)

CUPS (Presence)

 

 

CUCXn (Voicemail)

Application instance (AI)

Application instance is a deployment instance of the application type.

Application instance node (AIN)

Application instance node is a virtual machine (VM) within an application. Cisco HCS has defined the following application instance nodes for each application type:

Application type

Nodes

CUCM

  • Publisher (PUB)
  • Subscriber (SUB)
  • Music on Hold (MOH)
  • Trivial File Transfer Protocol (TFTP)

CUPS

Cisco Unified Presence Server (CUPS)

CUCXn

CUCXn

Note

The AIN count differs for the different deployment models of the application type.

Mapping the Cisco HCS entities with the service blueprints

A service blueprint caters to all the deployment models containing multiple application types. The service definition and deployment definition of the blueprint are mapped to the Cisco HCS entities in the following way:

  • Application type: Mapped to multiple functional components
  • Application instance nodes (AIN): Resource sets for the deployment definition
  • Application templates: Product catalog entries (DML) available as the installable resource in the Compute Resources section of the resource set.

In the service definition section as shown in the following figure, functional components cater to all the deployment models (Small, Medium, and Large) with the combinations of two or more application types (CUCM, CUPS, and CUCXn).

ServDefn.png

 

Note

Functional components are reused among different service deployments definitions.

In the service deployment definition section, 12 deployment definitions exist for the combinations of Cisco HCS packages (Basic, Foundation, and Standard offerings) and all the deployment models for different application types (CUCM, CUPS and CUCXn). Each service deployment definition has corresponding resource sets per the deployment model. So, a Cisco HCS service blueprint has all the functional components required for all the possible combinations of application types and deployment models as shown in the following example. 

Example of a Basic HCS Small service offering

The Basic HCS Small service deployment definition has 6 CUCM resource sets (1 PUB, 2 SUB, 1 MOH, 2 TFTP, and 2 CUPS). You need to create the resource sets as PUB(1), SUB(1), SUB(2), MOH(1), TFTP(1), TFTP(2), CUPS(1), and CUPS(2) by using the respective functional components CUCM-Small-PUB, CUCM-Small-Subscriber 1, CUCM-Small-Subscriber 2, CUCM-Small-MOH, CUCM-Small-TFTP 1, CUCM-Small-TFTP 2, Presence-Small-CUPS 1 and Presence-Small-CUPS 2.

Service deployment definition

Resource sets

Functional components

Basic HCS Small

PUB(1)

CUCM-Small-PUB

 

SUB(1)

CUCM-Small-Subscriber 1

 

SUB(2)

CUCM-Small-Subscriber 2

 

MOH(1)

CUCM-Small-MOH

 

TFTP(1)

CUCM-Small-TFTP 1

 

TFTP(2)

CUCM-Small-TFTP 2

 

CUPS(1)

Presence-Small-CUPS 1

 

CUPS(2)

Presence-Small-CUPS 2

Adding Cisco HCS templates in the service blueprint

  • You must create the DML entries for the templates in the Product Catalog Console with the same template name as that visible in the vCenter.

    Note

    Provisioning flow does not work if the template used for provisioning is available on multiple datastores of the vCenter server, so ensure that the template is stored on a single datastore.

  • You must select the correct DML entry as visible in the Installable Resources section of the blueprint for the associated resource set.

To create a service blueprint

To create a service blueprint for a Cisco HCS instance, you can follow the general service blueprint creation procedure. However, you should also follow the guidelines that describe the distinctions for service blueprints that are created for Cisco HCS instances.

  1. In the Service Blueprint window, click New to open the Service Blueprint Definition window.
  2. Follow the steps for creating a service blueprint. See Building a Service Blueprint and related procedures.

To define the Cisco HCS service deployment definitions and resource sets

Following sample Cisco HCS deployment models are considered to create the service deployment definitions and resource sets in this release:

Deployment model

Supported subscribers

Small

2500

Medium

7500

Large

10000

For details on defining Cisco HCS service deployment definitions and resource sets, see Creating-Cisco-HCS-service-deployment-definitions-and-resource-sets.

To prepare the service offering instance

Create and use an Cisco HCS instance as you would any service offering. For detailed procedures, see Creating-cloud-services.

To set service offering options

Set the service offering options for Cisco HCS instances as you would for other options. For information and instructions for defining options, see Service-Catalog-options-and-option-choices.

Note

For the Cisco HCS service offering, only the postdeployment options are supported. See how to define service postdeployment actions for details.

To create the requestable offering definition

Define your Cisco HCS requestable offering as you would any other offering. For instructions, see Creating-a-requestable-offering-definition.

Note

For the Cisco HCS definition, select Compute for the Type value.

 

 

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