Support for integrating BMC Cloud Lifecycle Management with BMC Remedy OnDemand has been discontinued and will be removed fully in the next service pack release planned in 2018. BMC is no longer providing support for this integration.
This topic provides a list of the enhancements included in version 4.5.00 of the BMC Cloud Lifecycle Management solution. The topic also provides an overview of how to get started with the new version.
Enhancements in version 4.5
The following sections provide an overview of the enhancements included in version 4.5.00 of the BMC Cloud Lifecycle Management solution.
The following video (7:39) presentation provides a high-level summary of the new features and enhancements in version 4.5 of BMC Cloud Lifecycle Management.
New My Cloud Services Console
BMC Cloud Lifecycle Management 4.5 introduces a streamlined My Cloud Services console for end users. The new console provides easier access to the catalog of services available, makes options more intuitive to select, and allows multiple services to be requested at one time through the cart.
From the My Cloud Services Console, users can view details for their provisioned services and servers, and search for specific services and servers.
The new console also enables users to monitor the activities taken on their manageable resources. For example, users can see the activities taken for a service that has service monitoring rules enabled.
New CLM Self Checker Console
The CLM Self Checker monitors the health of your CLM environment and alerts you if any component is down or not reachable. This enables you to take recovery action proactively.
New integrated Value, Health, and License Capacity Dashboards
Cloud administrators can use new integrated dashboards to monitor the value, health, and license capacity of BMC Cloud Lifecycle Management and the services users have provisioned.
Prior to BMC Cloud Lifecycle Management 4.5, the Health and Value Dashboards were available as a separately installed utility: BMC Cloud Lifecycle Management Dashboards 1.0.
The Value dashboard provides information about servers and tenants in BMC Cloud Lifecycle Management, enabling you to monitor the usage of the servers you provision with BMC Cloud Lifecycle Management, as well as how many users and tenants are using those servers. This information helps you determine where your BMC Cloud Lifecycle Management environment is delivering the greatest value.
The Health Dashboard shows a summary view of the health of BMC Cloud Lifecycle Management component applications, as well as the number of failed provisioning requests.
The License Capacity dashboard provides information about the BMC Cloud Lifecycle Management licenses in your environment.
New integration with BMC MyIT
With the BMC MyIT with BMC Cloud Lifecycle Management integration, MyIT users can view and request the available virtual machine offerings. Users can create groups and add them to BMC Cloud Lifecycle Management offerings, which users can access in MyIT's Unified Catalog. After an offering is provisioned, users can view the provisioned services in the Service Health tab in the MyIT client. If a user clicks a service, a BMC Cloud Lifecycle Management window opens where the user can manage the service. Pending, Failed, and other status messages appear in the user's MyIT timeline. For more information, see the BMC MyIT documentation.
New CLM AWS SDK
The BMC Cloud Lifecycle Management Amazon Web Services software development kit (CLM AWS SDK) provides a normalized and homogenous interface to manage your Amazon Web Services cloud and other on-premises cloud providers such as VMware.
The CLM AWS SDK supports the following operations for the AWS cloud and the on-premises cloud provider (VMware):
- Provisioning an instance
- Describing an instance
- Describing an instance's status
- Describing an instance's attributes
- Rebooting an instance
- Starting an instance
- Stopping an instance
- Terminating an instance
The following table describes the installation enhancements included in this release.
|CLM Self-Check Monitor|
For Small, Medium, and Large deployments only, this optional feature lets you install the Self-Check Monitor as an integrated piece of the solution instead of installing it separately.
In addition, during the Platform Manager installation, you can enter Self-Check Monitor inputs.
Use the installer to install the Self Checker Monitor on a separate host so that it can effectively monitor CLM and alert you if any CLM components are down or not functioning properly. This feature is not available for Compact Deployment. You can also use a standalone installer to install CLM Self-Check Monitor. For more information, see Installing standalone CLM Self-Check Monitor.
|Cloud Portal Web Application|
The Cloud Portal Web Application is the new end user portal to access CLM for user operations. You can install the Cloud Portal Web Application (also known as the My Cloud Services Console) in the following ways:
For more information, see Installing standalone Cloud Portal Web Application.
|End-to-end process to install Linux/Oracle Compact Deployment documented||In version 4.5.00, the entire Red Hat Linux/Oracle process for Compact Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
|End-to-end process to install Linux/Oracle Small Deployment documented||In version 4.5.00, the entire Red Hat Linux/Oracle process for Small Deployment is thoroughly documented from start-to-finish, complete with screenshots.|
The following table describes the upgrade enhancements included in this release.
Only the following upgrade paths are supported in 4.5.00:
You cannot upgrade directly from 2.1.x to 4.5.00. If you are starting with 2.1.x, first upgrade your environment to 4.1, as described in Upgrade considerations for BMC Cloud Lifecycle Management version 2.1.x in the 4.1.00 documentation. Then upgrade your environment to 4.5.00.
|CLM Self-Check Monitor|
During the Platform Manager upgrade, you can enter Self-Check Monitor inputs. For more information, see To upgrade Cloud Platform Manager.
|Upgrading and replacing the Health Dashboard with the standalone Self-Check Monitor||You upgrade and replace the 1.0 Health Dashboard with the Self-Check Monitor. For more information, see Upgrading and replacing the 1.0 Health Dashboard with the standalone Self-Check Monitor.|
|My Cloud Service console|
During the Platform Manager upgrade, you can deploy the new My Cloud Service console as an integrated piece of the upgrade. By default, the option is No, because a separate Cloud Web Application node is available in the install planner. For more information, see To upgrade Cloud Platform Manager.
|Restore configuration parameter changes|
Install planner now restores user configurations during upgrades for the corresponding product configuration files:
|Product version displayed during integration|
Install planner now shows the product versions before and after upgrade.
When you perform data migration during an upgrade, you can track its progress. Data migration now generates a status report that includes remedial actions if there is a failure.
This feature is only available from:
For more information, see Migrating data for the cloud core components.
|BMC Server Automation upgrade changes|
When upgrading BMC Server Automation, the install planner includes the BL-Configurator installer for stateless configuration and database migration. BL-Configurator is run internally as part of the Application Server upgrade – no inputs are prompted by the install planner. Configurator, Migration, and Application Server are upgraded automatically before you start the post-install configuration stage. Manual intervention is no longer needed.
The following table describes the enhancements included in this release for enabling the cloud administrator perform better troubleshooting and maintenance activities for service offering instances.
|Configure and view automatic email notifications for service offering instance failures|
The cloud administrator can configure BMC Cloud Lifecycle Management to receive email notifications every time the service offering instance (SOI) provisioning fails. A link from the email notification directs a cloud administrator to the troubleshooting section on the console.
|Retrying service offering instances||From the automatic email notification, the cloud administrator is directed to the new end user console from where the cloud administrator can review the status of the SOI, view information about the stages where the SOI provisioning failed and after resolving the conflict, retry provisioning the SOI.|
|Download log files for service offering instance failures||If the service offering instance fails, a cloud administrator receives automatic proactive email notifications from BMC Cloud Lifecycle Management. The troubleshooting hyperlink in the email directs an administrator to the Activity Log on the BMC Cloud Lifecycle Management End User Console. From the console, you can download the collective log files to determine the reason where and why the SOI provisioning failed. See Downloading log files for service offering instance failures.|
|Revised error messages|
Error messages that appear on BMC Cloud Lifecycle Management are revised to include the detailed cause and suggested action for the cloud end user or administrator. These error messages provide detail reasons for failure and suggested troubleshooting steps.
See Revised error messages for more information.
Centralized way to stop and restart BMC Cloud Lifecycle Management component products
Prior to version 4.5, you needed to stop and restart BMC Cloud Lifecycle Management component products individually and manually. It was also necessary to perform these actions in a specific order if you needed to restart multiple components. For example, the Platform Manager should be started after BMC Remedy Action Request System Server. This process introduced the potential for error and lost productivity. To resolve this, BMC Cloud Lifecycle Management now includes a one-click restart for entire stack of components from a centralized location. For more information, see Monitoring BMC Cloud Lifecycle Management health with the CLM Self Checker.
In addition to setting up an on-premise platform-as-a-service (PaaS) environment with BMC Database Automation, you can now provision the following types of public cloud PaaS platforms:
- Databases (Amazon AWS RDS and Azure SQL Server)
- Application Containers (for example, Cloud Foundry and Heroku)
- Custom Containers
For more information, see PaaS provisioning.
The following table describes the BMC Cloud Lifecycle Management Developers API enhancements included in this release:
The following are some of the new classes added to Cloud API:
The Provider API now includes CustomContainer class, a new class.
|CLM Python SDK||A few new commands and APIs are added and updated to the Python SDK in this release.|
|CLM AWS SDK||A new set of methods that provide API access to the BMC Cloud Lifecycle Management stack and the Amazon Web Services (AWS) cloud are included in the AWS SDK.|
Simpler integration with BMC Change Management
You can now use the BMC Cloud Lifecycle Management UI to integrate with BMC Change Management. You can integrate with any of the following software:
- BMC Remedy ITSM
- BMC Remedy OnDemand
- BMC Remedyforce
- Other ITSM systems
For more information, see Integrating with BMC Change Management.
Enhanced support for Amazon Web Services
The following table describes the enhancements to Amazon Web Services (AWS) support included in this release.
|IPAM integration and DNS registration|
When you create a network blueprint for an AWS environment, you can enable external IPAM through integration with BMC Network Automation. IPAM allows you to consistently manage IP addressing of servers throughout your on-premises and AWS environments.
Additionally, when creating a network blueprint, you can add a domain name system or server (DNS) in your network. This can help you manage servers in off-premises cloud providers through BMC Server Automation, which stores IP addresses as a host name. BMC Server automation enrolls Amazon instances by its host name instead of IP addresses when provisioning.
For more information, see Enabling IPAM and DNS registration with AWS.
|Dynamic selection of EC2 instance types|
BMC Cloud Lifecycle Management supports new instance types that are available in Amazon AWS. They can be defined in the AWSInstanceTypeMetaData.json file. The selection is based on the closest match of memory and CPU values. The administrator must check the available instance types per AWS region. For more information, see Overview of support for Amazon Web Services.
|Reprovisioning a logical hosting environment||You can reprovision logical hosting environments. For more information, see Reprovisioning a VPC.|
The following table describes the networking enhancements included in this release.
Deploy VMs into different port groups that have the same VLAN ID
In earlier releases, customer networks could be created only by using VLANs that were created at a container-level. These VLANs were unusable for other networks.
Starting with this release, the cloud administrator can use a pod-level VLAN that is created in the BMC Network Automation pod to:
Control DNS registration on a per NIC basis from BMC Cloud Lifecycle Management
In earlier releases, by default, all the service offerings or NICs were registered into the DNS by setting a global property in BMC Network Automation. Starting with this release, the cloud administrator can control DNS registration on a per NIC basis by using Service Designer > NIC Configuration and Service Catalog > Options Editor.
|Add a pod-level management network to an existing pod||The cloud administrator can add more capacity to an existing pod-level management network by adding a chained address pool or creating a new management network in BMC Network Automation. The cloud administrator must then synchronize the pod and create a new container before the newly created network can be consumed in BMC Cloud Lifecycle Management.|
Software Development Kit enhancements
The following commands and APIs are added in BMC Cloud Lifecycle Management 4.5.00:
The following commands and APIs are changed in BMC Cloud Lifecycle Management 4.5.00:
|You can now offboard Azure environments.|
|You can now onboard Azure environments.|
|New arguments are added for bulk delete: |
Azure Provider enhancements
The following table describes the Azure Provider enhancements included in this release.
|Onboard existing Azure VMs|
You can bring existing Microsoft Azure Virtual Machines into BMC Cloud Lifecycle Management by onboarding them using any of the following procedures:
|Monitor server and tenant details of the Azure Provider|
You can now monitor server and tenant details of the Azure Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.
|Using external IP Address Management (IPAM) solution for an Azure Provider|
|Request and manage Azure services and servers using both legacy and new My Cloud Services Console|
You can now request and manage Azure services and servers using both legacy and new My Cloud Services Console. For detailed procedures see:
OpenStack Provider enhancements
The following table describes the OpenStack Provider enhancements included in this release.
|Monitor server and tenant details of the Openstack Provider|
You can now monitor server and tenant details of the OpenStack Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.
|Support for installing software using any of the public IPs (if multiple NICs exists) or the private IP of NIC 0 (if no public IPs are assigned).||You can now install software 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). See Building service blueprints for OpenStack service for details.|
|Request and manage OpenStack services and servers by using both legacy and new My Cloud Services Console|
You can now request and manage OpenStack services and servers by using both legacy and new My Cloud Services Console. For detailed procedures see:
eZDeploy utility enhancements
The eZDeploy utility includes the following enhancements:
- Export and import of an entire business service which, contains multiple blueprints. In the earlier releases, you could export and import only one blueprint along with its business service.
- Export and import a service offering only.
- Export and import a single or multiple software packages separately.
- Import and export of option categories.
- Validate the ZipKit version.
- Use an XML file for the answer file instead of a text file.
Product versions and compatibility
For detailed information about versions, service pack, and patch levels for the products installed in BMC Cloud Lifecycle Management 4.5.00, see Component BMC product service pack and patch levels.
Downloading the files
For download instructions, see Downloading the installation files.
Download all the files in the BMC Cloud Lifecycle Management 4.5.00 folder.
Installing the version as a fresh installation
- 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.
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.5 installer
BMC Atrium Core Web Registry 8.1.01 BMC Atrium Orchestrator Content
BMC Atrium Orchestrator Platform, including:
- BMC Atrium Orchestrator – Configuration Distribution Peer
- BMC Atrium Orchestrator – Configuration Distribution Peer (High Availability)
BMC Cloud Lifecycle Management, including:
- Cloud Database Extensions
- Cloud Platform Manager
- Cloud Portal AR Extensions
BMC Network Automation, including:
- (Optional) BMC Network Automation – Device Agent
8.6.00.001 BMC Remedy Action Request System 8.1.01 BMC Remedy Mid Tier 8.1.01 BMC Remedy Service Request Management 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
Upgrading to the new version
If you are upgrading from any previous version to version 4.5, you must review the items in the Preparing for upgrades 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.
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.
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.5 installation program, then perform the following tasks prior to upgrading:
- 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.
- Backup all the installer-related files from the following location:
- Microsoft Windows: c:\windows\temp and %temp% folders
- Linux: \tmp folder
- 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 BMC Communities blog entry
The following link provides supplemental information available from a blog entry in BMC Cloud Lifecycle Management Communities:
How to Video: New My Cloud Services Console - BMC CLM 4.5
This video demonstrates the features of new My Cloud Services Console, which is one of the major enhancement in BMC Cloud Lifecycle Management 4.5.
Log in or register to comment.