Skip to Content
Information
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 custom cloud configurations for BMC Small RDS

These steps in this topic have been validated only for baby PODs with multiple NIC IDs (management and customer subnet). These are reference configuration steps for BMC Cloud Lifecycle Management version 4.0, and the steps are specific to BMC Software network infrastructure. Remember the details of the customer's infrastructure and make appropriate changes in the configuration steps.

 This topic contains the following information:

The uses cases were validated using dummy devices in BMC Network Automation, so make relevant configurations per the customer's network devices and create the relevant templates for baby or large PODs.

Warning

Note

This topic contains numerous sections and numerous steps. Make sure you read each section carefully as you perform the steps listed.

Configuring BMC Server Automation

The following steps describe how to custom configure BMC Server Automation. 

Adding a vCenter to BMC Server Automation

These steps show how to add a vCenter to BMC Server Automation into the Servers > VC folder (as a server group) and then add it to the Property Dictionary view. 

Warning

Note

Install and license the RSCD agent for VC on the target vCenter.

Adding a vCenter to BMC Server Automation to the Property Dictionary View

  1. Log on the BMC Server Automation Console.
  2. (optional) Select Server > Server Group (for example, VC), and then click Finish to create the VC folder.
    VCServerGroup.jpg 
  3. Right-click the VC server group, and then select Add Server. 
    AddServer.jpg 
  4. Enter the vCenter details to add the vCenter. 
    AddvCenterServer.jpg 
  5. Click Finish. 
  6. Select Configuration > Property Dictionary View to add the Virtual Entity Connection details for the VC and specify the required information.
    PropertyDictionaryView.jpg 
  7. Add Connection information and parameter values.
    For more information, see Adding-the-vCenter-server-to-BMC-Server-Automation. 
  8. Add and verify the Virtualization information.
    Virtualization.jpg

Distributing configuration objects for the vCenter

  1. In the BMC Server Automation Console, create a Jobs folder if it does not already exist.
  2. Right-click the Jobs folder and select New > Administration Task > Distribute Configuration Objects. 
    For more information, see Creating or modifying Distribute Configuration Objects Jobs in the BMC Server Automation documentation portal.
    DistributeConfigObjectsJob.jpg 
  3. Execute the job and verify the results.
  4. Verify that the vCenter (under Servers) is now recognized as a Virtual Center.
  5. Right-click the vCenter (under Servers) and select Distribute Configuration Objects to create a job that distributes the Virtual Center Configuration Object.
    DistributeConfigObjects.jpg      

Creating a Virtual Guest Package (VGP) to test the VM Deployment to VC

  1. In the Depot, verify that the CSM_Virtual_Guest_Packages folder is available (if it does not exist, then create it).
  2. Right-click the CSM_Virtual_Guest_Packages folder, and then select New > Virtual Guest Package > VMware. 
    NewVGP.jpg 
  3. Using the wizard, create a new VGP.
    VGPwizard.jpg 
  4. Create the Virtual Guest Package from the template. 

Creating a System Package

System packages are necessary to create blueprints.

  1. In the Depot, verify that the CSM_OS_Packages folder is available (if it does not exist, then create it).
  2. Select Depot > CSM_OS_Packages > New > System Package and create a new system package.
    NewSystemPackage.jpg 

Publishing the Product Catalog

  1. Verify the setup connection information by selecting Configuration > Atrium Integration > Configuration.
  2. Test the connection.
    Under the Jobs folder, the CSM_Publish_Product_Catalog should be available with the Publish_Product_Catalog job listed.
  3. Execute the Publish_Product_Catalog_job and verify the results.
    It should create the VGP created in BMC Server Automation into the BMC Atrium CMDB. The CMDB connection should be set up automatically by the install planner.

Configuring BMC Network Automation

Use the following steps to manually configure BMC Network Automation.

Before you begin

Make sure that the BMC CMDB is integrated with BMC Network Automation. Select Admin > System Parameters to verify that you have enabled CMDB integration.
BNACMDBintegraton.png 

Creating the BMC Network Automation Device Security Profile (DSP) for the vCenter

  1. Log on to the BMC Network Automation console (typically sysadmin/sysadmin). 
    For example:
    https://bnaServer:11443/bca-networks  
  2. Select Admin > Network Admin > Device Security Profile > Add.
    DeviceSecurityProfile.png 
  3. Set the Username and Password to the vCenter username and password for both the Login and Privileged Login.

Creating the Switch Device

  1. From the BMC Network Automation console, select Network > Spans > Devices > Add.
    BNAnetworkdevice.png 

  2. Enter the parameters to create the switch device.
    For more information, see Adding a device.

    Field

    Parameter

    Name

    Host name, IPv4 or IPv6 address, or URL of the device's primary interface. When the access mode is web service, this field must contain the URL for accessing the host or server that is providing the web services interface (vSwitch0@<ESXname>@https://<VCName>). For example, a fully-qualified URL for a vSwitch might be:
    vSwitch0@https://ServerName:443/sdk

    Device Type

    VMware VMware vSwitch

    Hostname/IP/URL

    Use the following format:
    switchVCweburl For example:
    @pe-pun-cld-qa06.bmc.com@    https://pun-cdl-vc11.labs.bmc.com 

    Device Agent

    Local

    Access Mode

    WebService

    File Transfer Mode

    Tunneled

    Device Security Profile

    Select the profile you previously created, for example, TestProfile.

     

     

  3. Click Save. 
    If you are successful, then the connection to the vCenter vSwitch is good.

Creating the Site in the Physical Location form

  1. Log on to the Enterprise-AR server with the Mid Tier as an AR System Administrator.
  2. Open the BMC.CORE:BMC_PhysicalLocation form and create a new request.
    BNASitePhysicalLocation.jpg 

  3. Enter the following parameters:

    Field

    Description

    Name

    Pod name

    DatasetId

    BMC.ASSET

    TokenId

    Same of Name

    StateOrProvince (Specifications tab)

    Name of state, for example, California or Pune.

    City (Specifications tab)

    Name of city, for example, San Jose or Austin.

    Company (Custom tab)

    Company or Tenant created

  4. Click Save. 

Creating the Baby Pod

Warning

Note

  • At this stage, the Baby Pod XML files are already imported into BMC Network Automation.
  • Before you start, the site must already be created on the Enterprise-AR server.
  1. From the BMC Network Automation console, select Network > Virtual Data Center > Pod Blueprints > Create Pod.
    PodBlueprints.png
  1. Under Pod Details, enter a name, and then click Next. 
    The site should be prepopulated from the menu drop-down. The CMDB must be already integrated with BMC Network Administration. 
    PodDetails2.png 

  2. Enter the parameters to create Access Switch 1, and then click Next. 
    Select the device that you created earlier. 
    AccessSwitch1.png
  1. Enter the DNS and NIC parameters, and then click Next. 
    DNCNIC.png 
  2. Enter the management addresses of the address pool, and then click Next. 
    AddressPoolMgtAddress.png 
  3. Enter the address range, and then click Next. 
    AddressRangeCustomer.png 
  4. Enter the VLAN pool of the customer, and then click Next. 
    VLANPoolCustomer.png 
  5. Enter the management VLAN pool, and then click Next.
    VLANPoolMgt.png 
  6. Enter the VLAN number for the Management VLAN, and then click Next. 
    MgtVLAN.png 
  7. Click Submit to create the pod.
    worddav999749854b76563d92503bedb9851719.png

Creating the VLan Port Group on the targeted ESX

Here you create the VLAN Port Group for Management-VLANNumber on the targeted ESX server, for example, Management. The Management VLan Port Group is the one mentioned during pod creation for Management, for example, 1521.

Finishing manual configuration

  1. Go to the CLM-PM VM.
  2. Open a command window and restart the OSGi service:
    /etc/init.d/bmccsm restart
  3. Check the /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/logs/csm.log file for any errors.

Configuring CLM Administration

Use the following steps to manually configure CLM Administration.

Creating resources

  1. Log on to the Mid Tier (for example, http://csm-mt:8080/arsys) with the Cloud Admin User (CloudAdmin/clmAdm1n)
  2. Open the BMC Cloud Lifecycle Management Administration Console.
  3. Select Workspaces > Resource > Pods.  
    OnboardPod.png 
  4. Onboard a pod:
    1. Select a BBNA provider.
    2. From the Pod list, select a Baby Pod.
    3. Click Onboard. 
      SelectBabyPod.png 
  5. Select the pod and click Import Network Container Blueprints.
    ImportNetworkBlueprintContainers.png
  6. Test the pod by selecting one or more Available Network Container Blueprints and then clicking Import.
    ImportNetworkBlueprintContainers2.png 
  7. Onboard the resources:
    1. On the Resource Management window, click Resources.
    2. Click Onboard Resource.
    3. Select the Pod.
    4. Select the Resource Type.
    5. Select the Provider Name.
    6. Select one ore more available resources, and then click Add.
    7. Click Onboard. 
      OnboardResources.png 

 

Creating compute pools

Use the following steps to create a Compute Pool.

  1. On the Resource Management window, click Compute Pools.
  2. Click Create Compute Pool.

  3. Set the following attributes:

    Attribute

    Entry

    Name

    Enter any name.

    Pod

    Select the pod you previously created.

    Resource type

    Virtual Cluster

    Provider Type

    BBSA

    Vendor

    VMWare

    Hardware Architecture

    X86

     

  4. Click Next.
    ComputePool.png 
  5. Select an available resource and then click Save. 
    ComputePool2.png 

Creating network containers

Use the following steps to create a network container.

  1. On the Resource Management window, click Network Containers.
  2. Click Create Network Container.

  3. Set the following attributes:

    Attribute

    Entry

    Name

    Enter any name.

    Provider

    BBNA

    Pod

    Select the pod you previously created.

    Container Blueprint

    Already populated

    NAT Address Pools

    Add optional NAT Address Pools

    Vendor

    VMWare

    Hardware Architecture

    X86

  4. Click Next.
    NetworkContainers2.png 
  5. Review the dynamic components and then click Next. 
    DynamicComponents.png 
  6. (optional) Add additional parameters.
  7. Click Submit.
  8. Select the Network Container you just added.
  9. Click Manage Pool Mappings.
    ManagePoolMappings.png 
  10. Select the Available Resource Pool that you just created and click Add.
    MapPool.png 
  11. Click Save. 

Mapping tenants to a network container

  1. Network->Network Containers
  2. On the Resource Management window, select the network container you just added.
  3. Click Manage Tenant Mappings.
    ManageTenantMapping.png 
  4. Select the Available Tenant and click Add.
    MapTenant.png 
  5. Click Save.

Creating service blueprints 

  1. In the Cloud Service Administration Console, select Service Designer.
  2. Click Create New and select Service Blueprint.
    NewServiceBlueprints.png 
  3. Click Server in the Blueprint Editor tab.
  4. Select the Hardware type, Cloud Platform, and Machine Name.
    HardwareType.png 
  5. From the Blueprint Editor, select Network, and then select New > NetworkType > Management.
    NetworkTypeMgt.png
  6. To add a Customer network, select New > NetworkType > Customer. 
    If the option is not present, then create the Customer Network tag under the NetworkType group. 
    NetworkTypeCustomer.png 
  7. Click Save, enter a blueprint name, and then click OK.
    SaveBP.png 
  8. Select Connect and then connect the compute resources to the network details.
    ConnectComputeResources.png
  1. To monitor service health data, select Definition > Properties.
  2. Select Enable Monitoring and Enable Monitoring Policy. Then click OK.
    EnableMonitoring.png 
  3. Select File > Save and Check In.

Creating entitlement packages and requestable services

  1. In the BMC Cloud Lifecycle Managemenbt Administration console, select Service Catalog > Entitlement Packages. 
    NewEntitlementPackage.png 
  2. Click the Entitlement Packages tab.
  3. Click Create Entitle Package.

  4. Enter the following information: 

     

    Field

    Description

    Name

    Enter a Name for the Package

    Company

    Select the company or keep as Global (for all companies)

    Package Group

    Enter a Package Group name

    Available Requestable Offerings (SRDs)

    Select an SRD and then click Add.

    PackageDetails.png 

  5. Click Save. 
  6. Click the Service Catalog tab.
  7. Click Create a new service and its default request. 
  8. Enter a Name for the service.
  9. On the General Information tab, enter a Name and Description for the Service Offering Information.
  10. Select Default Service Offering.
  11. Select a Service Blueprint and a Service Deployment Definition from the drop-down.
  1. Enter a Base Customer Price and a Base Deployment Cost.
    Keep the Instance and Month as selections.
    NewService.png 
  2. Click Save.
    Wait for few minutes. DSO takes some time to import the service offering from Cloud AR to Enterprise AR.
  3. Select the created Service Offering and click Edit a Service.

  4. Click Create the request definition and enter the following attributes:

    Field

    Description

    Title:

    Enter a title.

    Description:

    Enter a description.

    Start Date:

    Select a date.

    Change Policy:

    No Change Required

    Type:

    Compute

    Approval Type:

    None

    RequestDefinition.png

  5. Click Next.
  6. Select Cloud Services as the navigational category.
  7. Select the Service Request Definition Available Package and then click Add.
    This is the Entitlement Package created above.
    RequestDefinition2.png 
  8. Click Finish.
  9. Click Save to save the service.
  10. In the BMC Cloud Lifecycle Management Administration console, select Tenants to assign an Entitlement Package.
  11. Select a Tenant (Company) and then click Edit Tenant.
  12. Select the Available Entitlement Package and click Add.
    EditTenant.png 
  13. Click Save.
  14. In the BMC Cloud Lifecycle Management Administration console, select Service Governor.
  15. Click Network to define policies
  16. Select NetworkType as the Service Blueprint, and then click Save.
    SelectNetworks.png 
  17. To test the service, Select Service Instances in the BMC Cloud Lifecycle Management Administration console.
  18. Click New Service Request.
  19. Select the service that you created.

  20. Enter the details to request the new service:

    Field

    Description

    Instance Name Prefix

    Enter a prefix, for example, bmc10.

    Username

    Enter the username to add to the VM being created

    Password

    Enter the user password to add to the VM being created

    Confirm Password

    Repeat the password to make sure that you entered it correctly.

     

    SubmitRequest.png

  21. Click Next.
    The summary page appears.  
    SubmitRequest2.png 
  22. Click Submit.
  23. Log on to the vCenter console and enable the management VLAN with the name Management. 
    EnableVLAN.png 

Configuring Amazon EC2

The following section describes how to manually configure Amazon EC2.

To obtain your AMI ID

In this procedure, you log into the Amazon Web Services console to obtain the AMI ID that you will you use to create definitive media library (DML) in the Product Catalog.

  1. Log into the Amazon Web Services console with your AWS user credentials.
  2. From the Amazon EC2 Console Dashboard, select AMIs under the IMAGES folder in the navigation tree.
  3. In the Amazon Machine Images pane, filter for your customized AMIs by selecting Owned By Me in the Viewing drop-down box:

    ec2_custom_ami.png
  4. After noting the ID, you can exit the Amazon Web Services console.

To create your product catalog entry

  1. Access the enterprise BMC Remedy AR System server by using the Mid-Tier URL: http(s)://<mid-tier hostname or IP address>:<portNumber>/arsys.
  2. Log on to the Mid-Tier by using the user name appadmin without a password.
  3. Navigate to the Product Catalog > Product Catalog Console.
  4. Under General Functions, choose New Product/Suite.

    product_catalog_add_ami.png
  5. Under the Product Category section, click Create.

  6. Ensure that the following fields are completed with the specified entries. If any of the Product Categorization Tier fields are blank, you must manually add a corresponding tier value.

    Field

    Entry

    Product Type

    Software

    CI Type

    Virtual System Enabler

    Product Categorization Tier1

    Software Distribution. If the field is blank, manually enter Software Distribution.

    Product Categorization Tier2

    VM Template. If the field is blank, manually enter VM Template.

    Product Categorization Tier3

    Amazon. If the field is blank, manually enter Amazon.

    Product Name

    Valid AMI unique ID. This the AMI ID for which you will create a product catalog entry. In our example the ID is ami-50dd5160.

    Manufacturer

    Amazon. If Amazon is not listed, then click New to open the dialog box. Then enter the manufacturer's name and select its status. Click Save.

    Origin

    Select the origin of the entry, if it is not already the default. Generally, your AMIs will have a Custom origin, because they have RSCD agents installed on them.

    Status

    Set to Enabled.

    Suite Definition

    Indicate if the entry is to be used in a suite.

  7. Click Save.

To add the EC2 credential

ManageEC2.png

  1. In the Providers workspace, select Compute. 
  2. Select an AWS provider in the list of providers.
  3. Click Manage EC2 User Credentials ManageEC2UsrCredsBtn.gif.
     The Manage EC2 User Credentials dialog box is opened and ready for data input. On this dialog box, you specify a user name and the AWS account credentials needed to establish a secure connection to an Amazon Elastic Compute Cloud (EC2) provider instance.

  4. Complete the following fields:

    Field

    Description

    User Name

    User name assigned to this AWS account. The user name serves as an alias for a set of Amazon credentials.

    Access Key

    The Access Key ID from the Access Keys tab on the AWS Security Credentials page in your AWS account.

    Shared Secret

    The Secret Access Key associated with the Access Key. This key is just a long string of characters (and not a file) that you use to calculate the digital signature that you include in the request. The key is available from the Access Keys tab on the AWS Security Credentials page in your AWS account.

  5. Click Save and close the dialog box.

To onboard AWS as your logical data center

AWSLogicalDataCenter.png

  1. On the BMC Cloud Lifecycle Management Administration console, access the Resource Management > Network > Network Containers workspace.
  2. Select a Network Container (logical hosting environment).
  3. Click the Onboard Logical Data Center icon OnboardLogicalDataCenterIcon.gif to display the Onboard Logical Data Centers dialog box.
    Onboard_VPC2.gif
  4. Select the Amazon AWS provider from the Provider drop-down menu to display the list of available Logical Data Centers. Both VPCs and AZs are listed as Logical Data Centers.
  5. Select a Logical Data Center entry from the list of available entries, and click Add to add the Logical Data Center to the Resource Management > Network Containers workspace.
  6. Click Onboard.

To map tenants to the Logical Hosting Environment

  1. On the Resource Management > Network > Network Containers window, choose a Network Container, and click the Manage Tenant mappings icon ManageTenantMappingsIcon.gif to open the Network Container - Map Tenants dialog box.
    VPC_map_tenants.gif

  2. Choose a Tenant from the Available Tenants list. If necessary, enter search criteria in the Search text box and click the Search icon to retrieve matching tenants.
  3. After making your Tenant selection, click Add to move the entry to the Mapped Tenants list.
  4. To remove existing Tenants from the current Mapped Tenants list, select the Tenant, and click Remove to move the entry back to the Available Tenants list.
  5. Click Save.

If you are using the same tenant for Amazon and Template Base provision, then create a Governor Policy and tagging for the Network Container.

To create a service blueprint for AWS

Warning

Note

Make sure you have selected network type as "customer".

 The following table identifies the items to consider when creating a service blueprint for AWS.

Service blueprint construct
Available for AWS?
Notes specific to AWS
Service blueprint parameters
Yes
Add the BmcSshInstanceKey parameter to the service blueprint to enable a BMC Cloud Lifecycle Management end user to access a provisioned VM using a Key Pair. To add the parameter to the service blueprint:
  1. From the Service Designer workspace, select a service blueprint or create a new one.
  2. Select Service Properties > Parameters.
  3. In the Parameters table, click New.gif.
  4. For Name, add BmcSshInstanceKey.
  5. Enter a Label, such as AWS Key Pair.
  6. Optionally, add a short Description.
  7. Ensure that the Data Type is set to String.
  8. Optionally, enter a Default Value for the parameter.
  9. Select the User Entry Enabled option, and leave the other options blank.
  10. Click OK to add the parameter.
  11. Click OK to save the definition details.
The figure below provides an example of adding the parameter to a service blueprint definition.KeyPair_parameter.gifYou can also add the parameter to an individual server, if you want to use different Key Pairs for different servers. To do so, select a server item and click Parameters in the edit pane. For more information about adding parameters to a service blueprint, see Configuring-service-blueprint-parameters.
Application
Yes
Click Software Packages, and select from a list of available Amazon AMI files. Follow the instructions in To add and define applications in a service blueprint.
Server
Yes
  1. Add or select a server in the blueprint and expand the Compute Resources detail panel.
    Compute_resources.gif
  2. Under Cloud Platform, click the Add Icon plus_icon.gif.
  3. On the Cloud Platform panel, select Amazon for the Cloud Platform and then select the Amazon Machine Image as the deployable resource.
Cloud_platform.gif
Warning
NoteEnsure that the characteristics of the AMI you choose conforms to the instance types supported by BMC Cloud Lifecycle Management and to the instance types supported in your region. Otherwise, you could encounter errors in provisioning the instance. First generation Standard, Second generation Standard, High-Memory, and High-CPU instances are available in all Amazon EC2 regions. Other advanced types (such as High-Combination) could be region specific, so ensure that the instance type you select is supported in the target region.
In general, the AMI contains the OS, so you do not need to specify that option.For additional details, see To add and define server definitions in a service blueprint.
PaaS Resource
No
Not applicable for AWS.
Networks
Yes
On the Network Placement details panel, you must select both the Static option and the Assign NAT address option to enable Amazon Elastic IP addresses.See To add and define networks in a service blueprint.
Load balancer pools
Yes
IP End Points/VLAN
Yes

To create a Service Catalog entry for AWS

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
  2. In the Service Catalog, click Create a New Service servicecatalog_newservice_button.png. The New Service panel is displayed.
    New_service_AWS.gif
  3. Enter the service name.
  4. For Type, select a service type.
    • Business service - Shows the customer view of services, such as email or an online store.
    • Technical service - Supporting IT and infrastructure resources required to support business services that are not visible to customers, such as servers, applications, and network CIs.
  5. Enter a description of the service.
  6. Do one of the following:

    • To create the service offering, click Apply.
    • To create the service offering later, click Save to save your selections and close the window.

To create the service offering for AWS

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window, and click Service Catalog.
  2. From the Service Catalog, select the service you previously created and click the Edit icon edit_icon.gif.
  3. In the General Information tab, edit the default service offering:
    • Default Service Offering - Enable this option to make the selected service offering the default for the service. 
      Unless users select a different service offering, the default service offering is used. 
    • Name - A short, descriptive name for the service offering. 
    • Description - A more detailed description of the service offering. 
    • Service Blueprint  - Specify the software and hardware to associate with the service offering by selecting one of the service blueprints you created previously. 
    • Reference Definition - Specify the version of the selected service blueprint you want to use. 
    • Definition - Specify how to deploy the selected service blueprint. 
      From the list, select a service definition that is available for the chosen service blueprint.
  2. Add a Base Customer Price to define the amount charged to the customer for the service offering. 
    You can enter multiple customer prices per service. For more information, see Adding-a-customer-price-or-delivery-cost-to-an-option-service-or-request-action.
  3. Add a Base Deployment Cost to define the amount that it costs to provide the service offering. 
    You can enter one deployment cost per service. For more information, see Adding-a-customer-price-or-delivery-cost-to-an-option-service-or-request-action.
  4. Click Apply, which activates the Options tab.
  5. Click the Options tab to add options to the service offering. 
    You can only select options whose Type is set to Any request or Request Definition. The choices for the selected option appear in the Option Choice table.
  6. Click Apply to save the current settings. You can now create the requestable offering definition.

To submit the AWS service offering instance

  1. In the Service Instances workspace, access the Service Catalog tab, browse to view the available Cloud Services requests, and select one to request. In this example, we request a service called VPC Bronze 1T, which requests a single tier AWS VPC to be provisioned.
  2. Click Request Now to open the Submit Request dialog box, and enter your selections in the fields.
    Submit_request1.gif
  3. Click Next to view the summary.
    Submit_request2.gif
  4. Click Submit to initiate the service offering request. 

You can view the status of the service request under the Services subtab of the Activities tab. Also, go to your Amazon Account and verify that VM was created successfully.

Configuring AO Storage

Use the following steps to manually configure Atrium Orchestrator Storage.

Before you begin

  1. Make sure that the target VM has the iSCSI Initiator installed and running.
  2. Make sure that proper NSH scripts location is listed in the BMC-SA-MY Service Portal Module.
  3. Make sure that the NetApp Storage Services is already created.
  4. Log on to AO CDP.
    For example:
    http://clm-bao:28080/baocdp 

  5. Update the NetAppActor Adapter with the following details:

    <configs>
    <config name="Server1">
    <target><netapphostname></target>
    <user-name>administrator</user-name>
    <password><password></password>
    <protocol>http</protocol>
    <port>8088</port>
    </config>
    </configs>

     

To configure AO storage

  1. Log on to the Mid Tier (for example, http://csm-mt:8080/arsys) with the Cloud Admin User (CloudAdmin/clmAdm1n)
  2. Register the provider for storage:
    1. Select Workspaces > Providers > Storage. 
    2. Register a new provider. 
    3. Specify all the storage information in the storage provider, and then click Submit. 
      RegisterProvider.png 
  3. Select Workspaces > Service Catalog and open the Options Editor.
  4. Create a new option and specify all the required information.
    NewStorageOption.png 

  5. Create new option choices for Capacity for storage.

    Warning

    Note

    You can update the option choice value depending on your requirements for storage. 

    NewOptionChoice.png

  6. Create a new service catalog offering for the file system.
    1. Specify the Service and Service Offering Information.
    2. Click Apply to save the current settings. 
      NewService.png 
    3. Click the Options tab and add Capacity from the list of Available Options for the storage to attach.
      createoptions.png 
    4. Create a request definition for File System and select Storage-FileSystem as the Type. 
      newRequestDefintion.png 
  7. Create a new service catalog offering for the Block Device.
    1. Create a new Service and Service Offering.
    2. Click Apply to save the current settings. 
      BlockDevice.png 
    3. Click the Options tab and add Capacity from the list of Available Options.
      BlockDeviceOptions.png 
    4. Create a request definition and select Storage-BlockDevice as the Type. 
      SANRO.png 
  8. Select Workspaces > Providers > Storage to create a new storage mapping.
    1. Click Manage Storage Mappings.
      ManageStorageMappings.png 
    2. Create new storage mappings for File and Block.
    3. Select the service offering name from drop down list in Deployment Request.
    4. Specify remaining information in the panel. 
    5. Manually specify NetApp Adapter configuration name as Server1.
      the NetApp Storage Service should be already created volume on NetApp Server.
      StorageOfferingMapping.png 
    6. Create the mapping for Block storage.
      ManageStorageMappings2.png 
    7. Create the mapping for Block Device.
  9. Select Workspaces > Service Instances to create the service request for File System and Block Device.
    1. Click the Storage tab. 
    2. Click New Service Request for File System.
      The new request is displayed. 
      NewServiceRequest.png        
    3. Click New Service Request for Block Device.
      The new request is displayed.        In My Services > Storage, you can see the Block Devices and File System requests. 
    4. To attach storage to the running VM, right-click the VM and select Storage > Attach for Block Devices or File System.
      AttachStorage.png 
    5. To attach storage to the File System, enter the name and password.
      AttachStorage2.png 
    6. Verify request completed successfully from the Activities tab.

Configuring BSA PXE server

Use the following steps to manually configure a PXE server.

Warning

Note

You should be familiar with PXE configuration /bare metal provisioning.

PXE/TFTP server configuration

 

  1. Launch /opt/bmc/bladelogic/NSH/bin/blpxeconf. 

  2. On the Database tab, specify the Bladelogic Database Server, Port, User, and Password information.

    Warning

    Note

    If the BSA database is on Oracle RAC, then use the Advanced option and provide the same details used in BSA configuration.

    PXEserverconfiguration.png 

  3. Click the PXE Options tab, select eth type from the dropdown list (for example, eth1 or eth0), and then specify the proper domain information.
    PXEoptions.png 
  4. Click the TFTP Options tab, and specify the host IP Address and base directory location.
    TFTPOptions.png
     
  5. Keep the remaining default information, and then click OK. 
    PXEconfiguration.png 
  6. Click the Diagnostics tab, and then click Run Diagnostics. 
    The PXE configuration is completed successfully.
    RunDiagnostics.png 


Creating an image and a PXE datastore in BladeLogic

The following steps walk you through the steps to create an image and a PXE datastore in BMC Server Automation. 

  1. Create the WinPE image. 
    For more information, see 0 and later boot image files. 
  2. After you create the WinPE image, copy it to the /opt/bmc/bladelogic/tftp folder on the CLM-PXE VM.
    For more information, see Copying image files to the TFTP server (PXE).
  3. Log on to the BMC Server Automation Console using the csm-bsa host profile.
  4. In the Servers list, select Configuration > Property Dictionary View to add the PXE Host (csm-pxe). 
    PropDictionaryView.jpg
  5. Select Built-in Property Classes> Datastore > PXE Datastore.
    PXEDatastore.jpg
  6. To create a new instance of the PXE Datastore, select the Instances tab and then click the Add New Property button (as highlighted above).

  7. In the New Instance wizard, enter the following settings:NewInstance.jpg

     

    Field

    Description and setting

    Name

    Enter the CSM Datastore - PODNAME format. 

    FULL_PATH

    Specify the datastore installed path on the PXE host. For example:
    /opt/bmc/bladelogic/datastore 

    LOCATION

    Specify the IP address of the PXE host.

    USERNAME

    Administrator user name. The user name must have permission to access the SMB server.

    PASSWORD

    clmAdm1n password

     

    1. Enter the name. 
      It should be in the CSM Datastore - PODNAME format. For example:
      CSM Datastore - vw-pun-cdl-qa80.bmc.comPod
    2. For FULL_PATH, specify the datastore installed path on the PXE VM.
      For example:
      /opt/bmc/bladelogic/datastore 
    3. For Location, 
    4. For VIRTUAL_DIR, specify pxestore. 
  8. Click Next > Finish. 

Provisioning the configuration in BladeLogic

The following steps walk you through the steps to provision a configuration in BMC Server Automation. 

  1.  Select Configuration > Provisioning Configurations. 
  2. In the System Package Type tab, select the relative path for OS Image that you are planning to use for provision (for example, Windows 2008 Standard), and then edit it.
    SystemPackageType.jpg

  3. Enter the following settings: 

    Field

    Description and settings

    Installer Location

    Enter the OS image Folder location in the data store.

    RSCD Location

    Enter the RSCD msi file in the data store folder

    Initial Partition Size (MB)

    Modify size, if necessary. Default is 10000.

  4. Click OK. 
  5. Click the PXE tab and verify that the PXE setting match the PXE configuration information that you have already provided in PXE host.
    PXEsettings.jpg 
  6. Click the TFTP tab and verify the TFTP settings.
    TFTPsettings.jpg 
  7. Click the Image Files tab and enter WinPE image folder name in the Kernel Name.
    For example:
    WIN2K8X86
    The image is present in the tftp folder on the CLM-PXE VM. The image path name should be the Image File in the tftp location.
    ImageFiles.jpg 
  8. Click OK. 
  9. On the DHCP Server host, update the BladeLogic Server information.
    For more information, see Configuring DHCP. 
  10. Run DHCP from the Start menu by selecting Programs > Administrative Tools > DHCP.
  1. In Scope Options, do the following:
    1. Select 211 bl-server and set the value to the BladeLogic Application Server host IP address. 
    2. Select 212 bl-port and set the value to 0x23ab. 

Creating System Packages

For more information, see Creating a system package for Windows and Linux.

  1.  Launch the BMC Server Automation Console.
  2. In the Depot, create a folder named CSM_OS_Packages.
  3. Right-click the folder and select New > System package.
    NewSystemPackage.jpg 
  4. Enter the details for the new system package.
    NewSystemPackage2.jpg 
  5. Click Finish. 
  6. Select the new system package and then edit it.
  7. Click the Computer Settings tab and then specify the license setup information. 
    LicenseKey.jpg 
  8. Click the Post-Install Configuration tab and then specify the IP address (??APP_SERVER_IP??) and port (9131) in the Application server for BMI callback section. 
    IPaddress.jpg 
  9. Click the Local Properties tab and then specify the DATA_STORE settings.
    Enter the same DATA_STORE name as the Instance name in the Property Dictionary (for example, CSM Datastore – PODNAME). If the name is different, edit that property and change it. 
    DATA_STORE.jpg 
  10. Save the system package. 

 Creating VGPs

For more information, see Manually creating a Virtual Guest Package.

  1. From the Depot folder, right-click the CSM_Virtual_Guest_Packages folder where you want to add the VGP. 
  2. From the pop-up menu, select New > Virtual Guest Package and then the virtualization platform type for the package.
    NewVGP.jpg 
  3. Select VMware Virtual Machine as the type.
    NewVGP2.jpg
  4. Click Next and then click Finish.
  5. Edit the VGP created by entering the Name, storage location, and the appropriate OS Type and OS Version.
    NewVGP3.jpg 
  6. Click the VM Processor/Memory/Disk Settings tab and allocate the disk space.
    VGPdiskspace.jpg 
  7. Save the template.
  8. From the BMC Service Automation Console, run the Publish catalog job to add the System Package and VGP information into the Enterprise AR form.

 

Creating service blueprints for bare metal provisioning

For more information, see Building-service-blueprints.

  1. Log on to the BMC Cloud Lifecycle Management - Administration Console using CLM Admin credentials.
  2. Select Workspaces > Service Designer, and then select Create New > Service Blueprint.
  3. Select Compute Resources and enter the vmware details in the Cloud Platform section.
    NewServiceBlueprint.jpg
  1. For Installable Resource, enter the VGP created in BladeLogic.
  2. For Install Operating System, enter the OS Package created in BladeLogic,
    The remaining steps are similar to VM Template Provisioning.
  3. In Network Resources, specify the network label information.
  4. Click Save.
  5. Select Workspaces > Service Instances, and then submit the request for the bare metal request.

Where to go from here

Troubleshooting-BMC-RDS

 

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

BMC Cloud Lifecycle Management 4.0