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.

Version 4.1.00

This topic provides a list of the enhancements included in version 4.1.00 of the BMC Cloud Lifecycle Management solution. The topic also provides an overview of how to get started with the new version.

Version 4.1 provides the following enhancements:

Enhancements in version 4.1

The following sections provide an overview of the enhancements included in version 4.1.00 of the BMC Cloud Lifecycle Management solution.

What's New in version 4.1 video

The following video (7:42) presentation provides a high-level summary of the new features and enhancements in version 4.1 of BMC Cloud Lifecycle Management.

Use player to increase quality or switch to full screen | YouTube: http://youtu.be/O-gknScOfcU

Specifying a port group in Quick Start

When defining a network for an environment in Quick Start, you now select a specific port group. In earlier releases, you selected a VLAN, which allocated all the port groups associated with that VLAN. For more information on defining a network for an environment, see the Quick Start documentation for adding vCenter environments.

Selecting a service type when onboarding VMs with Quick Start

When using Quick Start to onboard existing VMs into BMC Cloud Lifecycle Management, you can now specify a service type. Making this choice (VMware or AWS) associates the resulting service offering instance (SOI) with the type of service that originally generated the VM.

Refreshing IP addresses

In earlier releases of BMC Cloud Lifecycle Management, if the IP address of a virtual machine changed, the IP address in BMC Cloud Lifecycle Management remained unchanged. Now, if the IP address of a VM changes due to any reason such as the IP renewal or DHCP lease expires, the change is reflected when you synchronize or refresh the service offering instance. For more information, see Refreshing-service-instances. 

Ability to specify a disk with a 0GB size

When adding additional disks to a service through a post-deployment action, you can now specify a disk size of 0GB for IBM LPARs. This enables you to create two adapter pairs (WWPN) for multipathing. 

Warning

You can specify 0GB size only for IBM LPAR service offerings. Do not specify 0GB for any other service offerings. 

Simplified disk names

Virtual machine disks will now have display names of Disk1, Disk2,.. Diskn according to the order in which those disks were provisioned. This provides a simpler and clearer view of the disks in the BMC Cloud Lifecycle Management user interface. The original name of a disk is available in the Description field in the CloudDB. You can sort the system disks by the Name field on the Server details screen.

If you want existing disks to benefit from the change in naming, run the DiskRenameUtility.zip after installation.  For more information, see  Implementing-simplified-disk-names.

Viewing quota allocated to a user from the My Cloud Services Console

As a cloud end user, you can now view the quota allocated to you from the BMC Cloud Lifecycle Management – My Cloud Services Console. You cannot change any quota details from the console. For more information about the quota visibility, see Viewing-quota.

Adding and associating cost centers

In this release of BMC Cloud Lifecycle Management, a cloud administrator can add cost centers to a tenant or create global cost centers, which can be used across tenants. Cost centers are used to identify which business units to charge costs to. A cloud administrator can create cost centers and associate them to cloud users. A tenant administrator can only associate cost centers to users. 

For more information about adding cost centers to tenants, see Working-with-cost-centers.

Support for assigning multiple tenants to a tenant administrator

You can now assign multiple tenants to a tenant administrator from BMC Cloud Lifecycle Management consoles and the multitenant administrator can perform almost all administration activities for the tenants. A cloud administrator or the cloud organization administrator (also known as the cloud tenant administrator) can assign multiple onboarded tenants to a cloud tenant administrator. A cloud tenant administrator can only assign those tenants to a new multitenant administrator, which are assigned to the tenant administrator. 

For more information about the capabilities and limitations of a tenant admin with multiple tenants, see Getting-started-by-user-role. For more information about assigning multiple tenants to a tenant administrator, see  Creating-and-managing-users-in-BMC-Cloud-Lifecycle-Management .

Enhanced support for Amazon Web Services

The following table describes the enhancements to Amazon Web Services (AWS) support included in this release.

Enhancement

Description

Auto scaling for VPCs

Ability to create auto scaling health checks to horizontally scale out or scale in a VPC, using the Service Health charts.Auto scaling is available for the following SOI types:

  • Gold level (service blueprints that contain at least one Network Path and possibly Load Balancing objects)
  • Silver level (service blueprints that contain Load Balancing objects)
  • Bronze level (any basic service blueprint)

Administrators can implement auto scale and remediation support for AWS, including the ability to:

  • Add server(s) while responding to over-utilization situations
  • Add CPU(s) or Memory while responding to over-utilization situations
  • Remove server(s) while responding to under-utilization situations
  • Remove CPU(s) or Memory while responding to under-utilization situations

See Enabling-auto-scaling-health-checks-for-AWS-VPCs for more information.

Onboard VMs

Ability to use Quick Start to onboard existing EC2 VMs in parity with on premise VMs using the new Service Type option. Selecting AWS as the service type associates the resulting SOI with the type of service that originally generated the VM.

See Onboarding-existing-VMs.

Networking enhancements

The following table describes the networking enhancements included in this release.

Enhancement

Description

Custom IPAM enhancements and DNS registration for static IPs

BMC Cloud Lifecycle Management 4.1.00 supports custom IPAM enhancements and out-of-the-box DNS registration and deregistration of static IP addresses for Linux, Windows, and Infoblox DNS servers.

For details, see Defining a DNS server in BMC Network Automation , Configuring-BMC-Atrium-Orchestrator-for-automatic-DNS-registration, and Implementing-integrated-DNS-DHCP-and-IP-address-Management in the BMC Network Automation online technical documentation.

New networking platform support

This release of BMC Cloud Lifecycle Management includes support for the Palo Alto PA-4050 firewall as a new platform for networking.

For details, see Configuring vendor-specific devices and Configuring Palo Alto Networks firewalls  .

Third-party IPAM support

BMC Cloud Lifecycle Management 4.1.00 i ntegrates with Alcatel-Lucent VitalQIP 7.3 as a third-party IP address management (IPAM) solution.

Improved pod and container management

The macro hidden-data from Confluence is no longer available.

Container enhancement: In the Create Network Container wizard and the Edit Network Container wizard, the administrator can now select a value from a list of available runtime parameters during container creation or enter a new runtime parameter value.

Virtualization enhancements

The following table describes the virtualization enhancements included in this release.

Enhancement

Description

Enhanced support for IBM LPARs

Support for IBM LPARs has been enhanced to provide the ability to:

  • Add or remove NPIV disks as Day 2 actions 
  • Reuse WWPN adapter pairs 
  • Use multi-pathing for NPIV disks

See Configuring-shared-memory-resources-and-NPIV for more information.

Notes:

  • To perform a remove disk operation for a Fibre Channel disk, the LPAR must be in the running state, otherwise the operation fails from VIO server.
  • To perform a local disk remove (rootvg), the LPAR must be in the powered off state.
  • To reuse a WWPN adapter for Day 2 operations, the deployment parameter must be passed with the disk option itself and not by creating two separate option choice (that is, it requires a single option choice that includes both disk and parameters). Otherwise, the reuse operation is skipped and a new adapter is created.

Enhanced platform support

For Hyper-V: Microsoft Windows 2012 R2 guests as a new supported hypervisor platform.

Windows 2012 R2 as a new supported BMC Cloud Lifecycle Management platform.

Software Development Kit enhancements

The following commands/arguments and APIs were added/updated in BMC Cloud Lifecycle Management 4.1.00.005:

Command

API

Update

New command

New command

Includes an optional usetemplatecredentials argument

Includes an optional force argument

Includes an optional force argument

The following commands/arguments and APIs were added/updated in BMC Cloud Lifecycle Management 4.1.00.004:

Command

API

Update

New command

Includes an optional disk argument

The following commands/arguments and APIs were added/updated in BMC Cloud Lifecycle Management 4.1.00.003:

Command

API

Update

New command

New command

Includes loadbalancer and environment arguments. lbpool-name, which is deprecated in this patch is renamed to lbpool.

All the commands

All corresponding APIs

Include an optional verbose argument applicable to all the SDK commands

The following commands and APIs were added in BMC Cloud Lifecycle Management 4.1.00.

Command

API

The following commands and APIs were updated in BMC Cloud Lifecycle Management 4.1.00.

Command

API

Update

The podname attribute is now optional.

The description attribute is now optional.

The providername attribute is now optional.

Added provider as a required attribute.

Added isonboard and account as optional attributes.

Added offeringname as a required attribute, replacing servicename.

Added the following as optional attributes:

  • options
  • params
  • decommissiondate

Added decommissiondate as an optional attribute.

Added actionname as a required attribute.

Added options as a required argument, replacing optionname and optionchoicename.

Added params as as optional attribute.

Azure Provider enhancements

The following table describes the Azure Provider enhancements included in this release.

Enhancement

Description

Support for Availability Set

Ability to add the virtual machines to an availability set  during provisioning and manage the availability of an application that uses multiple virtual machines.

See Viewing Availability Set of an Azure VM for more information.

Support for Load Balancer

Ability to add servers to load balancer pool.

See Managing-load-balancers-for-the-Azure-Provider for more information.

Support for Quota Management

Ability to allocate and view tenant and user quota usage for the Azure Provider users in BMC Cloud Lifecycle Management.

See Managing-tenant-and-user-quota-for-the-Azure-Provider for more information.

Support for Self Service

Ability to:

  • Request an Azure cloud service on behalf of another user.
  • Share and transfer ownership of an existing Azure cloud service.

See Managing-Azure-services-and-servers for more information.

OpenStack Provider enhancements

The following table describes the OpenStack Provider enhancements included in this release.

Enhancement

Description

Support for OpenStack components of Folsom, Grizzly, Havana, and Icehouse releases

Support for OpenStack components has been enhanced to Folsom, Grizzly, Havana, and Icehouse release components.

See Supported OpenStack Components for more information.

Support for VM placement on specific subnets

Ability to place VMs on specific subnets of an OpenStack Virtual Network.

See Managing the OpenStack Logical Data Centers for more information.

Support for Quota Management

Ability to allocate and view tenant and user quota usage for the OpenStack Provider users in BMC Cloud Lifecycle Management.

See Managing-tenant-and-user-quota-for-the-OpenStack-Provider for more information.

Support for installing software on a provisioned VM

Support for installing software has been enhanced for post-provisioning also.

See Managing-OpenStack-servers for more information.

Support for shutting down a provisioned VM

Ability to shutdown a provisioned VM in OpenStack.

See Managing-OpenStack-servers for more information.

Support for OpenStack public cloud (Cloudwatt)

Support for public cloud (Cloudwatt) services and resources.

See Version 4.1.1 of the OpenStack Provider for more information.

Support for Self Service

Ability to:

Support for allowing SSH Keypair during provisioning

Allows SSH Keypair to enable access to a VM provisioned in the OpenStack cloud (for example: Cloudwatt) using BMC Cloud Lifecycle Management.

See Version 4.1.1 of the OpenStack Provider for more information.

Product versions and compatibility

Note

BMC does not automatically certify newer versions of compatible products like VMWare vSphere, Oracle, SQL Server, Linux, and so on. However, BMC does support customers running newer versions of these products as long as backward-compatibility is guaranteed. For more information about compatible products, see the Compatibility Matrix, located in the BMC Cloud Lifecycle Management compatibility section of the Product Availability and Compatibility site at http://www.bmc.com/support.

When you upgrade to version 4.1, review the following table for the minimum version requirement for each product and the version each product is upgraded to.

Product

Minimum version required for upgrade

Version upgraded to in Cloud 4.x

Is Backward compatible?

BMC Remedy AR System Server and BMC Remedy Mid Tier

7.6.04 SP1

8.1.01

Yes

BMC Server Automation

8.1.02 Patch 001

8.5.01

Yes

BMC Network Automation

8.1.02

8.5.01

  • Yes for 3.x
  • No for 2.x

BMC Atrium Orchestrator

7.6.01.04

7.6.03

Yes

BMC Atrium Orchestrator Content

7.6.05

20.12.04

No

BMC Service Request Management

7.6.04 SP1

8.1.01

No

BMC Atrium Core Web Services

7.6.04 SP2

8.1.01

No

BMC Atrium Core

7.6.04 SP2

8.1.01

No

Atrium Integrator

Not applicable for 2.1.00.

8.1.01

  • Yes for 3.x
  • No for 2.x

PXE Server

8.1.02 Patch 001

8.5.01

No

Cloud Portal AR Extensions

2.1.00

4.1.00

No

Cloud Platform Manager

2.1.00

4.1.00

No

Cloud Database Extensions

2.1.00

4.1.00

No

 

Downloading the files

For download instructions, see Downloading-the-installation-files. 

Download all the files in the BMC Cloud Lifecycle Management 4.1.00 folder.

Installing the version as a fresh installation

  1. If you do not already have BMC Cloud Lifecycle Management installed in your environment, perform the procedures in the Installing section using the downloaded files.

  2. Ensure that the supported products are at the latest service pack or patch level listed in the following table. Review especially any required hotfixes. 

    Required products

    Version in 4.1 installer

    8.1.01

    8.1.01

    BMC Atrium Orchestrator Content 
    (cloud-specific content)

    4.1.00

    BMC Atrium Orchestrator Platform, including:

    • BMC Atrium Orchestrator – Configuration Distribution Peer
    • BMC Atrium Orchestrator – Configuration Distribution Peer (High Availability)

    7.6.03

    BMC Cloud Lifecycle Management, including:

    • Cloud Database Extensions
    • Cloud Platform Manager
    • Cloud Portal AR Extensions

    4.1.00

    BMC Network Automation, including:

    • (Optional) BMC Network Automation – Device Agent

    8.5.01

    8.1.01

    8.1.01

    8.1.01

    BMC Server Automation, including:

    • BMC Server Automation – Application Server and Console
    • BMC Server Automation – Virtual Center Agent (installed manually)
    • (Optional) BMC Server Automation – Advanced Repeater
    • (Optional) BMC Server Automation – PXE Server
    • (Optional) BMC Server Automation – File Server

    8.5.01

Upgrading to the new version

If you are upgrading from any previous version to version 4.1, you must review the items in the Preparing-for-upgrade topic to successfully complete the upgrade process. Ensure that the supported products are at the latest service pack or patch level listed in Component-BMC-product-service-pack-and-patch-levels. 

Note

Upgrading BMC Service Level Management in Enterprise-AR Primary and Secondary is not supported in 4.1. 

You do not need to perform the data migration steps while upgrading from version 3.1 to 3.1.01. You can upgrade your system by performing the steps listed in the Upgrading section. 

Click here to see the pre-upgrade tasks.

If you are using the existing BMC Cloud Lifecycle Management version 2.1.x, 3.0.x, or 3.1.x host to launch the version 4.1 installation program, then perform the following tasks prior to upgrading:

  1. Uninstall the existing planner version. To uninstall the existing planners, perform the following steps:
    • Microsoft Windows: Go to the <Planner Install Directory\UninstallBMCPlanner> folder and run the uninstall.bat file. Example: C:\Program Files\BMC Software\Planner\UninstallBMCPlanner.
    • Linux: Go to the <Planner Install Directory/UninstallBMCPlanner> folder and run the uninstall.sh file. Example:  /opt/bmc/Planner/UninstallBMCPlanner.
  2. Backup all the installer-related files from the following location:
    • Microsoft Windows: c:\windows\temp and %temp% folders
    • Linux: \tmp folder
  3. Delete all the uninstall files from both of the above locations.

BMC recommends that you restart the Microsoft Windows computer after performing the pre-upgrade tasks.  

Related topics

Known-and-corrected-issues

 

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