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.

Supported target platforms for provisioning

This version of BMC Cloud Lifecycle Management supports the following platforms, all of which have been certified by BMC. For other platform versions, contact BMC Customer Support.

Supported operating systems for provisioning

OS platformSupported version

VMware
vCenter
6.x

VMware
vCenter
5.x

Hyper-V
SCVMM
2012 R2

Citrix
Xen
6.x
IBM
LPAR

Physical
server
support

Red Hat Linux5.x 32-bit
YesYesNoNoN/ANo
5.x 64-bitYesYesYesNoN/ANo
6.x 32-bitYesYesNoNoN/ANo
6.0 64-bitYesYesYesYesN/AYes
6.5 64-bitYesYesNoNoN/ANo
7.x  64-bit (template based) with VC/ESX 5.5 update 2YesYes

Only RHEL 7.1
GEN2 template

NoN/ANo

8.x  64-bit (template based) with VC/ESX 6.0, 6.5, 6.7

Supported only with TrueSight Server Automation 20.02.

YesNoYesNoN/ANo
Microsoft Windows2019 64-bitYesYesNoNoNoNo
2016 64-bitYesYesNoNoNoNo
2008 32-bit and 64-bitYesYesNoNoN/ANo
2008 R2 64-bitYesYesYesYesN/AYes
2012 64-bit
YesYesYesYesN/AYes
2012 R2 64-bitYesYesYesYesN/AYes
IBM
AIX 6.x LPAR pSeries
N/A N/AN/AN/AYesN/A
AIX 7.x LPAR pSeries
N/A N/AN/AN/AYesN/A
SUSE Linux Enterprise Server11, 64-bit on VMwareYesYesNoNoN/AYes
Oracle Enterprise Linux (OEL)6.0 64-bit on VMware
YesYesNoNoN/AYes
CentOS

5.6 (This support requires that you set the OS Name in to BMC Server AutomationLinux)

The following BMC Communities video describes how to provision a virtual machine that uses a non-compatible Community Enterprise Operating System (CentOS) image. This involves changing the template on the vCenter so that the operating system is recognized.

Provisioning a VM Using a Non-Compatible CentOS Image (2:38): https://youtu.be/GykEQWpMbKU

YesYesNoNoN/ANo
ESX5.0 N/A N/AN/AN/AN/AYes

1 BMC Cloud Lifecycle Management 4.6.07.001 supports Windows Server 2019 64-bit provisioning for VMware with TrueSight Server Automation 8.9.04.

Note

If you have VMware vSphere Platform integrated with BMC Cloud Lifecycle Management, and you plan to migrate to VMware vCenter Server Appliance (VCSA), contact BMC Support to obtain the latest information on supported migration paths.

Switching from a Windows-based vCenter to a vCenter Server Appliance alters certain internal identifiers that disrupt the ability BMC Cloud Lifecycle Management to manage existing workloads and provision new workloads on that vCenter instance.

BMC Cloud Lifecycle Management 4.6.05 supports Windows Server 2016 64-bit provisioning for VMware with BMC Server Automation 8.9. The following are the known issues with this type of provisioning:

  • On the End User Portal, under the Operating System panel, the end user sees Windows Server 2008 instead of Windows Server 2016.
  • The Storage File system attached to the VM is not shown in the mapped drive list under My Computer. However, you can map it manually from the VM.

Back to top

Supported virtualization platforms

OS platformSupported version
Docker18.05, 8.1
Citrix XenServer5.6, 6.0.2
VMware vSphere

  • VMware vCenter Server Appliance 6.5

Note: VMware vCenter 6.5 is certified with BMC Server Automation 8.9.02.

  • VMware vSphere 6.5
Note that only existing functionality prior to version 6.5 is supported. New functionality in version 6.5 is not supported.
  • VMware vSphere 6.0 (Requires BMC Network Automation 8.7.00 HF#31 (000100716))

  • VMware vSphere 4.x, 5.x (Windows only)
VMware vCloud Director1.5, 5.1, and 5.5, 9.1
VMware ESXi
  • 6.7
  • 6.5
  • 6.0
  • 5.5
  • 5.1

Note: 6.5 is valid only if you are using TrueSight Server Automation 8.9.03 and later.

VMware ESX4.0
IBM pSeries6, 7
Microsoft Hyper-V
  • 2019
  • 2016
  • 2012 R2 System Center Virtual Machine Manager (SCVMM)
  • 2012 R2
(See Support for Microsoft Hyper-V environments for more information.)


VMware vCenter Server Appliance


  • 6.7
  • 6.0



Note

If you are using VC Appliance, enroll it in BMC Server Automation with AMO. (For more information, see Adding+and+configuring+a+vCenter+AMO in the BMC Server Automation documentation.)

On the AMO server, set the assetImpl_proxyCapable parameter to true in the AssetImplConfig.xml file, which is located in C:\Program Files\BMC Software\BladeLogic\RSCD\daal\Implementation\BMC_VMware_VirtualInfrastructureManager_win64\win64.


Back to top

Supported third-party cloud platforms

OS platformSupported version
Amazon Web Services

EC2, VPC

BMC Cloud Lifecycle Management uses the Amazon Web Services Java SDK 1.10.2. See the Amazon Web Services online technical documentation for more information on using the SDKs.

OpenStackSee Supported OpenStack Components for details.
AzureMicrosoft Windows Azure Service Management REST API Version 2014-02-01

Back to top

Supported storage provisioning platform

OS platformSupported version
NetApp OnCommand Unified Manager Core (previously known as NetApp DataFabric Manager)4.x, 5.x, 7.x

Back to top

Related topics

Component BMC product service pack and patch levels

Was this page helpful? Yes No Submitting... Thank you

Comments