VMware has just released LCM 1.1.
VMware vCenter Lifecycle Manager (LCM) 1.1 release enhances the performance, robustness, and scalability of LCM and resolves a number of known issues.
The LCM 1.1 release runs on VMware vCenter Orchestrator 4.0.1. To run LCM 1.1, you must install the version of Orchestrator (4.0.1 Build 4502) that accompanies the LCM 1.1 download. See the vCenter Lifecycle Manager 1.1 Installation and Configuration Guide for installation instructions.
Download now.
http://www.vmware.com/support/pubs/lcm_pubs.html
VMware vCenter Lifecycle Manager Release Notes
VMware vCenter Lifecycle Manager Installation and Configuration Guide
VMware vCenter Lifecycle Manager Administration Guide
VMware vCenter Lifecycle Manager User’s Guide
I’m kind of curious about the future of LCM. As far as I can tell its not widely adopted in favor of either homegrown solutions or just doing things the old fashioned way.
I like the concept of it though. Is this a precursor to something else?
In my experience, it is an interesting concept and somewhat showcases Orchestrator’s functionality, but it doesn’t have the teeth of third-party solutions as far as enforcement and post-deployment auditing of activities performed outside the LCM interface.
Even with vSphere, the lack of true integration with vCenter is disappointing and I’d look for that to be corrected — perhaps having the functionality rolled into the native vCenter interface at some point.
Well I think that a self-service portal should just be a website but the management/approvals should be pushed into some place in vCenter. You probably don’t want application owners, etc. logging in to vCenter (even with restricted roles.)
I’m guessing the idea behind LCM is to say “hey you can do this with orchestrator” in the hopes that enterprises will get a rough idea of what they need in the core product and roll their own using orchestrator? That would almost make sense if LCM wasn’t a charge for product.