4.6.03 enhancements
This topic provides a list of the enhancements included in the releases that are available on BMC Communities or BMC Electronic Product Download (EPD) after the release of BMC Cloud Lifecycle Management version 4.6.00:
Version 4.6.03 enhancements
4.6.03 is available on the Customer Support website at http://www.bmc.com/support.
For additional download information, see, Downloading the installation files. But in general, perform the following steps:
- Create a directory in which to place the downloaded files.
- Go to http://www.bmc.com/support.
- Download the CLM_FeaturePack_4.6.03_Linux_Installer.tar.gz or CLM_FeaturePack_4.6.03_Windows_Installer.zip file.
- Extract the downloaded file.
- Open the ReadMe.txt files and review the prerequisites and instructions.
The following table outlines the features in this release and where you can find more information:
Category | Description |
---|---|
Providers (AWS, Azure, OpenStack) | Consistent mechanism for Azure instance type selection BMC Cloud Lifecycle Management supports new instance types that are available in Azure. They can be defined in the AzureInstanceTypeMetaData.json file. The CPU and Memory specifications are read as blueprint configuration parameters. The selection first filters the instance type based on the closest match (on the higher side) of memory and then CPU values. |
VPN-based private network deployments A cloud administrator can secure management traffic to external, public cloud-based resources, which might have public facing connectivity. Management traffic (application deployments, configuration updates, compliance measurement/remediation, patching, and so on) can be carried out over a VPN tunnel to a specific subnet in the VM network environment. With a VPN connection in place, the cloud administrator can manage each VM in an Azure Cloud Service individually through BMC Server Automation, instead of managing all the servers of a CloudService under one BMC Server Automation entry. | |
Support for Network Security Groups (NSGs) In the earlier versions, BMC Cloud Lifecycle Management only supported opening endpoints on the VM for Azure implementations. Starting with this release, a VM is assigned to a network security group in Azure. The network security group consists of rules that control inbound network traffic from the VM. These security rules require source and destination ports, address, protocol and access (allow/deny). The rules act as endpoint Access Control Lists (ACLs). | |
Compliance at Service level for Azure, Amazon, and Openstack providers Cloud administrators can configure compliance standards for Azure, Amazon Web Services (AWS), and OpenStack providers by enrolling the respective servers in BMC Server Automation, and then leveraging the existing BMC Server Automation jobs to accomplish the following:
End users and tenant administrators can only view the compliance status of services and servers. For details, see Monitoring BMC Cloud Lifecycle Management service compliance. | |
Support for Microsoft Azure Government When you set up a Microsoft Azure user account, you can now specify the Azure Government URL. A physical and logical network-isolated instance of Azure, operated by screened US persons, Azure Government is a cloud platform that has been specifically designed to meet the needs of US government agencies and their partners. | |
Support for OpenStack releases Starting with version 4.6.03, BMC Cloud Lifecycle Management has discontinued support for the Icehouse release and added support for the Liberty and Mitaka releases. | |
Networking | You can add newly added networks to existing network containers. For details, see Scaling an existing network pod. |
You can name load balancer pools through the General tab of the Configuration workspace. For details, see Configuration workspace overview and Creating custom logic for load balancer pools. | |
The performance of firewall rule management was enhanced. | |
BMC Cloud Lifecycle Management now supports the NULL VLAN (VxLAN), which allows you to create a NIC segment without any VLAN in BMC Network Automation to use VxLAN back port profile. For details, see Synchronizing network pods. | |
Tenant Management | Administrators can allow end users to transfer ownership and request services on behalf of another user. (Previously, only cloud and tenant administrators could do this.) For details, see Giving end users more control over services. |
Users can change the description of a service offering instance from the Edit Description action on the My Cloud Services console. Administrators can also change the description from the Administration Console. For details, see Managing cloud resources and Modifying the description of service offering instances in the legacy console. | |
SDK | To enable the cloud administrator to perform various operations by using SDK commands, this release includes the following changes:
|
API | The following APIs are newly added in this release: The following APIs are updated in this release:
|
Miscellaneous | Troubleshooting To enable tenant administrators and end users to view SOI progress details, a new parameter, |
Version 4.6.02 enhancement: BMC CLM ITSM Brownfield utility
With the BMC CLM ITSM Brownfield utility, you can synchronize ITSM Foundation data from the BMC Remedy ITSM server (also called Corporate ITSM AR server) to the BMC Cloud Lifecycle Management server (CLM AR server). The utility reads the objects related to ITSM Foundation data on the Corporate ITSM AR server. If the objects are already present, the data is merged (for extra fields) and overwritten (for fields already completed and read from ITSM server) or creates a new object. The utility creates a new object on the CLM AR server as if it is creating a new object in BMC Cloud Lifecycle Management server from the Tenant Management Console.
For details about downloading the artifacts from Communities, see, https://communities.bmc.com/docs/DOC-41578.
For details about how to use the utility, see Using the BMC CLM ITSM Brownfield utility.
Version 4.6.01 enhancement: Support for AWS CloudFormation
BMC Cloud Lifecycle Management can provision artifacts or resources for public cloud providers like Amazon Web Services (AWS) in an externally-declared fashion. This functionality extends BMC Cloud Lifecycle Management's capability by supporting offerings from various public cloud services that it does not directly support.
For details about downloading the artifacts from Communities, see https://communities.bmc.com/docs/DOC-40778.
For details about the documentation, see Provisioning for AWS CloudFormation.
Comments
Log in or register to comment.