×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

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.
BMC Cloud Lifecycle Management 4.1 Configuring after installation

Set up the initial configuration

When you use Quick Start to create a connector, you are essentially performing these initial configuration steps.

You must perform the following configuration tasks to set up the base BMC Cloud Lifecycle Management environment:

Before you begin

Ensure that you have completed the tasks described in Verifying the BMC Cloud Lifecycle Management configuration.

To configure the BMC Cloud Lifecycle Management Administration Console

Use the Configuration workspace to set various options needed by BMC Cloud Lifecycle Management. Many of these options have default values, but you must verify that the values are appropriate for your environment before using them. Perform the following tasks to ensure that the console is configured to best suit your needs:

To create a physical location for a pod

Before you can create a pod, you must create a site in the Physical Location form on the BMC AR System Server – Cloud Portal and Database server.

  1. Create a direct access URL link to the Physical Location form using the mid-tier server and port.
    Specify a valid enterprise BMC Remedy AR System server (EAR Host in the accompanying syntax example) in the URL. The direct access link follows this format:
    http://<Mid-Tier Host>:<Mid-Tier Port>/arsys/forms/<EAR Host>/BMC.CORE:BMC_PhysicalLocation
  2. Enter values for the following (all fields are required unless otherwise noted):
    • Name (required)
    • Short Description (optional)
    • DatasetId (BMC.ASSET)
    • StateOrProvince (optional, located on the Specification tab)
    • City
    • Company (optional, located on the Custom tab)
    • Description
  3. Click Save.

To configure SSL for the Linux Platform Manager

If you have installed the Platform Manager on Linux, complete the following steps to configure SSL for Linux Platform Manager.

  1. Download OpenSSL and unpack the tar files.

    1. Download OpenSSL.
      See this website to obtain a tar file for OpenSSL.
    2. Copy the installation package to the location where you want to install OpenSSL, and run the following command to unpack the tar file:
      tar -xf openssl-0.9.8c.tar.gz
    3. Navigate to the directory where OpenSSL is installed and create the following directories with read, write, and execute permissions:
      • demoCA
      • demoCA/certs
      • demoCA/crl
      • demoCA/newcerts
      • demoCA/private
    4. Run the following commands to copy files between directories:
      cp apps/demoCA/index.txt demoCA/index.txt
      cp apps/demoCA/serial demoCA/serial

    5. In the /etc/pki/tls/openssl.cnf file, edit the CA_default section so it identifies the location of /demodirectory.

      [ CA_default ]
dir      = <openssl_install_dir>/demoCA       # Where everything is kept

  2. Generate a CA certificate.

    1. Enter the following command:
      openssl req -new -x509 -days 365 -keyout cakey.pem -out cacert.pem
    2. When prompted, enter a pass phrase.
    3. When prompted, repeat the pass phrase to confirm your entry.
    4. When prompted, provide the requested information or enter a dot to leave the field blank.
    5. When prompted for a common name, enter the host name or IP address of the Linux Platform Manager host.
      OpenSSL generates a cakey.pem and a cacert.pem file in the same directory where you have installed OpenSSL.

  3. Generate an SSL certificate request.

    1. Enter the following command:
      openssl req -new -nodes -out req.pem -keyout reqkey.pem
    2. When prompted, enter a pass phrase.
    3. When prompted, repeat the pass phrase to confirm your entry.
    4. When prompted for additional information, provide the requested information or enter a dot to leave the field blank.
    5. When prompted for a common name, enter the host name or IP address of the Linux Platform Manager host.

  4. Generate a signed SSL certificate.

    1. From the directory where OpenSSL is installed, run the following commands to copy files between directories:
      cp cakey.pem openssl-0.9.8c/apps/demoCA/private/.
      cp cacert.pem openssl-0.9.8c/apps/demoCA/private/.
    2. Enter the following command:
      openssl ca -out cert.pem -infiles req.pem
    3. When prompted, enter a pass phrase.
      If you have installed the Platform Manager on Linux, complete the following steps to configure SSL for Linux Platform Manager.
  5. When you configure Platform Manager to run on SSL, you must also import the certificate on the enterprise AR Server host so that the CloudPortal Plugin can communicate to the Platform Manager. You must import the root certificate into the CA certificates present in the Java/security folder, as the Java which is being utilized by Cloud Portal.

To configure the virtualization connections in BMC Server Automation

BMC Cloud Lifecycle Management uses BMC Server Automation for provisioning. To be able to provision virtual machines (VMs) in a specific virtualization environment (for example, VMware vSphere) you must set up the virtualization connections in BMC Server Automation.

The following topics provide instructions for adding the connections in BMC Server Automation for specific virtualization environments:

To ensure access to Quick Start


Quick Start is a web application that runs in its own framework. The Quick Start server runs on the same server where you installed Cloud Platform Manager.

After installing BMC Cloud Lifecycle Managment, you can perform procedures to ensure access to Quick Start.

  1. Log on to the Enterprise AR (EAR) server using the BMC Remedy User tool.
  2. Search for a form named CMF:PluginConfiguration.
  3. When you find the form, add a field named QuickStart URL.
  4. Set the value of the field to the fully qualified URL for the Quick Start server. For example, in the following graphic, the field is set to http://pcsm-sqa-r5v11.bmc.com:9000.

Assigning a different port number for Quick Start

Some installations may not want to use the default value of 9000 for the Quick Start port number.

  1. Enter a port number in the fully qualified URL for the Quick Start server, as described in the procedure above.
  2. On the server where you installed the Cloud Platform Manager, modify the application.conf file.
    In a typical installation on Windows, you can find this file in the following directory:

    C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\QuickStart\conf
  3. In the application.conf file, uncomment line 33 by removing the hash sign. By default the line reads:
    # http.port=9000.
  4. On the same line, set the port number to the number you assigned to the Quick Start server in the first step. For example, the line might read as follows:

    http.port=9075

To create network pod blueprints

Pods are built from pod blueprints, which define the pod architecture and include a definition of the physical pod topology. Pod blueprints are created by modifying an XML document and then importing it into BMC Network Automation. You then create the pod in BMC Network Automation by specifying the imported pod blueprint. After you create the pod, you onboard the pod into BMC Cloud Lifecycle Management.

To create network pods

Note

Prior to creating a network pod, you must first import the devices into BMC Network Automation and set up authentication profiles. See the following BMC Network Automation online technical documentation topics for more information:

A pod is the base on which logical networks are created in the cloud. A pod is created on a group of co-located network hardware, such as routers, firewalls, and load balancers, that segregates cloud networks from other pods and non-cloud networks.
Pods are created in BMC Network Automation using pod blueprints, which define the pod architecture and include a definition of the physical pod topology. After a pod is created, you can then onboard the pod into BMC Cloud Lifecycle Management.

To onboard network pods

You must onboard one or more network pods to make BMC Cloud Lifecycle Management aware of the network environment.

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  2. Under Quick Links at left, click Pods under the General section.
  3. Click the Onboard Pod icon . The Onboard Pod dialog box is displayed.
     
  4. Click the Provider Name menu button to select the resource provider instance for the pod. The default network resource provider is listed as BBNA for BMC Network Automation.
  5. Select the pods that you want to onboard.
  6. Click Onboard to onboard the selected pods and close the dialog box.

To create and import network container blueprints in BMC Network Automation

Network container blueprints are XML files that define the settings used when creating a network container. To create a new network container blueprint you copy and modify one of the templates that are installed with BMC Network Automation and then importing it into BMC Network Automation. After the blueprint is available in BMC Newtork Automation, you use the BMC Cloud Lifecycle Management console to import the blueprint into BMC Cloud Lifecycle Management.

Importing network container blueprints in BMC Cloud Lifecycle Management

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  2. Under Quick Links on the left, click Pods under the General section.
  3. Click the Import Network Container Blueprints icon .
    The Import Network Container Blueprints dialog box is displayed. The dialog shows the Pod name, the version number (if the pod has been updated), and a description (if available).
     
  4. Select the network container blueprints that you want to import.
  5. Click Import to onboard the selected blueprints and close the dialog box.

Where to go next

Configure environments 

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.

Last modified by Deepa Bhat on Feb 16, 2015
configuration

Comments

Log in or register to comment.

Perform preliminary tasks
Configure environments
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.