Building service blueprints for OpenStack service
This topic provides the caveats and considerations you need to review when creating a service blueprint for OpenStack services. It also provides links to the applicable service blueprint documentation. This topic contains the following sections:
Roadmap for service blueprint documentation
The following table provides links to the applicable service blueprint documentation.
Topic | Description |
---|---|
Service blueprints overview | Provides an overview of the service blueprint blueprint workspace. |
Creating, copying, or editing a service blueprint | Describes how to add several of the various types of service blueprint objects, and how to define network connections between those objects. |
Considerations for creating a service blueprint for OpenStack Provider
Create service blueprints as described in Building service blueprints. The following table identifies the items to consider when creating a service blueprint for the OpenStack Provider.
Note
The following constructs do not apply to OpenStack:
- PaaS Resource
- Load balancer pools
- IP Endpoints/VLAN
Service blueprint construct | Notes specific to OpenStack |
---|---|
Service blueprint parameters | You have defined the following definition-level parameters so that they are applicable on the deployment packages during VM provisioning:
In this implementation of the OpenStack Provider, you cannot add new OS users after the VM has been provisioned. However, you can add users by using BMC Server Automation and you must add the following service blueprint definition parameter to enable addition of local users in a provisioned VM:
Note: For instructions, see Creating a BLPackage for adding local users in the OpenStack Provider.
|
Application | The VM must be assigned a security group that ensures TCP port 4750 is open in the VM. You must first create a BMC Server Automation Deploy Job or an application component template and ensure that the RSCD Agent is installed in a VM that was provisioned in the OpenStack Provider before installation. You can then enable a software installation as a part of an OpenStack service offering. (See the "To add and define applications in a service blueprint" section in Creating, copying, or editing a service blueprint.) See the OpenStack Virtual Machine Image Guide for information about creating snapshots and images. |
Server |
|
Networks | When you enable VM placement in single or multiple subnets for a Virtual Network, you must define single or multiple subnets for a Virtual Network in a service blueprint and tag them appropriately (as shown in the figure below). Note: You can allow software install using any of the public IPs (if multiple NICs exists for a VM) or the private IP of NIC 0 (if no public IPs are assigned). Private IP of NIC 0 is applicable only if there is a VPN connectivity between BSA and OpenStack. |
Where to go from here
Proceed to Managing the OpenStack service offerings.
Comments
Log in or register to comment.