Creating Cisco HCS service deployment definitions and resource sets
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.
To create service deployment definitions and resource sets
- In the Service Deployment Definitions tab of the Blueprint Definition Editor, shown in the following figure, click New
:
- Enter a name and description for the service deployment definition.
- In the Resource Sets tab, click Add
.
- In the Resource Set Details window, shown in the following figure, specify a name and description for the resource set:
- From the list of available components, select the components for this resource set and click Add.
- In the Resource Set Details window, click the tags
icon to tag the component of the resource set.
Select the tag to add and click OK.
In the Compute Resources tab, shown in the following figure, specify the compute attributes that are required for this resource set:
In the Network Resources tab, as shown in the figure below, configure the Network Interface Cards (NICs) with the following details:
- NIC Number: Specify the NIC number.
- NIC Tags: Select the NIC tag (applicable only if you select Use Network Policies in the Network Selection Method).
- Network Selection Method: Select Use Label and specify Management.
- IP Address: Select an option:
- Dynamic: The internet protocol must be selected dynamically during virtual machine (VM) provisioning.
- Static: The user must select the internet protocol for VM provisioning.
- Click OK to close the window.
- Click Save to commit the blueprint and all your changes.
To define a service deployment definition parameter
After you have created the service definition, you are ready to define service deployment definition parameter for the Cisco HCS Provider. The service deployment definition parameters apply to a specific deployment (for example, a Large deployment that utilizes three tiers) but not to another (a Small deployment with only one tier). The Service Deployment Definition allows you to specify values for parameters expected by any of the packages (for example, with the NSH scripts or AO Workflows). In the Service Deployment Definition, you must know what parameters the packages expect and the names of the parameters.
As a cloud administrator, you must define the following service deployment definition parameter, as shown in the figure, so that it is applicable on the deployment packages during multitier VM provisioning.
Service deployment parameter | Description |
---|---|
Cluster_Instance | The data type is numeric and the default value is 01. |
To define service postdeployment actions
After you have created the service definition, you must define the following postdeployment actions of the service blueprint for the Cisco HCS Provider (as shown in the figure below):
Post deployment action | Required | Description |
---|---|---|
CiscoHCS_IntegrationConfiguring CUBE SP | Yes | Define this action for executing the Configure CUBE SP job in BMC Network Automation. This job enables provisioning of the PUB and SUB application types. |
CiscoHCS_IntegrationPersist NAT SP | Yes | Define this action to enable NAT. |
To define the service deployment sequence
After you have created the service definition, you must define the deployment sequence in the service blueprint, as shown in the figure below: