vRealize Suite LifeCycle Manager – Environment
As part of my new role, I have worked extensively on a project deploying VMware’s vRealize Suite Lifecycle Manager. It’s a project that is fairly new in the VMware ecosystem and not a lot of people have come across it. If you run any of the following products then it’s worth checking it out.
vRealize Log Insight
vRealize Network Insight
This is the first post of a few that I’m going to do on vRSLCM showing a bit of the environment Management and a product deployment
vRSLCM performs two fairly distinct roles. These are Environment and Content Management. The Content management part of the product is a replacement for codestream (Houdini)
Environment management is used for deployment, Patching, Certificate and environment config management.
To deploy a component you must first set up an environment within vRSLCM
This involves creating a datacentre where you also add the target vCentre
When that is done you can create an environment. An environment is like a wrapper for the products and controls them as a set. You can have multiple of these with the idea that you would have production, test development etc. You can have multiple of each of these if required.
When you have your environment created its time to deploy a product. vRSLCM will do this step for you but it needs to have the relevant files within the appliance. These are added in the settings section under product binaries.
You can use three different ways to add the relevant files into the appliance. Connect it to an NFS share with the relevant files, Manually upload via SSH or by far the easiest is to add your “My VMware” details and then vRSLCM will download them automatically. The advantage to the My VMware method is that it can also track the available patches for the products.
I used a combination of NFS and My VMware to add the product binaries
Once that was done I added two separate environments (one for testing and one to simulate production) and then deployed some workloads
Here you can see that I have vROPS deployed in test and both Log Insight and vROPS in the production environment.
I am now going to use vRSLCM to deploy Log Insight Into the test environment by adding it as a product
Here you can see I have selected Log Insight to be added (It is possible to add multiple at the same time.). I have gone for a “small” config and I have chosen version 4.6.0.
You will then be asked to confirm the user agreement and vRSLCM will take you into the deployment step. Here you will provide the specific info. A really nice feature is that as part of this wizard if you provided the My VMware details earlier it will list the keys for you.
Most of the Infrastructure details are taken from the environment set up earlier Including vCentre, Cluster, Network details, Datastore NTP etc. It will also deploy certificates for you at this step (a really nice feature)
These are the only questions that the wizard can’t answer which is basically the node size to be deployed. The name for the VM, Hostname and IP address. Once you have added these to the wizard check that both forward and reverse DNS Is in place before going any further. This is because on the next step the vRSLCM does a prerequisite check.
Here you can see that the precheck failed as I had a clash of virtual machine names between my test and production environments. This is an issue as they are in the same vCentre/Cluster
With the precheck passing, you submit this and vRSLCM will go off and deploy. Obviously, this can take quite a while depending on the config you have asked to deploy. This can be monitored in the requests section.
Here you can see all the steps and if required can troubleshoot any failures. When complete it should look something like the below
Going back to the Environment we now see that Test matches Production