I’ve finally gotten around to upgrading the vRLI Configuration Management and Audit Tool to handle the full deployment process as well as clustering! Let’s take it for a spin to see what the new features allow us to do!
1. First we need to deploy the vRLI VMs from OVA that can be downloaded from my.vmware.com. Once they have been fully booted and you see them serving the following webpage we can start. You can close your browser at this point; nothing is required here other than we are checking to make sure that they are fully booted.
2. The tool uses a JSON configuration file that you can see a sample of by running the program with a “-d” flag or browsing the first part of the Python (my recommended approach). You can also generate a simplified version by calling the wizard using a “-b” flag. For now, I’m going to create my configuration file based on the sample in the documentation with a single Master Node under the “fqdn” key and 2 Secondary Nodes under the “nodes” key in my JSON file. This means that when the script is done I will have a new, 3 node vRLI Cluster.
Let’s kick off the program and tell it to use my configuration file by running:
python li-json-api.py -f ctest.json -r
more “Deploying vRealize Log Insight (vRLI) via API”
For those of you who are interested I have updated the API based audit and remediation tool with a couple new features. After all, what is the use of automation if it isn’t user friendly?
1. Better error handling of remediation errors: In the past you would just get a message to the effect of “Something went wrong” but now the tool will pass the HTTP status code and Error Details from the Log Insight Server’s response to your remediation request. In the below example you can see this in action.
2. Now includes a wizard to help build a simplified JSON configuration file! Now, without having to create a single bit of JSON you can quickly get value from the tool. The wizard is simplified because let’s be honest, if you want the wizard you don’t want to answer 250 questions. Because of this some things are assumed/disabled. If you want them then you can simply add it to the code or use the template in the included docs (use the -d switch).
I hope that this helps you get started in seeing the value of using Configuration APIs to manage your Log Insight Servers!