BMC Cloud Lifecycle Management Reviews

Our use cases are related to IaaS and PaaS solutions. It's primarily used by DevOps, they use the PaaS solution to implement IBM WebSphere and they want to use the interface for issuing the deployment. They use the CLM platform to implement their DevOps process. CLM is only a part of the project, we have also used Orchestrator and Remedy for workflow process in terms of deployment and release.

We had this project a year ago. My colleagues are on the customer-side to implement new use cases. They only do the maintenance of the infrastructure and implement a process for DevOps. We have stopped the cloud platform at the moment because of BMC, they don't invest anymore on CLM platforms. The customer has asked for a new platform. 

CLM has a multi-cloud portal because they have the resources to implement in various environments in various ports. It could be used for when you design a blueprint in a cloud environment. Other solutions don't have the capacity to implement a blueprint based on resources that could be run in Azure or in AWS. It's not the same, and it isn't implemented in the same way.

I need to implement a solution, for example, on a server on a LAN. It doesn't matter if it runs on Azure, or in AWS, or in Google, or in my site. And this is a major benefit that CLM has. I think that is the most valuable aspect of this solution.  

Implementing a private cloud in the client environment, which is very secured and managed in-house using the cloud suite along with capabilities, like BMC Capacity Optimization, BMC Database Automation, and Bladelogic Server Automation suite, to manage and use effectively.

Total build time has been reduced from four weeks to one week, then later to 24 hours.

• Threat remediation: Combine with SecOps to link vulnerabilities to identified patches and create a remediation plan. 
• Compliance: Integrates role-based access control with pre-configured policies for CIS, DISA, HIPAA, PCI, SOX, NIST, and SCAP documentation and remediation.
• Provisioning: Supports unattended installs and image-based, script-based, or template-based provisioning.
• Configuration: Consistently manage change and configuration activities across a broad range of server environments with one tool.
• Reporting: Assesses change impact or completes an audit using multiple dashboard views.
• Patching: Supports and follows Maintenance Window Guidelines to ensure timely delivery of patches.

Automated provisioning from an end user. With CLM, you can tie together your public and private cloud infrastructure into a "single pane of glass".

• By allowing end users to request their own services, the request process for systems is much quicker and more accurate. 
• Taking the human aspect out of the provisioning process can close gaps in security.

Server provisioning with full automation.

We have many regions where more than 10000 servers are deployed. So it helps in patching and hardening of servers.

It's helped us with our automation.

It needs to be more script-based; as of now, there are a few features that still need to be manually uploaded.