With the SovLabs Lifecycle Components Toolkit (LCT) for vRealize Automation, administrators create provisioning "profiles" consisting of both script components and SovLabs modules which can each be aligned to specific lifecycles. Additionally, the profiles can be applied to blueprint machine components.
The term “Lifecycle” refers to the build phases that execute in the course of provisioning a machine (VM). Until now, there has been a prescribed order of execution for the various SovLabs modules. Additionally, interlacing custom script content required creating custom vRealize Orchestrator workflows and invoking them through custom Event Broker Subscriptions (EBS). As environments begin to scale, management of vRealize Automation content, configurations, blueprints and vRealize Orchestrator workflows begin to proliferate.