VMware Cloud Community
evil242
Enthusiast
Enthusiast

Best Practices for VMware Aria Suite Lifecycle

We’ve really dove into using VMware Aria Suite Lifecycle, but find we need to understand Best Practices and Recommended deployments a little further.

Lifecycle appears to be very capable to handle multiple environments including Production, Horizon/VDI, and TestDev.  We currently have two additional environments deployed in the single LCM:

LCM-EnvironmentList.png

Where we have Automation/Orchestrator in both Production and TestDev. 

But because it only allows a single deployment of vIDM as “globalenvironment”, we have a question about being able to run a vDIM upgrade through and testing against our TestDev environments before upgrading vIDM in Production. 

I am contemplating deploying a second Lifecycle Manager as TestDev with TestDev globalenvironment vIDM.  Deleting the TestDev environment from production, and adding to the new TestDev LCM.  Then migrating other TestDev environments to use the new TestDev vIDM (NSX, vRA, etc).  Probably deploy Operations and Operations for logs. 

Any thoughts?   The one comment I had gotten from VMware Explore was content pipelines where I can migrate Cloud Templates and Orchestrator Workflows.  But it appears I can create content endpoints in LCM from any managed or unmanaged environment. 

Damion Terrell  .   +  (He/Him)  +  . *  .  +   @   + .    *  .    +      .                    
Core IT Service Specialist * . + * . + . + . + * +
UNM – IT Platforms – VIS + . . . . . . . . .
. + . + * . + * .
* . . + . . . . + . + * + .
“You learn the job of the person above you, * + . + * @
and you teach your job to the person below you..” . * +
0 Kudos
1 Reply
venkat527
Contributor
Contributor

I am getting this error while trying to connect the VMware aria suite life cycle.

still loading the login screen

0 Kudos