Creating OpenStack 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, 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, specify a name and description for the resource set.
- From the list of available components, add the components to include with this resource set.
In the Compute Resources tab, specify the compute attributes that are required for this resource set.
- In the Network Resources tab, 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).
- Select one of the Network Selection Method:
- Use Network Policies: Select Use Network Policies.
- Use Label: Specify private or public.
IP Address: Select Dynamic if the IP needs to be selected dynamically while provisioning the virtual machine (VM). Select Static if the user needs to select the IP for VM provisioning.

- Click OK to close the dialog box.
- Click Save to commit the blueprint and all your changes.
To define service deployment parameters
After you have created the service definition you are ready to define service deployment parameters for the OpenStack Provider.

As a cloud administrator, you need to define the following service deployment parameters so that they are applicable on the deployment packages during multi-tier VM provisioning.
Service Deployment Parameter | Example | Description |
|---|---|---|
BmcSecurityGroups |
| Enables an OpenStack instance to be placed within a security group (firewall). This security group allows RSCD agent traffic through port 4750 and remote access through an SSH or an RDP port. All comma-separated values should match the security group IDs that you specified in the Access & Security Console of the OpenStack eCloud. |
UNIX_USER |
| Enables user provisioning. The value name must exactly match the key user name you specified in BMC BladeLogic Server Automation. |
UNIX_USER_PASSWORD |
| Enables user provisioning. The value name must exactly match the corresponding password name for the key user name you specified in BMC BladeLogic Server Automation. |


