Search Results

VMware Aria Suite Lifecycle allows us to download product binaries once we have "My VMware Account " mapped into it. What really happens in the backend? Where does it store the product binary? In short , when a download is triggered and mapping is done , there is a content id generated. This content id is something like the one shown below 2023-07-14 03:46:27.764 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Created content with vmid :: ced3c5b4-1cdc-4107-899c-5261e949c67b. Once it's created for this specific binary download it is stored under /data/vm-config/vmrepo/productBinariesRepo/ Are you interested to know in depth , then let's jump into it. We will understand the whole process by looking into the logs The moment we click on ADD for any product binary,it can be an upgrade or install there is a validation done and a request to request service is generated ****** ADD is clicked here ****** 2023-07-14 03:32:56.415 INFO [http-nio-8080-exec-4] c.v.v.l.l.u.SettingInputValidationUtil - -- Product validation status : true 2023-07-14 03:32:56.415 INFO [http-nio-8080-exec-4] c.v.v.l.l.c.SettingsController - -- Validation result for Setting :myvmwaredownload result true 2023-07-14 03:32:56.416 INFO [http-nio-8080-exec-4] c.v.v.l.l.c.SettingsController - -- Setting Value before save: "" ****** Request to request service is generated ****** 2023-07-14 03:32:56.418 INFO [http-nio-8080-exec-4] c.v.v.l.l.u.RequestSubmissionUtil - -- ++++++++++++++++++ Creating request to Request_Service :::>>> { "vmid" : "9a42d32b-8866-47ab-ba5b-e3bb4e119393", "transactionId" : null, "tenant" : "default", "requestName" : "myvmwaredownload", "requestReason" : "VROPS 8.12.1 Type Install - My VMware Product Binary Download", "requestType" : "MYVMWARE_DOWNLOAD", "requestSource" : null, "requestSourceType" : "user", "inputMap" : { "productId" : "vrops", "productVersion" : "8.12.1", "productBinaryType" : "Install", "productBinaryPath" : null, "componentName" : null, "mappingType" : null, "productName" : "VMware Aria Operations", "requestId" : null, "removeBinary" : null }, "outputMap" : { }, "state" : "CREATED", "executionId" : null, "executionPath" : null, "executionStatus" : null, "errorCause" : null, "resultSet" : null, "isCancelEnabled" : null, "lastUpdatedOn" : 1689305576418, "createdBy" : null } As we can see from the request above, I am trying to download VMware Aria Operations 8.12.1 Install binary It identifies how many requests to be processed. There is an engine request created and it's set to IN PROGRESS 2023-07-14 03:32:56.432 INFO [http-nio-8080-exec-4] c.v.v.l.l.u.SettingsHelper - -- MyVMware download requestIds : 9a42d32b-8866-47ab-ba5b-e3bb4e119393 2023-07-14 03:32:56.830 INFO [scheduling-1] c.v.v.l.r.c.RequestProcessor - -- Processing request with ID : 9a42d32b-8866-47ab-ba5b-e3bb4e119393 with request type MYVMWARE_DOWNLOAD with request state INPROGRESS. The statemachine is now kicked in 2023-07-14 03:32:57.911 INFO [scheduling-1] c.v.v.l.a.c.FlowProcessor - -- Injected OnStart Edge for the Machine ID :: myvmwaredownload Validates MY VMware credentials 2023-07-14 03:32:58.007 INFO [pool-3-thread-20] c.v.v.l.p.c.m.t.StartGenericMyVMwareCredentialsTask - -- Starting :: Start Validating the MyVMware Credentials Starts downloading binaries after fetching the token for the user mapped under MY VMware account 2023-07-14 03:32:58.563 INFO [pool-3-thread-25] c.v.v.l.p.c.m.t.MyVmwareDownloadTask - -- Starting :: Download VMware Aria Product Binaries 2023-07-14 03:32:58.565 INFO [pool-3-thread-25] c.v.v.l.p.c.m.t.MyVmwareDownloadTask - -- Trying to get access token with user arun@arunnukula.com 2023-07-14 03:32:58.566 INFO [pool-3-thread-25] c.v.v.l.c.a.InternalOnlyApiAspect - -- Internal Only Check for: execution(ResponseEntity com.vmware.vrealize.lcm.locker.controller.CredentialController.getPassword(String)) 2023-07-14 03:32:58.568 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token - Started 2023-07-14 03:32:58.569 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Myvmware base URL: https://apigw.vmware.com 2023-07-14 03:32:58.569 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token. Current try number : '1' 2023-07-14 03:32:59.964 INFO [pool-3-thread-25] c.v.v.l.u.RestHelper - -- Status code : 200 2023-07-14 03:32:59.965 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token - Finished 2023-07-14 03:32:59.966 INFO [pool-3-thread-25] c.v.v.l.p.c.m.t.MyVmwareDownloadTask - -- Successfully logged into my vmware with account username Checksum validation is done 2023-07-14 03:32:59.971 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentDownloadController - -- INSIDE ContentDownloadControllerImpl 2023-07-14 03:32:59.971 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentDownloadController - -- REPO_NAME :: /checksumRepo 2023-07-14 03:32:59.972 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentDownloadController - -- CONTENT_PATH :: /vrops/8.12.1/checksum.json 2023-07-14 03:32:59.972 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentDownloadController - -- URL :: /checksumRepo/vrops/8.12.1/checksum.json 2023-07-14 03:32:59.972 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentDownloadController - -- Decoded URL :: /checksumRepo/vrops/8.12.1/checksum.json The initial phase of the download process begins 2023-07-14 03:33:12.263 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- *** Download requested VMware Aria Product : [VROPS-8.12.1]: OPERATIONS-8121 2023-07-14 03:33:12.263 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token - Started 2023-07-14 03:33:12.264 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Myvmware base URL: https://apigw.vmware.com Download group is identified 2023-07-14 03:45:30.871 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Download group to be checked OPERATIONS-8121 against OPERATIONS-8121. 2023-07-14 03:45:30.871 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- *** Binary file NAME match happened for : 'vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' 2023-07-14 03:45:30.872 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- *** Binary file NAME match happened for : 'vRealize_Operations_Manager_With_CP-8.x-to-8.12.1.21952629.pak' 2023-07-14 03:45:30.872 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- *** Binary file NAME match happened for : 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' Starts writing the binary to disk 2023-07-14 03:45:34.357 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Successfully created the metadata file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.metadata ' with content '886d6d4ce3ff995f1faa24f00e9aec86e2574477'. 2023-07-14 03:45:34.357 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Starting download of 'vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' to '/data/myvmware/vrops/8.12.1/install' ... 2023-07-14 03:45:34.393 INFO [pool-3-thread-25] c.v.v.l.u.RestHelper - -- Status code : 200 2023-07-14 03:45:34.393 INFO [pool-3-thread-25] c.v.v.l.u.DownloadHelper - -- Started writing input stream to the file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova'. 2023-07-14 03:46:27.764 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Created content with vmid :: ced3c5b4-1cdc-4107-899c-5261e949c67b. 2023-07-14 03:46:27.764 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- SOURCE LOCATION :: /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova 2023-07-14 03:46:27.764 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- content.getRepositoryIdentifier() :: productBinariesRepo 2023-07-14 03:46:27.766 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- DESTINATION LOCATION :: productBinariesRepo 2023-07-14 03:46:27.768 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- DESTINATION FOLDER LOCATION :: /data/vm-config/vmrepo/productBinariesRepo/ce/ced3c5b4-1cdc-4107-899c-5261e949c67b Download is now complete and uploaded to content repo 2023-07-14 03:51:02.014 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Content uploaded successfully in the content repo 2023-07-14 03:51:02.016 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Download product binary file 'vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' - Finished. 2023-07-14 03:51:02.028 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Verifying if binary file 'vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' of 'VROPS-8.12.1' is fully downloaded. 2023-07-14 03:51:02.151 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Validate Checksum disabled false 2023-07-14 03:51:02.152 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- >> PROCESSING 1 of 1. File Name : vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova 2023-07-14 03:51:02.152 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Starting :: checksum matching for : /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova 2023-07-14 03:51:02.155 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract directory for source file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' is '/data/tempextract/9aeb0d09-be87-446e-bd33-14679eab6738/'. 2023-07-14 03:51:02.156 INFO [pool-3-thread-25] c.v.v.l.u.ShellExecutor - -- Executing shell command: tar -xf /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova -C /data/tempextract/9aeb0d0 9-be87-446e-bd33-14679eab6738/ --wildcards *.mf 2023-07-14 03:51:02.156 INFO [pool-3-thread-25] c.v.v.l.u.ProcessUtil - -- Execute tar 2023-07-14 03:51:02.291 INFO [pool-3-thread-25] c.v.v.l.u.ShellExecutor - -- Result: []. 2023-07-14 03:51:02.292 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' to '/data/tempextract/9aeb0d09-be87-446e-bd 33-14679eab6738/' success. 2023-07-14 03:51:02.293 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Binary file NAME match happened for : /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova 2023-07-14 03:51:02.295 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Adding result record for :: vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova 2023-07-14 03:51:02.296 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- ProductId: vrops The temporary extract directory is deleted 2023-07-14 03:51:02.296 INFO [pool-3-thread-25] c.v.v.l.u.f.FileUtil - -- Directory is deleted : /data/tempextract/9aeb0d09-be87-446e-bd33-14679eab6738 2023-07-14 03:51:02.300 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract directory '/data/tempextract/9aeb0d09-be87-446e-bd33-14679eab6738/' for source file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova' is deleted. 2023-07-14 03:51:02.300 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Checksum MATCHED for file vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova of VROPS-8.12.1. Along with VMware Aria Operations 8.12.1,we have the cloud proxy to be downloaded as well 2023-07-14 03:51:02.385 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get product download url for 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' - Started. 2023-07-14 03:51:04.855 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get product download url for 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' - Finished. 2023-07-14 03:51:04.856 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- HOST of final download URL :: https://download2.vmware.com 2023-07-14 03:51:04.856 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- SHA1 Checksum check for file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' with checksum value '193444c7b424f67ab1a46939e4f1a3d7aa6b85af ' - started 2023-07-14 03:51:04.858 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- SHA1 Checksum check for file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' with checksum value '193444c7b424f67ab1a46939e4f1a3d7aa6b85af ' - Finished 2023-07-14 03:51:04.858 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Starting download of product binary file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova'. Size is : '1.65 GB'. 2023-07-14 03:51:04.859 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Download product binary file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' - Started. 2023-07-14 03:51:04.860 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Download product binary file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova'.Current try number : '1' 2023-07-14 03:51:04.860 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token - Started 2023-07-14 03:51:04.861 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Myvmware base URL: https://apigw.vmware.com 2023-07-14 03:51:04.862 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token. Current try number : '1' 2023-07-14 03:51:06.201 INFO [pool-3-thread-25] c.v.v.l.u.RestHelper - -- Status code : 200 2023-07-14 03:51:06.273 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Get myvmware access token - Finished 2023-07-14 03:51:06.275 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Successfully created the metadata file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.metadata' with content '193444c7b424f67ab1a46939e4f1a3d7aa6b85af'. 2023-07-14 03:51:06.277 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Starting download of 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' to '/data/myvmware/vrops/8.12.1/install' ... Starts writing the download to the specific location 2023-07-14 03:51:06.275 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Successfully created the metadata file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.metadata' with content '193444c7b424f67ab1a46939e4f1a3d7aa6b85af'. 2023-07-14 03:51:06.277 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Starting download of 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' to '/data/myvmware/vrops/8.12.1/install' ... 2023-07-14 03:51:06.363 INFO [pool-3-thread-25] c.v.v.l.u.RestHelper - -- Status code : 200 2023-07-14 03:51:06.363 INFO [pool-3-thread-25] c.v.v.l.u.DownloadHelper - -- Started writing input stream to the file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova'. 2023-07-14 03:51:40.944 INFO [pool-3-thread-25] c.v.v.l.u.DownloadHelper - -- Finished writing input stream to the file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova'. 2023-07-14 03:51:41.000 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Writing file to content repo with filename vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova. 2023-07-14 03:51:41.003 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Uploading product binary with filename cloudproxy.ova to content repo. 2023-07-14 03:51:41.003 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Content delete requested for url /productBinariesRepo/vrops/8.12.1/install/cloudproxy.ova. 2023-07-14 03:51:41.520 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Content delete is failed with given URL :: /productBinariesRepo/vrops/8.12.1/install/cloudproxy.ova 2023-07-14 03:51:41.521 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Creating content operation. 2023-07-14 03:51:41.532 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- URL :: /productBinariesRepo/vrops/8.12.1/install/cloudproxy.ova 2023-07-14 03:51:41.536 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- URL :: /productBinariesRepo/vrops/8.12.1/install/cloudproxy.ova 2023-07-14 03:51:41.537 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH LENGTH :: 6 2023-07-14 03:51:41.537 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH LENGTH TEST PASSED 2023-07-14 03:51:41.539 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- SEARCHINE FOR :: REPO -> productBinariesRepo :: NAME -> __ROOT__ :KXKXKXKX PARENT -> 367eb197-9850-4013-b66e-e4c4077b3263 2023-07-14 03:51:41.550 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH :: 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH ::productBinariesRepo 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH ::vrops 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH ::8.12.1 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH ::install 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- PATH ::cloudproxy.ova 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- ADDING NODE - PATH LENGTH :: 6 2023-07-14 03:51:41.551 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- SEARCHINE FOR :: REPO -> productBinariesRepo :: PARENT -> a530119f-d933-4391-9d62-6fe8d40d57f3 :: NAME -> vrops 2023-07-14 03:51:41.554 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- SEARCHINE FOR :: REPO -> productBinariesRepo :: PARENT -> 45ce3af0-0325-4439-af4d-3160366d8bfd :: NAME -> 8.12.1 2023-07-14 03:51:41.557 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- SEARCHINE FOR :: REPO -> productBinariesRepo :: PARENT -> d3e25c69-45db-4e05-b87c-cbf4aacbe24e :: NAME -> install 2023-07-14 03:51:41.559 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- SEARCHINE FOR :: REPO -> productBinariesRepo :: PARENT -> fbc115f0-dc23-4e8b-87a7-5d057f51cfec :: NAME -> cloudproxy.ova 2023-07-14 03:51:41.562 INFO [pool-3-thread-25] c.v.v.l.c.s.ContentDownloadUrlServiceImpl - -- ADDING NODE :: 5 2023-07-14 03:51:41.570 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Created content with vmid :: 3a051861-9b68-43a2-aa65-71abc24aae59. 2023-07-14 03:51:41.570 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- SOURCE LOCATION :: /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova 2023-07-14 03:51:41.571 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- content.getRepositoryIdentifier() :: productBinariesRepo 2023-07-14 03:51:41.572 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- DESTINATION LOCATION :: productBinariesRepo 2023-07-14 03:51:41.573 INFO [pool-3-thread-25] c.v.v.l.c.c.FileContentDatabase - -- DESTINATION FOLDER LOCATION :: /data/vm-config/vmrepo/productBinariesRepo/3a/3a051861-9b68-43a2-aa65-71abc24aae59 2023-07-14 03:51:43.267 INFO [http-nio-8080-exec-2] c.v.v.l.d.i.u.InventoryWriteUtil - -- QUERY MAP LENGTH :: 3 2023-07-14 03:51:43.271 INFO [http-nio-8080-exec-2] c.v.v.l.d.i.u.InventorySchemaQueryUtil - -- GETTING ROOT NODE FOR :: ProductInventory 2023-07-14 03:51:43.592 INFO [http-nio-8080-exec-3] c.v.v.l.d.i.u.InventoryWriteUtil - -- QUERY MAP LENGTH :: 3 2023-07-14 03:51:43.592 INFO [http-nio-8080-exec-3] c.v.v.l.d.i.u.InventorySchemaQueryUtil - -- GETTING ROOT NODE FOR :: ProductInventory 2023-07-14 03:51:46.066 INFO [pool-3-thread-25] c.v.v.l.c.c.ContentRepositoryController - -- Content uploaded successfully in the content repo 2023-07-14 03:51:46.066 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadRestClient - -- Download product binary file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' - Finished. 2023-07-14 03:51:46.067 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Verifying if binary file 'vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' of 'VROPS-8.12.1' is fully downloaded. 2023-07-14 03:51:46.069 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Validate Checksum disabled false 2023-07-14 03:51:46.069 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- >> PROCESSING 1 of 1. File Name : vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova 2023-07-14 03:51:46.069 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Starting :: checksum matching for : /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova 2023-07-14 03:51:46.069 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract directory for source file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' is '/data/tempextract/ b2c7eb4f-e3cc-49bc-b0e8-225d4a9c08ec/'. 2023-07-14 03:51:46.231 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova' to '/data/tempextract/b2c7eb4f-e3cc-49bc-b0e8-225 d4a9c08ec/' success. 2023-07-14 03:51:46.231 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Binary file NAME match happened for : /data/myvmware/vrops/8.12.1/install/vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova 2023-07-14 03:51:46.233 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Adding result record for :: vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova 2023-07-14 03:51:46.235 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- ProductId: vrops 2023-07-14 03:51:46.235 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- File match found 2023-07-14 03:51:46.235 INFO [pool-3-thread-25] c.v.v.l.u.f.FileUtil - -- Directory is deleted : /data/tempextract/b2c7eb4f-e3cc-49bc-b0e8-225d4a9c08ec 2023-07-14 03:51:46.240 INFO [pool-3-thread-25] c.v.v.l.d.s.h.SourceMappingUtil - -- Extract directory '/data/tempextract/b2c7eb4f-e3cc-49bc-b0e8-225d4a9c08ec/' for source file '/data/myvmware/vrops/8.12.1/install/vRealize-Operations-Clo ud-Proxy-8.12.1.21952631_OVF10.ova' is deleted. 2023-07-14 03:51:46.240 INFO [pool-3-thread-25] c.v.v.l.d.m.h.MyVmwareDownloadUtil - -- Checksum MATCHED for file vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova of VROPS-8.12.1. 2023-07-14 03:51:46.270 INFO [pool-3-thread-25] c.v.v.l.p.c.m.t.MyVmwareDownloadTask - -- Source mapping results for myvmware download is ::: [ { "productId" : "vrops", "productVersion" : "8.12.1", "productBinaryType" : "install", "productBinaryPath" : "vRealize-Operations-Manager-Appliance-8.12.1.21952151_OVF10.ova", "componentName" : "default", "mappingType" : "MY VMware", "productName" : "VMware Aria Operations", "requestId" : null, "removeBinary" : null }, { "productId" : "vrops", "productVersion" : "8.12.1", "productBinaryType" : "install", "productBinaryPath" : "vRealize-Operations-Cloud-Proxy-8.12.1.21952631_OVF10.ova", "componentName" : "cloudproxy", "mappingType" : "MY VMware", "productName" : "VMware Aria Operations", "requestId" : null, "removeBinary" : null } ]

Upgrading infrastructure and management applications regularly offers several benefits: 1. Security: Newer versions often include security patches and fixes, protecting your systems against vulnerabilities and reducing the risk of cyberattacks or data breaches. 2. Performance: Upgrades often bring performance improvements, optimizing resource utilization, enhancing speed, and enabling your infrastructure to handle increased workloads efficiently. 3. Compatibility: As technology advances, software and hardware requirements change. Upgrading ensures compatibility with newer technologies, preventing compatibility issues and enabling seamless integration with other systems. 4. Features and Functionality: Upgrades frequently introduce new features, functionality, and enhancements that can improve productivity, streamline operations, and provide a competitive edge. Staying up to date allows you to take advantage of these advancements. 5. Support and Maintenance: Software vendors typically provide ongoing support and maintenance for the latest versions, ensuring you have access to assistance when needed. Older versions may have limited support or no longer receive updates. 6. Cost Savings: Maintaining outdated infrastructure and applications can become costly due to increased downtime, security risks, and inefficient processes. Regular upgrades can help minimize these risks and potential expenses. By keeping your infrastructure and management applications up to date, you can leverage the latest technology, enhance security, improve performance, and optimize your overall operations, ultimately benefiting your organization in the long run. VMware Aria Suite Lifecycle provides simplified lifecycle management through streamlined deployment,configuration,patching,upgrades,configuration management and decommissioning process. Suite Lifecycle (formerly vRSLCM) automates most of the repetitive tasks which avoids human errors. So, If you haven't started exploring VMware Aria Suite Lifecycle , it's right time to begin...... 👍

It was all normal till November 8, 2022 till my dad boarded Chicago flight from Abu Dhabi to visit my brother in Austin along with my mother. Flight was about to land in Chicago O'Hare in 30 minutes and all of a sudden he lost his geo-location sense and had a sense of fear. My mom was all alone with him, somehow they managed to get off Chicago flight but they were not allowed to board Austin flight due to aggressive & panicky behaviour of dad. No one knows what's happening at that instance. It gives me goosebumps when I imagine what my mom had to go through during that 12 hours. Fortunately they were already in US which allowed my brother to pick them up from Chicago. Over a period of next few weeks he totally stopped conversations , no appetite , he was lost in his own world. Few days later he was admitted at St. David's Round Rock Medical Center where every possible test was performed and everything turned out negative. They had to extract his cerebrospinal fluid for examination which was sent to Mayo Clinic. After few days at hospital he was discharged and based on doctors suggestion we decided to bring him back to India safely. December 26,2022 we took him to KIMS, Hyderabad for further examinations as we still didn't know the exact cause as we were waiting for results from Mayo Clinic,Cleaveland. Upon careful examination and few MRI scans, it was revealed that he had CJD (Creutzfeldt-Jakob Disease). This was something new to us. Doctors stated that he might have 6 months at hand but he was hardly alive for 40 days. CJD is a rare disease, one in a million gets this and in a million CJD patients , dad's condition was rarest as it was rapidly progressive. The reason I wanted to share this with you all is to bring awareness of CJD, it can happen all of a sudden and we won't even know the changes are occurring in our brain. Early hours of February 1, 2023 dad passed away peacefully with everyone of his family around him. Let's understand CJD in-depth and why does it occur. What's CJD CJD stands for Creutzfeldt-Jakob Disease. It is a rare and degenerative brain disorder that belongs to a group of diseases called prion diseases. Prions are abnormal proteins that can cause normal proteins in the brain to become misfolded, leading to the accumulation of damaged tissue. CJD affects a person's cognitive abilities, causing rapid mental deterioration, memory loss, personality changes, and difficulties with movement. It is a progressive and ultimately fatal condition. Why does it occur? Creutzfeldt-Jakob Disease (CJD) occurs due to the misfolding and accumulation of a specific protein called prion protein. The exact cause of this misfolding is not fully understood, but it is believed to be associated with spontaneous changes in the structure of the protein. In some cases, CJD can be inherited through mutations in the PRNP gene, which provides instructions for making the prion protein. Additionally, CJD can also be acquired through exposure to infected brain or nervous tissue, typically through medical procedures or contaminated surgical instruments. However, such cases are extremely rare. Overall, the underlying mechanisms and triggers for prion misfolding and the development of CJD are still an active area of research, and scientists continue to investigate these aspects in order to better understand and manage this complex disease. I am forever indebted to my uncle Dr Naresh Vadlamani. who was always there for us till the end to make right decisions and guided us appropriately. Columbus hospitals was his home for few days , thanks to all its staff who helped us in crisis. !!!! Bala Sista , Kiran Nukala , Divya. & Vaishnavi thank you !!!! !!! You'll be missed dad , your always with us !!!

A good product manager possesses several key qualities that contribute to their effectiveness in the role. Here are some important qualities of a good product manager: 1. Strong Leadership: A good product manager is capable of leading a cross-functional team, driving collaboration, and inspiring others to achieve shared goals. 2. Strategic Thinking: They have the ability to think strategically and make informed decisions based on market analysis, customer needs, and business goals. They can identify opportunities, set a clear product vision, and devise effective strategies to achieve it. 3. Customer-Centric Approach: A good product manager deeply understands customer needs, pain points, and desires. They prioritize user satisfaction and leverage customer feedback to make informed product decisions. 4. Excellent Communication: Effective communication is crucial for a product manager. They can articulate their vision, share product requirements, and collaborate with various stakeholders, including developers, designers, marketing teams, and executives. 5. Analytical Skills: They possess strong analytical skills to analyze data, identify trends, and make data-driven decisions. They can gather insights from market research, user feedback, and metrics to guide product improvements. 6. Adaptability and Flexibility: Good product managers can adapt to changing market conditions, prioritize tasks, and adjust their strategies accordingly. They are comfortable with ambiguity and can handle evolving priorities. 7. Technical Aptitude: While not always mandatory, a good product manager has a solid understanding of the technical aspects of their product. This helps them effectively communicate with development teams and make informed decisions. 8. Problem-Solving Abilities: They are adept at identifying problems, defining solutions, and overcoming obstacles. Good product managers approach challenges with a creative mindset and find innovative ways to solve them. 9. Empathy and Collaboration: They foster a collaborative and inclusive work environment, showing empathy towards team members' perspectives. They actively listen, understand others' viewpoints, and encourage teamwork. 10. Result Orientation: A good product manager is focused on delivering results and achieving measurable outcomes. They set clear goals, track progress, and take ownership of the product's success. These qualities collectively enable a good product manager to effectively lead product development, align teams, and deliver successful products that meet customer needs and drive business growth.

Upgrading VMware products frequently can have both advantages and challenges. Here are a few points to consider: Advantages: 1. Access to new features and enhancements: Frequent upgrades can provide you with the latest features, performance improvements, security updates, and bug fixes offered by VMware. 2. Better compatibility and support: Upgrading to newer versions can ensure compatibility with other software and hardware, and it may offer improved support from VMware. Challenges: 1. Time and resources: Frequent upgrades may require time and effort to plan, test, and implement, especially if you have a complex IT infrastructure. 2. Disruption to operations: Upgrading software can temporarily disrupt operations as you transition to the new version, potentially requiring downtime or impacting productivity. 3. Compatibility issues: There's a possibility of encountering compatibility issues with existing software, hardware, or custom configurations during the upgrade process. It's important to weigh the benefits against the potential challenges and consider factors such as your specific requirements, the stability of your current environment, and the significance of the new features or fixes in the newer versions.

There was a vRSLCM or VASL environment where the product UI wasn't loading at all after a reboot After checking logs , none of the application services were running as expected. Apart from bootstrap all of them were stopped or in "not running" status What could have happened ? How do i resolve this ? If i look closely , the postgres service is stopped. Unless postgres is up , none of the application services would start. So my starting point would be postgres. Executing status command on vposgres tells us the story /storage/db/pgdata ]# systemctl status vpostgres * vpostgres.service - VMware Postgres database server Loaded: loaded (/etc/systemd/system/vpostgres.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2023-06-29 15:25:54 UTC; 32s ago Process: 27267 ExecStart=/opt/vmware/vpostgres/current/bin/pg_ctl -s -D ${VMWARE_POSTGRES_DATA} -w -t ${VMWARE_POSTGRES_PGCTL_TIMEOUT} start (code=exited, status=1/FAILURE) Jun 29 15:25:54 lcm-fqdn systemd[1]: vpostgres.service: Service RestartSec=100ms expired, scheduling restart. Jun 29 15:25:54 lcm-fqdn systemd[1]: vpostgres.service: Scheduled restart job, restart counter is at 5. Jun 29 15:25:54 lcm-fqdn systemd[1]: Stopped VMware Postgres database server. Jun 29 15:25:54 lcm-fqdn systemd[1]: vpostgres.service: Start request repeated too quickly. Jun 29 15:25:54 lcm-fqdn systemd[1]: vpostgres.service: Failed with result 'exit-code'. Jun 29 15:25:54 lcm-fqdn systemd[1]: Failed to start VMware Postgres database server. root@lcm-fqdn [ /storage/db/pgdata ]# systemctl start vpostgres Job for vpostgres.service failed because the control process exited with error code. See "systemctl status vpostgres.service" and "journalctl -xe" for details. root@lcm-fqdn [ /storage/db/pgdata ]# Checking journalctl logs , we come to know why it was failing Reference Command : journalctl -u vpostgres.service --since "YYYY-MM-DD" Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Control process exited, code=exited status=1 Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Failed with result 'exit-code'. Jun 29 12:18:22 lcm-fqdn systemd[1]: Failed to start VMware Postgres database server. Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Service RestartSec=100ms expired, scheduling restart. Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Scheduled restart job, restart counter is at 1. Jun 29 12:18:22 lcm-fqdn systemd[1]: Stopped VMware Postgres database server. Jun 29 12:18:22 lcm-fqdn systemd[1]: Starting VMware Postgres database server... Jun 29 12:18:22 lcm-fqdn postgres[53444]: pg_ctl: directory "/var/vmware/vpostgres/current/pgdata" does not exist Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Control process exited, code=exited status=1 Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Failed with result 'exit-code'. Jun 29 12:18:22 lcm-fqdn systemd[1]: Failed to start VMware Postgres database server. Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Service RestartSec=100ms expired, scheduling restart. Jun 29 12:18:22 lcm-fqdn systemd[1]: vpostgres.service: Scheduled restart job, restart counter is at 2. Jun 29 12:18:22 lcm-fqdn systemd[1]: Stopped VMware Postgres database server. The whole folder contents of /var/vmware/** was missing on the problematic environment On a working environment like my lab , this is how the folder structure would look Now , if there is no snapshot how do i fix this ? Fortunately , we have the database which was under /storage/db/pgdata and that was intact. So to fix , the thought process was to create missing folders and symbolic links and see if that helps. As during postgres startup it was complaining about only this issue. Here are the steps taken to fix the problem Step-1 : Take snapshot of vRSLCM / VASL appliance Step-2 : Create vpostgres directory mkdir /var/vmware/vpostgres Step-3 : Set appropriate permissions to vpostgres directory chmod 755 /var/vmware/vpostgres Step-4 : Under vpostgres directory create version folder , which is 11 mkdir /var/vmware/vpostgres/11 Step-5 : Assign postgres:users permission to the folder created chown postgres:users /var/vmware/vpostgres/11 Step-6 : Change permissions for version directory "11" chown 700 /var/vmware/vpostgres/11 Step-7 : Create symbolic link "11" as shown below ln -s /var/vmware/vpostgres/11 11 Step-8 : Browse to the directory "11" cd /var/vmware/vpostgres/11 Step-9 : Create directory pgdata mkdir /var/vmware/vpostgres/11/pgdata Step-10 : Browse to directory pgdata cd pgdata Step-11 : Assign postgres:users to pgdata folder chmod postgres:users pgdata Step-12 : Create symbolic link for pgdata which points to the actual db location ln -s /storage/db/pgdata pgdata Step-13 : Restart postgres service vRSLCM systemctl start vpostgres.service Step-13 : Restart postgres service vRSLCM / VASL systemctl stop vrlcm-server.service systemctl start vrlcm-server.service systemctl status vrlcm-server.service Step-14 : Monitor /var/log/vrlcm/vmware_vrlcm.log for status. Ideally if the services are up UI and the whole application should be up After executing these steps , vRSLCM or VASL UI is now up

vRLSCM 8.x deployment through Easy Installer or vCF might fail while initializing postgres database with below exception Below snippet is taken from /var/log/bootstrap/firstboot/firstboot.log 2022-06-22 11:45:03.719 UTC [3053] DEBUG: proc_exit(-1): 0 callbacks to make ok performing post-bootstrap initialization ... ok syncing data to disk ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Success. You can now start the database server using: /opt/vmware/vpostgres/current/bin/pg_ctl -D /storage/db/pgdata -l logfile start Warning: your password will expire in 5 days Failed to start vpostgres.service: Transaction is destructive. See system logs and 'systemctl status vpostgres.service' for details. Ensure PostgreSQL server is fully started... Warning: your password will expire in 5 days PSQL: Sleeping 2 seconds for Postgres to start fully... + set -eu + set -x + log 'main bootstrap firstboot started' ++ date '+%Y-%m-%d %H:%M:%S' + echo '2022-06-22 11:45:28 main bootstrap firstboot started' 2022-06-22 11:45:28 main bootstrap firstboot started + for script in "${BOOTSTRAP_DIR}"/* + echo When it works following output is expected 2022-06-13 01:37:56.259 UTC [3064] DEBUG: proc_exit(-1): 0 callbacks to make ok performing post-bootstrap initialization ... ok syncing data to disk ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Success. You can now start the database server using: /opt/vmware/vpostgres/current/bin/pg_ctl -D /storage/db/pgdata -l logfile start Ensure PostgreSQL server is fully started... List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------+----------+----------+---------+-------+----------------------- postgres | postgres | UTF8 | C | C | template0 | postgres | UTF8 | C | C | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | C | C | =c/postgres + | | | | | postgres=CTc/postgres (3 rows) PostgreSQL server started. You are required to change your password immediately (password expired) su: Authentication token is no longer valid; new one required (Ignored) ALTER ROLE CREATE ROLE ALTER ROLE CREATE DATABASE password updated successfully The cause of the problem is that vmware-studio invokes firstboot script twice. This retriggers postgres configuration again while other one (original firstboot) was failed to configure fully. Note: "In case of VCF environment, execute steps 1 to 7" 1. SSH to SDDC Manager appliance and switch to root user 2. Open /etc/vmware/vcf/domainmanager/application-prod.properties in a text editor. 3. Add this line vrslcm.firstboot.timeout.period.in.minutes=15 4. Save the file and close the editor. 5. Restart the Domain Manager with: systemctl restart domainmanager 6. Wait 2 minutes for the service to restart. You can check status using: systemctl status domainmanager 7. Run the "Deploy vRealize Suite Lifecycle Manager" operation from the SDDC Manager UI. 8. Delete the postgres directory and run postgres configuration script. Incase of a vcf environment, customer has to perform this within 5mins or quicker. Once vRSLCM appliance gets deployed, login to Web Console from vCenter Server and perform following steps: 1. rm -rf /storage/db/pgdata/ 2. /etc/bootstrap/firstboot.d/02-configure-postgres.sh 3. /etc/bootstrap/firstboot.d/20-start-services 9. Reboot vRSLCM 10. Check vpostgres status service vpostgres status if in case admin@local password does not work , then use below command to reset it /opt/vmware/share/vami/vami-vlcm-passwd-reset Reboot Appliance and Login Verification After this workaround, vRSLCM UI will be up and running Check systemctl status vpostgres is in running state.

Before upgrading a vRealize product from one version to another, administrator needs to check how many phases or hops it might take for him to get to the desired version Also , check if the compatibility with the other vRealize products will remain intact. This used to be a manual effort from customer / administrator side and was little taxing on their part if you have large environments with multiple products involved Coming vRSLCM 8.8.2 , we introduced a new feature called Upgrade Planner There are two places where you would see an upgrade planner available Under Environments pane which helps customers or administrators to create a report if vRealize products are integrated between multiple vRSLCM environments For example , vRA might be a separate environment and vROPs managing or integrated with this vRA might be in another environment Note: Customer/Administrators should not deviate from the sequence of upgrades provided by Upgrade planner report as this will cause compatibility break Inside an Environment where administrators or customers would like to upgrade vRealize Products within itself You may download attached PDF which contains the procedure mentioned below if there is difficulty in reading screenshots Running an Upgrade Planner inside an vRSLCM environment Firstly , I upgraded my vRSLCM to 8.8.2 which provides me the new feature Upgrade Planner In my lab , apart from the globalenvironment which is my VMware Identity Manager , I do have 2 environments Environment called "Production" has multiple vRealize products in it vRealize Automation vRealize SaltStack Config vRealize Operations vRealize LogInsight vRealize Network Insight Environment called "sevensix" has one vRA 7.x product in it vRealize Automation 7.6 Now let's click on "Production" environment to get further details about it Now , let's click on "Upgrade Planner" , as shown below we are in an environment called "Production" All of the products which are available inside environment "Production" would be listed Upgrade Planner UI displays following data Product: vRealize product name Current Version: Current version of the product in this environment Latest Version: Latest version of the product which has been released by VMware Target Version: Target version of the product which is the desired one to go to If we examine this in detail , this is how we can interpret the UI Production Environment has ..... vRealize Automation 8.8.1 , whereas 8.8.2 is the latest version released. If i have to plan an upgrade , then the obvious target version would be 8.8.2 vRealize Log Insight 8.6.2 , whereas 8.8.2 is the latest version released. If i have to plan an upgrade , then the obvious target version would be 8.8.2 or 8.8.0 vRealize Operations 8.6.2 , whereas 8.6.3 is the latest version released. If i have to plan an upgrade , then the obvious target version would be 8.6.3 vRealize Network Insight 6.6.0 , whereas 6.7.0 is the latest version released. If i have to plan an upgrade , then the obvious target version would be 6.7.0 VMware Identity Manager 3.3.6 , whereas 3.3.6 is the latest version released. There is nothing to upgrade here vRealize Suite Lifecycle Manager 8.8.8 , whereas 8.8.2 is the latest version released. There is nothing to upgrade here The task at hand is to upgrade all of the eligible products to the latest ones. So let's generate our upgrade planner report Remember/Note: While upgrade planner is being generated do not navigate away from this page As seen in the above upgrade plan there is a need for 4 hops or windows needed for me to go from my existing versions to the target version ( latest available ) We can even download Upgrade Plan in PDF format so that it can be shared with wider group or stakeholders Now that we have "Upgrade Plan" , let's understand what it says Upgrade Plan presents me an optimal upgrade sequence of products in an environment. Out of all products selected in the environment , there are 4 eligible products which can be upgraded. vRA 8.8.1 to 8.8.2 and it takes 1 hop or window or attempt to reach target version vRLI 8.6.2 to 8.8.2 and it takes 1 hop or window or attempt to reach target version vROps 8.6.2 to 8.6.3 and it takes 1 hop or window or attempt to reach target version vRNI 6.6.0 to 6.7 and it takes 1 hop or window or attempt to reach target version Using this data , I can now confidently plan my upgrades Remember , Upgrade Planner will only show products which are not EOL or End of Life Running upgrade planner outside vRSLCM environment In this scenario , we will showcase how an upgrade planner can be leveraged outside of an environment This generic upgrade planner option gives us a way to change current version too as it's not dependent on environment Remember , end of life product releases will not be considered or even listed here Let's now generate an upgrade plan by selecting least possible versions of the product and the target version to be same as the latest version Select all of the products and then click on "Generate Upgrade Plan" If I go ahead with all minimum versions of the product then i'd be getting below exception which throws all the details regarding incompatibilities Let's say I have following environment and want to see upgrade path vRA 8.2 --> 8.8.2 vIDM 3.3.2 --> 3.3.6 vRSLCM 8.2 --> 8.8.2 Based on the previous data , here's the upgrade plan i get As seen in the above upgrade plan there is a need for 4 hops or windows needed for me to go from my existing versions to the target version ( latest available ) We can even generate a PDF out of this If we interpret or understand the report There are 4 windows / hops needed for us to reach target versions Window / Hop 1 1. Upgrade vRSLCM 8.2.0 to 8.4.1 2. Upgrade vIDM 3.3.2 to 3.3.4 3. Upgrade vRA 8.2.0 to 8.3.0 Window / Hop 2 1. Upgrade vIDM 3.3.4 to 3.3.5 2. Upgrade vRA 8.3.0 to 8.4.1 Windows / Hop 3 1. Upgrade vRSLCM 8.4.1 to 8.6.2 2. Upgrade vIDM 3.3.5 to 3.3.6 3. Upgrade vRA 8.4.1 to 8.6.2 Windows / Hop 4 1. Upgrade vRSLCM 8.6.2 to 8.8.2 2. Upgrade vRA 8.6.2 to 8.8.2 This is how an upgrade planner report can be generated and consumed in your planning. I have not written about vCF aware vRSLCM based environment's upgrade planner yet as i don't have a lab handy but from functionality wise it's pretty much the same

Documenting steps taken to install a vIDM ( Workspace One ) in my lab so that it would benefit others too Step-1 : Certificate Creation in Locker Create a certificate inside vRSLCM Locker. This would be your vIDM certificate Enter all information which is needed to create a certificate in the locker You must enter the load balancer name of in the CN field Under IP and Hostname section , enter all hostnames which belongs to vIDM cluster including Load Balancer Once certificate is created , click on the three dots next to the certificate and then download it A .pem file will be downloaded Edit the .pem file with the notepad The first section would be server certificate followed by root certificate. In my case root certificate is from vRSLCM's locker. The last section would be the private key. Copy the root certificate and create a separate cert called root.cer and then create a seperate file with server certificate and the key and call itas server certificate with key. Step:2 Importing certificates into NSX-T Login into NSX-T and then click on system to import the certificate files saved before root certificate server certificate with key root certificate should be imported as CA cert and then server certificate as certificate Step:3 Create Service Monitors You set up health check monitoring.Servers that fail to respond to the health checks within a specified time period are excluded from future connection handling. In a Web browser, log in to NSX-T Manager for the Management domain by using the user interface. On the main navigation bar, click Networking. In the navigation pane, click Load balancing and click the Monitors tab. From the Select monitor type drop-down menu, select Active. From the Add active monitor drop-down menu, select HTTPS and configure the settings. In the HTTP request section, click Configure The HTTP request and response configuration dialog box opens. On the HTTP request configuration tab, configure the settings On the HTTP response configuration tab, configure the settings, and click Apply In the SSL configuration section, click Configure. On the Monitors page, click Save Step:4 Creating Server Pool The server pool determines the load balancing algorithm and combines resources from the pool members. You add the three Workspace ONE Access cluster nodes as members of the server pool. In a Web browser, log in to NSX-T Manager for the Management domain by using the user interface On the main navigation bar, click Networking. In the navigation pane, click Load balancing, click the Server pools tab, and click Add server pool.The Add new server pool wizard opens. On the General properties page, configure the settings Click Select Members On the Configure server pool members page, click Add member, configure the settings, click Save, and click Apply Click Set Monitors, on the Select health monitors page, select didmmonitor, and click Apply.. On Server Pool page, click Apply Step:5 Create Application Profiles You create an application profile and associate it with a virtual server to define the behavior of a particular type of network traffic. The virtual server then processes traffic according to the values specified in the profile. In a Web browser, log in to NSX-T Manager for the Management domain by using the user interface. Create the application profiles for Workspace ONE Access or vIDM cluster On the main navigation bar, click Networking. In the navigation pane, click Load balancing and click the Profiles tab. From the Select profile type drop-down menu, select Application. From the Add application profile drop-down menu, select HTTP Profile, configure the settings, and click Save. Create a persistence profile for the cross-region Workspace ONE Access cluster. On the Load balancing page, click the Profiles tab. From the Select profile type drop-down menu, select Persistence. From the Add persistence profile drop-down menu, select Cookie, configure the settings, and click Save. Step:6 Creating Virtual Servers You create two L7 HTTP virtual servers for the cross-region Workspace ONE Access cluster. These virtual servers are associated with the configured application profile and server pool and distribute client connections among the server pool members. In a Web browser, log in to NSX-T Manager for the Management domain by using the user interface. On the main navigation bar, click Networking. In the navigation pane, click Load balancing and click the Virtual servers tab. From the Add virtual server drop-down menu, select L7 HTTP and configure the settings In the SSL Configuration section, click Configure The Edit SSL configuration dialog box opens. Click the Client SSL tab and configure the settings Click the Server SSL tab, configure the settings, and click Save Remember to select root certificate for LCM or any custom CA if your using your own certificate under Advanced Properties on both Client and Server SSL Expand the Load balancer rules section. Next to the Request rewrite phrase section click Set.The Set load balancer rules wizard opens. Click the Request rewrite tab, click Add rule, configure the settings, and click Save On Set load balancer rules page, click Apply. On the Virtual servers page, click Save. From the Add virtual server drop-down menu, select L7 HTTP, configure the settings, and click Save. This concludes NSX-T Load Balancer configuration for vIDM or Workspace One Step:7 Installing vIDM through vRSLCM Click on "Create Environment" Enable the trigger which says "Enable to Install/Import Identity Manager" Select the password , this is the default password Datacenter where it's to be provisioned Click on next to select "New Install" for vIDM. Choose Version and then the deployment type to be a cluster Accept EULA Select the certificate we created from Locker Select the vCenter Server , Cluster , Network , Datastore and Disk Mode as per your requirements Enter Default Gateway , Netmask , DNS and Search Path information along with DNS Server selection In the next pane you have map / enter all product properties like Selection of Certificate , select the certificate created before in locker Node Size , would be selecting Medium FIPS Compliance Mode , I'd leave it OFF Admin Password , I'd leave it to the default installer password Default Configuration Admin email would be configadmin@vsphere.local Default Configuration Admin username would be configadmin Default COnfiguration Admin password would be same as before , installer password I'd leave Sync Group Members ticked / selected In the Cluster Virtual IP Section , enter the FQDN and Delete IP for Database Under Components Section , enter VM Name , FQDN and IP Address of all the three nodes Perform Manual Validations Go ahead and check the box when manual validations are complete and ensure precheck is all good and green to move forward Submit the Request for deployment Step:8 vIDM Distributed Installation Completion

Added an AD group into vRSLCM and gave all available roles to that group Content Developer Content Release Manager LCM Cloud Admin Certificate Administrator From logs perspective, here are the actions which are performed in the background when you add a group and map roles to it ### vIDM Search group task is initiated ### 2022-07-27 22:50:12.085 INFO [pool-3-thread-13] c.v.v.l.v.c.t.s.VidmSearchUserGroupTask - -- Starting :: vIDM Search User Group task 2022-07-27 22:50:12.359 INFO [pool-3-thread-13] c.v.v.l.v.d.r.c.VidmRestClient - -- API Response Status : 200 Response Message : {"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]} 2022-07-27 22:50:12.359 INFO [pool-3-thread-48] c.v.v.l.v.d.r.c.VidmRestClient - -- API Response Status : 200 Response Message : {"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]} 2022-07-27 22:50:12.362 INFO [pool-3-thread-48] c.v.v.l.v.d.r.u.VidmUserGroupMgmtRestUtil - -- Get User response : VidmRestClientResponseDTO [statusCode=200, responseMessage={"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]}] 2022-07-27 22:50:12.364 INFO [pool-3-thread-13] c.v.v.l.v.d.r.u.VidmUserGroupMgmtRestUtil - -- Get User response : VidmRestClientResponseDTO [statusCode=200, responseMessage={"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]}] 2022-07-27 22:50:12.367 INFO [pool-3-thread-48] c.v.v.l.c.l.MaskingPrintStream - -- * SYSOUT/SYSERR CAPTURED: -- Get User response : VidmRestClientResponseDTO [statusCode=200, responseMessage={"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]}] 2022-07-27 22:50:12.369 INFO [pool-3-thread-13] c.v.v.l.c.l.MaskingPrintStream - -- * SYSOUT/SYSERR CAPTURED: -- Get User response : VidmRestClientResponseDTO [statusCode=200, responseMessage={"totalResults":0,"itemsPerPage":0,"startIndex":1,"schemas":[],"Resources":[]}] ### Group Search Task is successful ### 2022-07-27 22:50:12.429 INFO [pool-3-thread-13] c.v.v.l.v.d.r.c.VidmRestClient - -- API Response Status : 200 Response Message : {"totalResults":1,"itemsPerPage":1,"startIndex":1,"schemas":["urn:scim:schemas:core:1.0","urn:scim:schemas:extension:workspace:1.0"],"Resources":[{"id":"7e8dbd36-da 3b-4277-a42a-f3a3c5893faa","meta":{"created":"2022-02-14T00:56:55.862Z","lastModified":"2022-02-14T00:56:55.862Z","location":"https://idm.cap.org/SAAS/jersey/manager/api/scim/Groups/7e8dbd36-da3b-4277-a42a-f3a3c5893faa","version":"W/\"1644800215862\""},"displayName":"capadmins@cap.org","externa lId":"05da97d4-1269-48a2-94e9-1b7e4e4c9ea5","urn:scim:schemas:extension:workspace:1.0":{"distinguishedName":"CN=capadmins,CN=Users,DC=cap,DC=org","domain":"cap.org","internalGroupType":"EXTERNAL"}}]} 2022-07-27 22:50:12.429 INFO [pool-3-thread-48] c.v.v.l.v.d.r.c.VidmRestClient - -- API Response Status : 200 Response Message : {"totalResults":2,"itemsPerPage":2,"startIndex":1,"schemas":["urn:scim:schemas:core:1.0","urn:scim:schemas:extension:workspace:1.0"],"Resources":[{"id":"5fcb2bcd-4270-483e-9718-34d6b9139614","meta":{"created":"2022-02-14T00:56:55.863Z","lastModified":"2022-02-14T00:56:55.863Z","location":"https://idm.cap.org/SAAS/jersey/manager/api/scim/Groups/5fcb2bcd-4270-483e-9718-34d6b9139614","version":"W/\"1644800215863\""},"displayName":"premadmins@cap.org","externalId":"20acbbd4-07d3-46ff-922c-a6c6daaf1664","urn:scim:schemas:extension:workspace:1.0":{"distinguishedName":"CN=premadmins,CN=Users,DC=cap,DC=org","domain":"cap.org","internalGroupType":"EXTERNAL"}},{"id":"7e8dbd36-da3b-4277-a42a-f3a3c5893faa","meta":{"created":"2022-02-14T00:56:55.862Z","lastModified":"2022-02-14T00:56:55.862Z","location":"https://idm.cap.org/SAAS/jersey/manager/api/scim/Groups/7e8dbd36-da3b-4277-a42a-f3a3c5893faa","version":"W/\"1644800215862\""},"displayName":"capadmins@cap.org","externalId":"05da97d4-1269-48a2-94e9-1b7e4e4c9ea5","urn:scim:schemas:extension:workspace:1.0":{"distinguishedName":"CN=capadmins,CN=Users,DC=cap,DC=org","domain":"cap.org","internalGroupType":"EXTERNAL"}}]} 2022-07-27 22:50:12.431 INFO [pool-3-thread-13] c.v.v.l.v.d.r.u.VidmUserGroupMgmtRestUtil - -- Get Group response : VidmRestClientResponseDTO [statusCode=200, responseMessage={"totalResults":1,"itemsPerPage":1,"startIndex":1,"schemas":["urn:scim:schemas:core:1.0","urn:scim:schemas:extension:workspace:1.0"],"Resources":[{"id":"7e8dbd36-da3b-4277-a42a-f3a3c5893faa","meta":{"created":"2022-02-14T00:56:55.862Z","lastModified":"2022-02-14T00:56:55.862Z","location":"https://idm.cap.org/SAAS/jersey/manager/api/scim/Groups/7e8dbd36-da3b-4277-a42a-f3a3c5893faa","version":"W/\"1644800215862\""},"displayName":"capadmins@cap.org","externalId":"05da97d4-1269-48a2-94e9-1b7e4e4c9ea5","urn:scim:schemas:extension:workspace:1.0":{"distinguishedName":"CN=capadmins,CN=Users,DC=cap,DC=org","domain":"cap.org","internalGroupType":"EXTERNAL"}}]}] 2022-07-27 22:50:12.708 INFO [pool-3-thread-48] c.v.v.l.c.l.MaskingPrintStream - -- * SYSOUT/SYSERR CAPTURED: -- Task Result : {"status":"SUCCESS","statusCode":200,"responseType":"com.vmware.vrealize.lcm.vidm.request.common.dto.ad.VidmFormattedUserNGrpListDTO","response":{"vidmUsers":[],"vidmGroups":[{"displayName":"premadmins@cap.org","groupType":"EXTERNAL","providerIdentifier":"5fcb2bcd-4270-483e-9718-34d6b9139614","domain":"cap.org","isDisabled":false,"groupMetadata":{"distinguishedName":"CN=premadmins,CN=Users,DC=cap,DC=org","externalId":"20acbbd4-07d3-46ff-922c-a6c6daaf1664","additionalMeta":[]}},{"displayName":"capadmins@cap.org","groupType":"EXTERNAL","providerIdentifier":"7e8dbd36-da3b-4277-a42a-f3a3c5893faa","domain":"cap.org","isDisabled":false,"groupMetadata":{"distinguishedName":"CN=capadmins,CN=Users,DC=cap,DC=org","externalId":"05da97d4-1269-48a2-94e9-1b7e4e4c9ea5","additionalMeta":[]}}]},"message":null,"currentState":null,"currentTask":null} 2022-07-27 22:50:12.708 INFO [pool-3-thread-48] c.v.v.l.p.a.s.Task - -- Injecting Edge :: OnVidmSearchUserGrpSuccess * * 2022-07-27 22:50:13.164 INFO [scheduling-1] c.v.v.l.a.c.EventProcessor - -- INITIALIZING NEW EVENT :: { "vmid" : "ab8c333e-5019-4df7-969f-8511af14dac8", "transactionId" : null, "tenant" : "default", "createdBy" : "root", "lastModifiedBy" : "root", "createdOn" : 1658962212711, "lastUpdatedOn" : 1658962213127, "version" : "8.1.0.0", "vrn" : null, "eventName" : "OnVidmSearchUserGrpSuccess", "currentState" : null, "eventArgument" : "{\"componentSpec\":{\"name\":\"componentSpec\",\"type\":\"com.vmware.vrealize.lcm.domain.ComponentDeploymentSpecification\",\"value\":\"{\\\"component\\\":{\\\"symbolicName\\\":\\\"searchusergrp\\\",\\\"type\\\":null,\\\"componentVersion\\\":null,\\\"properties\\\":{\\\"vidmSearchUserRequestDTO\\\":\\\"{\\\\\\\"vidmHost\\\\\\\":\\\\\\\"idm.cap.org\\\\\\\",\\\\\\\"vidmTenant\\\\\\\":null,\\\\\\\"useServiceClient\\\\\\\":false,\\\\\\\"isTenantConfiguredByPath\\\\\\\":false,\\\\\\\"vidmAdminUser\\\\\\\":\\\\\\\"admin\\\\\\\",\\\\\\\"vidmAdminPassword\\\\\\\":\\\\\\\"JXJXJXJX\\\\\\\",\\\\\\\"vidmOAuthServiceClientId\\\\\\\":\\\\\\\"Service__OAuth2Client\\\\\\\",\\\\\\\"vidmOAuthServiceClientSecret\\\\\\\":\\\\\\\"JXJXJXJX\\\\\\\",\\\\\\\"vidmDomainName\\\\\\\":\\\\\\\"cap.org\\\\\\\",\\\\\\\"baseTenantHostname\\\\\\\":KXKXKXKX,\\\\\\\"requestId\\\\\\\":null,\\\\\\\"searchString\\\\\\\":\\\\\\\"cap\\\\\\\"}\\\",\\\"isVcfUser\\\":\\\"false\\\",\\\"hostName\\\":\\\"idm.cap.org\\\",\\\"vidmTenant\\\":null,\\\"useServiceClient\\\":\\\"true\\\",\\\"__isTenantByPath\\\":\\\"false\\\",\\\"vidmOAuthServiceClientId\\\":\\\"Service__OAuth2Client\\\",\\\"vidmOAuthServiceClientSecret\\\":\\\"JXJXJXJX\\\",\\\"vidmAdminUser\\\":\\\"admin\\\",\\\"vidmAdminPassword\\\":\\\"JXJXJXJX\\\",\\\"vidmDomainName\\\":\\\"cap.org\\\",\\\"vidmBaseTenantHostname\\\":KXKXKXKX,\\\"searchString\\\":\\\"cap\\\"}},\\\"priority\\\":0}\"}}", "status" : "CREATED", "stateMachineInstance" : "556b76d2-a8a0-4489-a382-c13f565d6d5c", "errorCause" : null, "sequence" : 563259, "eventLock" : 1, "engineNodeId" : "lcm.cap.org" } ### Role Mapping being performed ### 2022-07-27 22:50:34.634 INFO [http-nio-8080-exec-7] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Entity : Group [displayName=capadmins@cap.org, groupType=EXTERNAL, providerIdentifier=7e8dbd36-da3b-4277-a42a-f3a3c5893faa, domain=cap.org, isDisabled=false, groupMetadata={"distinguishedName":"CN=capadmins,CN=Users,DC=cap,DC=org","externalId":"05da97d4-1269-48a2-94e9-1b7e4e4c9ea5","additionalMeta":[]}] 2022-07-27 22:50:35.223 INFO [http-nio-8080-exec-7] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping Entity : GroupRoleMapping [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=65da899f-8483-426c-a2a6-1cb5eb53260a] 2022-07-27 22:50:35.321 INFO [http-nio-8080-exec-7] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping Entity : GroupRoleMapping [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=d5fea331-6576-407f-82b3-fd115541e059] 2022-07-27 22:50:35.322 INFO [http-nio-8080-exec-7] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping Entity : GroupRoleMapping [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=eed92b61-31d2-4024-b550-a008e10c4c8d] 2022-07-27 22:50:35.323 INFO [http-nio-8080-exec-7] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping Entity : GroupRoleMapping [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=f09ef48e-42ef-4613-8646-c62c56730c41] 2022-07-27 22:50:35.369 INFO [http-nio-8080-exec-7] c.v.v.l.c.l.MaskingPrintStream - -- * SYSOUT/SYSERR CAPTURED: -- Created Group vmid : 0d35fb24-84d2-4f5a-8c38-81b32120f08f 2022-07-27 22:50:35.552 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=65da899f-8483-426c-a2a6-1cb5eb53260a] 2022-07-27 22:50:35.552 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=d5fea331-6576-407f-82b3-fd115541e059] 2022-07-27 22:50:35.553 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=eed92b61-31d2-4024-b550-a008e10c4c8d] 2022-07-27 22:50:35.553 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=f09ef48e-42ef-4613-8646-c62c56730c41] 2022-07-27 22:50:35.554 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role DTO : RoleDTO [vmid=65da899f-8483-426c-a2a6-1cb5eb53260a, roleName=Content Developer, roleDescription=Content developer] 2022-07-27 22:50:35.561 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role DTO : RoleDTO [vmid=d5fea331-6576-407f-82b3-fd115541e059, roleName=Content Release Manager, roleDescription=Content Release Manager] 2022-07-27 22:50:35.562 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role DTO : RoleDTO [vmid=eed92b61-31d2-4024-b550-a008e10c4c8d, roleName=LCM Cloud Admin, roleDescription=vRealize Lifecycle Manager Cloud Admin] 2022-07-27 22:50:35.563 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role DTO : RoleDTO [vmid=f09ef48e-42ef-4613-8646-c62c56730c41, roleName=Certificate Administrator, roleDescription=Administrator for Certificate operations] 2022-07-27 22:50:35.564 INFO [http-nio-8080-exec-6] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group DTO : GroupDTO [vmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, displayName=capadmins@cap.org, groupType=EXTERNAL, providerIdentifier=7e8dbd36-da3b-4277-a42a-f3a3c5893faa, domain=cap.org, isDisabled=false, groupMetadata=GroupMetadataDTO [distinguishedName=CN=capadmins,CN=Users,DC=cap,DC=org, externalId=05da97d4-1269-48a2-94e9-1b7e4e4c9ea5, additionalMeta=[]], roleMappings=[RoleDTO [vmid=65da899f-8483-426c-a2a6-1cb5eb53260a, roleName=Content Developer, roleDescription=Content developer], RoleDTO [vmid=d5fea331-6576-407f-82b3-fd115541e059, roleName=Content Release Manager, roleDescription=Content Release Manager], RoleDTO [vmid=eed92b61-31d2-4024-b550-a008e10c4c8d, roleName=LCM Cloud Admin, roleDescription=vRealize Lifecycle Manager Cloud Admin], RoleDTO [vmid=f09ef48e-42ef-4613-8646-c62c56730c41, roleName=Certificate Administrator, roleDescription=Administrator for Certificate operations]]] I would now use one of the members of the AD group to login . Since i am using vIDM as my authentication source , I'll switch to it than local user and then click on "LOGIN WITH IDENTITY MANAGER" Have 2 domains and i'll be using the first one that's the CAP.ORG , as the group where the permissions has been assigned belongs to this domain User logs in So Authentication and Authorization are now complete Checking or trying to understand the login sequence from logs perspective ### Password based authentication begins by connector as soon as you click on sign in after entering username and password ### ### Reference: connector.log ( vidm ) ### 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : email 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - User Email attribute : 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - outside if : email HIDDEN 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : userInput 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - outside if : userInput HIDDEN 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : username 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : password 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : forgotPasswd 2022-07-27T23:09:13,502 INFO (Thread-10) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - attribute : signIn 2022-07-27T23:09:29,395 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.directory.ldap.LdapDirectoryService - Password-based authentication: arun@cap.org - BEGIN 2022-07-27T23:09:29,433 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.directory.ldap.dc.service.context.JNDIContextFetcher - LDAP Context env Json Values: { "java.naming.factory.initial" : "com.sun.jndi.ldap.LdapCtxFactory", "javax.security.sasl.server.authentication" : "true", "com.sun.jndi.ldap.connect.timeout" : "5000", "java.naming.ldap.attributes.binary" : "objectGUID pae-IconData objectSid securityIdentifier", "javax.security.sasl.strength" : "high,medium,low", "javax.security.sasl.qop" : "auth-conf,auth-int,auth", "com.sun.jndi.ldap.read.timeout" : "600000", "java.naming.provider.url" : "ldap://ad.cap.org:389", "java.naming.security.authentication" : "GSSAPI" } ### Password based authentication is now successful ### 2022-07-27T23:09:29,443 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.directory.ldap.LdapDirectoryService - Password-based authentication: arun@cap.org - SUCCESS ### States login is successful for user: arun ### 2022-07-27T23:09:29,443 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.adapters.passwordAdapter.PasswordIdpAdapter - Login: arun - SUCCESS 2022-07-27T23:09:29,443 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.connector.controller.AdapterLoginController - samlRequestInfo: SamlRequestInfo[acsUrl=https://idm.cap.org/SAAS/auth/saml/response,relayState=dfe41fd6-446a-4945-9a55-91534817100d,nameId=,requestId=_35a6cdf1404211eefc1b8baed576d91b,authnContextClassRefList=[urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport]] 2022-07-27T23:09:29,444 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.connector.controller.IdPInitiatedSSOController - samlRequestInfo: SamlRequestInfo[acsUrl=https://idm.cap.org/SAAS/auth/saml/response,relayState=dfe41fd6-446a-4945-9a55-91534817100d,nameId=,requestId=_35a6cdf1404211eefc1b8baed576d91b,authnContextClassRefList=[urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport]] -------------------------------------------------------------------------- ### horizon.log in vIDM states login succeeded after connector confirms it ### ### Reference: horizon.log ### 2022-07-27T23:09:30,131 INFO (Thread-3) [IDM;-;10.104.68.224;] com.vmware.horizon.components.authentication.monitoring.LoginMetricsPublisher - Login succeeded. -------------------------------------------------------------------------- ### Reference: vmware_vrlcm.log ( lcm ) ### ### Once horizon confirms authentication for user arun is successful , vRSLCM detects that there is an incoming token ### 2022-07-27 23:09:30.583 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.VMwareUserAuthenticationConverter - -- UserAuthenticationConverter Incoming token : {jti=2396d4fc-69d7-442e-845c-05e77eb3bc88, prn=arun@IDM, domain=cap.org, user_id=87, auth_time=1658963370, iss=https://idm.cap.org/SAAS/auth, aud=https://idm.cap.org/SAAS/auth/oauthtoken, ctx=[{"mtd":"urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport","iat":KXKXKXKX,"id":15}], scp=admin user, idp=0, eml=arun@cap.org, cid=vRLCMOAuth2client3c59ac4aefcf4301931942bb58277d95, did=, wid=, rules={expiry=1658965170, rules=[{resources=[*], actions=[acs:readRuleSets, dm:read, ug:read, ent:read, ctg:read, tnts:read, rpt:*], conditions=null}], link=https://idm.cap.org:443/acs/rules/me}, exp=1659568170, iat=1658963370, sub=91fb23fd-6ce1-4f69-a556-ce2ceffbef4a, prn_type=USER} ### API response is deciphered , which has all properties of the user , the memberships he has and properties of the user object in AD ### 2022-07-27 23:09:30.678 INFO [http-nio-8080-exec-2] c.v.v.l.u.RestHelper - -- RestHelper execute methode connection.getResponseCode : 200 2022-07-27 23:09:30.682 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.VMwareUserAuthenticationConverter - -- Current Authenticated user info API Response status : 200 Response data : {"schemas":["urn:scim:schemas:core:1.0","urn:scim:schemas:extension:workspace:1.0","urn:scim:schemas:extension:enterprise:1.0","urn:scim:schemas:extension:workspace:mfa:1.0"],"externalId":"89df3116-462b-4794-94ea-a0fed01772b6","active":true,"userName":"arun","id":"91fb23fd-6ce1-4f69-a556-ce2ceffbef4a","meta":{"created":"2021-12-07T05:39:56.929Z","lastModified":"2022-03-02T00:56:29.730Z","location":"https://idm.cap.org/SAAS/jersey/manager/api/scim/Users/91fb23fd-6ce1-4f69-a556-ce2ceffbef4a","version":"W/\"1646182589730\""},"name":{"givenName":"Arun","familyName":"Nukula"},"emails":[{"value":"arun@cap.org"}],"phoneNumbers":[{"value":""}],"groups":[{"value":"237386ee-7f61-4d3a-93fa-1569d4bf673a","type":"direct","display":"ALL USERS"},{"value":"7e8dbd36-da3b-4277-a42a-f3a3c5893faa","type":"direct","display":"capadmins@cap.org"}],"roles":[{"value":"84a56b68-f8d5-4b9e-a365-92ef2adb3fb3","display":"User"},{"value":"55048dee-fe1b-404a-936d-3e0b86a7209e","display":"Administrator"}],"urn:scim:schemas:extension:workspace:1.0":{"internalUserType":"PROVISIONED","distinguishedName":"CN=Arun Nukula,CN=Users,DC=cap,DC=org","userStatus":"1","domain":"cap.org","userStoreUuid":"3d7e1efd-2589-4fed-b86d-105d076cdbda","externalUserDisabled":false,"userPrincipalName":"arun@cap.org"}} ### Group to Role mapping is performed. What we've seen till now in authentication , now it's time for authorization ### 2022-07-27 23:09:30.691 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=65da899f-8483-426c-a2a6-1cb5eb53260a] 2022-07-27 23:09:30.705 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=d5fea331-6576-407f-82b3-fd115541e059] 2022-07-27 23:09:30.706 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=eed92b61-31d2-4024-b550-a008e10c4c8d] 2022-07-27 23:09:30.706 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Role Mapping DTO : GroupRoleMappingDTO [groupvmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, rolevmid=f09ef48e-42ef-4613-8646-c62c56730c41] 2022-07-27 23:09:30.707 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role Extended DTO : RoleExDTO [vmid=65da899f-8483-426c-a2a6-1cb5eb53260a, roleName=Content Developer, roleDescription=Content developer, authorities=CONTENT_DEVELOPER, isInternal=false] 2022-07-27 23:09:30.714 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role Extended DTO : RoleExDTO [vmid=d5fea331-6576-407f-82b3-fd115541e059, roleName=Content Release Manager, roleDescription=Content Release Manager, authorities=RELEASE_MANAGER, isInternal=false] 2022-07-27 23:09:30.715 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role Extended DTO : RoleExDTO [vmid=eed92b61-31d2-4024-b550-a008e10c4c8d, roleName=LCM Cloud Admin, roleDescription=vRealize Lifecycle Manager Cloud Admin, authorities=LCM_CLOUD_ADMIN, isInternal=false] 2022-07-27 23:09:30.715 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Role Extended DTO : RoleExDTO [vmid=f09ef48e-42ef-4613-8646-c62c56730c41, roleName=Certificate Administrator, roleDescription=Administrator for Certificate operations, authorities=LOCKER_CERTIFICATE_ADMIN, isInternal=false] ### It identifies that the group has following roles given ### 2022-07-27 23:09:30.716 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.AuthznCustomObjectMapper - -- Group Extended DTO : GroupExDTO [vmid=0d35fb24-84d2-4f5a-8c38-81b32120f08f, displayName=capadmins@cap.org, groupType=EXTERNAL, providerIdentifier=7e8dbd36-da3b-4277-a42a-f3a3c5893faa, domain=cap.org, isDisabled=false, groupMetadata=GroupMetadataDTO [distinguishedName=CN=capadmins,CN=Users,DC=cap,DC=org, externalId=05da97d4-1269-48a2-94e9-1b7e4e4c9ea5, additionalMeta=[]], roleMappings=[RoleExDTO [vmid=65da899f-8483-426c-a2a6-1cb5eb53260a, roleName=Content Developer, roleDescription=Content developer, authorities=CONTENT_DEVELOPER, isInternal=false], RoleExDTO [vmid=d5fea331-6576-407f-82b3-fd115541e059, roleName=Content Release Manager, roleDescription=Content Release Manager, authorities=RELEASE_MANAGER, isInternal=false], RoleExDTO [vmid=eed92b61-31d2-4024-b550-a008e10c4c8d, roleName=LCM Cloud Admin, roleDescription=vRealize Lifecycle Manager Cloud Admin, authorities=LCM_CLOUD_ADMIN, isInternal=false], RoleExDTO [vmid=f09ef48e-42ef-4613-8646-c62c56730c41, roleName=Certificate Administrator, roleDescription=Administrator for Certificate operations, authorities=LOCKER_CERTIFICATE_ADMIN, isInternal=false]]] ### All authorities or roles for the user are declared or shown below ### 2022-07-27 23:09:30.721 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.VMwareUserAuthenticationConverter - -- All Authorities of Current Authenticated user : [CONTENT_DEVELOPER, RELEASE_MANAGER, LCM_CLOUD_ADMIN, LOCKER_CERTIFICATE_ADMIN] 2022-07-27 23:09:30.721 INFO [http-nio-8080-exec-2] c.v.v.l.a.c.VMwareUserAuthenticationConverter - -- Authenticated Principal : arun@IDM##cap.org##Arun Nukula Trimmed username : arun Domain : cap.org Display Name : Arun Nukula 2022-07-27 23:09:32.612 INFO [http-nio-8080-exec-3] c.v.v.l.r.s.RequestServiceImpl - -- Authentication object is not null org.springframework.security.oauth2.provider.OAuth2Authentication@5cd44a9d: Principal: arun@IDM##cap.org##Arun Nukula; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=10.104.68.224, sessionId=, tokenType=BearertokenValue=; Granted Authorities: CONTENT_DEVELOPER, RELEASE_MANAGER, LCM_CLOUD_ADMIN, LOCKER_CERTIFICATE_ADMIN 2022-07-27 23:09:32.622 INFO [http-nio-8080-exec-3] c.v.v.l.l.u.RequestSubmissionUtil - -- Generic Request Response : { "requestId" : "ca78956f-83e9-4d61-a52c-85b9f148e2b3" } 2022-07-27 23:09:32.651 INFO [http-nio-8080-exec-9] c.v.v.l.r.s.RequestServiceImpl - -- Authentication object is not null org.springframework.security.oauth2.provider.OAuth2Authentication@5cd44a9d: Principal: arun@IDM##cap.org##Arun Nukula; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=10.104.68.224, sessionId=, tokenType=BearertokenValue=; Granted Authorities: CONTENT_DEVELOPER, RELEASE_MANAGER, LCM_CLOUD_ADMIN, LOCKER_CERTIFICATE_ADMIN 2022-07-27 23:09:32.663 INFO [http-nio-8080-exec-4] c.v.v.l.a.c.AuthznCustomObjectMapper - -- User Extended DTO : UserDTO [vmid=caa4d554-2dbf-45a9-b070-15b09fd76c7d, username=serviceadmin@local, password=KXKXKXKX, userType=LCM_LOCAL_USER, displayName=LCM Service Admin, providerIdentifier=null, domain=LCM Local, isDisabled=false, userPrincipalName=null, userMetadata=null, roleMappings=[RoleExDTO [vmid=964b87a9-aae8-4f1c-bd77-2fabfb7c69a5, roleName=LCM Service Admin, roleDescription=vRealize Lifecycle Manager Service Admin, authorities=LCM_SERVICE_ADMIN, isInternal=true]]] ### Confirms authentication or login is completed ### 2022-07-27 23:10:33.082 INFO [http-nio-8080-exec-9] c.v.v.l.s.n.s.NotificationServiceImpl - -- Authentication object is not null org.springframework.security.oauth2.provider.OAuth2Authentication@5cd44a9d: Principal: arun@IDM##cap.org##Arun Nukula; Credentials: [PROTECTED]; Authenticated: true Checking or trying to understand the logout sequence from logs perspective ### vmware_vrlcm.log ### ### Invalidates the access token when a user logsout. That's it ### 2022-07-27 23:29:36.197 INFO [http-nio-8080-exec-5] c.v.v.l.a.c.CustomLogoutSuccessHandler - -- Invaldiating vIDM access token. vIDM Logout url : https://idm.cap.org/SAAS/auth/logout?dest=https://lcm.cap.org/login

Introduction vRealize LogInsight does not use an external load balancer for balancing load between nodes which are part of vRLI cluster External load balancer is not supported. Log Insight features an Integrated Load Balancer (ILB) which supports one or more Virtual IP Address (VIPs). Each VIP balances incoming ingestion and query traffic fairly among available Log Insight nodes. Each VIP also ensures that incoming ingestion and query traffic is accepted even if some Log Insight nodes become unavailable. It is recommended that all Log Insight clients, using the web user interface and/or ingestion (via Syslog or the API), connect to Log Insight via a VIP defined below and not directly to a node. Please refer to the section "Working with an Integrated Load Balancer" of the Online Help I have deployed a single node vRealize LogInsight in my lab through vRSLCM Since , I have not configured VIP or there it's not a Cluster yet. Under Product properties you would see "Configure Cluster VIP" set to false Below screenshot shows you the appliance properties , where the VM Name , FQDN and the IP Address of the appliance is shown along with the vCenter where it's placed etc... Configure VIP or Integrated Load Balancer for vRealize LogInsight Login into vRealize LogInsight 8.x , navigate to cluster under management Here you would see all of the nodes which are part of cluster if it's already configured. If it's not then you would see a standalone node. This is the pane where you can configure integrated load balancer for vRLi I do have an IP which has been reserved for vRLI VIP or vRLI ILB , I have also created a DNS record for resolution purposes Now , we shall go ahead and click on " New Virtual IP Address " as shown below Enter the IP and then the FQDN of the VIP. Tags are not mandatory Click on Save , it will start configuring the VIP or ILB Once completed , status will be flipped to "Available" Since this vRealize LogInsight is managed by vRSLCM , now go ahead and perform an inventory sync to reflect cluster properties on vRLI product Since the Inventory Sync is now complete , if we check the product properties now you would see vRLI cluster IP and then the FQDN too Un-Configure VIP or Integrated Load Balancer for vRealize LogInsight Under vRLI , click on management and cluster , select the VIP and then delete it Perform Inventory Sync to refresh product properties on vRSLCM which would remove As you can see the cluster properties are now removed

There's a scenario where /storage partition is full. This is the one which hosts database which is used by vRSLCM 8.x In this scenarion , application would not be available and neither you can connect to postgres database What do you do then ? Execute command pvdisplay pvdisplay allows you to see the attributes of one or more physical volumes like size, physical extent size, space used for the volume group descriptor area and so on root@lcm [ ~ ]# pvdisplay --- Physical volume --- PV Name /dev/sdb VG Name data_vg PV Size <150.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 38399 Free PE 0 Allocated PE 38399 PV UUID zyOl4J-z4kj-sG5N-9ZRM-2zgR-Nk0L-bAj0HG --- Physical volume --- PV Name /dev/sdc VG Name stroage_vg PV Size <10.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 2559 Free PE 0 Allocated PE 2559 PV UUID nfAT0l-8gek-gJBm-hEop-DWd1-kGxp-tBm6Kl --- Physical volume --- PV Name /dev/sdd VG Name swap_vg PV Size <8.00 GiB / not usable 0 Allocatable yes (but full) PE Size 4.00 MiB Total PE 2047 Free PE 0 Allocated PE 2047 PV UUID DN2RgK-3Fn5-jEf0-BvkK-3utn-enX2-z40mZK Execute command lvdisplay The lvdisplay command displays logical volume properties (such as size, layout, and mapping) in a fixed format root@lcm [ ~ ]# lvdisplay --- Logical volume --- LV Path /dev/data_vg/data LV Name data VG Name data_vg LV UUID GfSxfD-juGP-HAtH-liAq-0h37-6zcR-HN4n3E LV Write Access read/write LV Creation host, time photon-machine, 2021-10-08 18:55:37 +0000 LV Status available # open 1 LV Size <150.00 GiB Current LE 38399 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:1 --- Logical volume --- LV Path /dev/stroage_vg/storage LV Name storage VG Name stroage_vg LV UUID X5D8wB-ua1P-A8qe-ge3O-2Vu8-STpm-zQydUx LV Write Access read/write LV Creation host, time photon-machine, 2021-10-08 18:56:27 +0000 LV Status available # open 1 LV Size <10.00 GiB Current LE 2559 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2 --- Logical volume --- LV Path /dev/swap_vg/swap1 LV Name swap1 VG Name swap_vg LV UUID U3Syes-Ud5j-N47U-yLCf-OaC4-qkb0-QfPL0p LV Write Access read/write LV Creation host, time photon-machine, 2021-10-08 18:56:46 +0000 LV Status available # open 2 LV Size <8.00 GiB Current LE 2047 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:0 From vCenter if you try to inspect disk layout If i go by the above data , my /storage is /dev/sdc which means if i have to increase /storage size , all i have to do is to go ahead and increase the disk size on the vCenter and then reboot appliance Let's try the procedure Before trying the procedure , here's the current disk space available root@lcm [ ~ ]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 3.0G 20K 3.0G 1% /dev/shm tmpfs 3.0G 1.1M 3.0G 1% /run tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup /dev/sda4 8.7G 3.3G 5.0G 40% / tmpfs 3.0G 28M 2.9G 1% /tmp /dev/sda2 119M 28M 85M 25% /boot /dev/mapper/stroage_vg-storage 9.8G 521M 8.8G 6% /storage /dev/mapper/data_vg-data 148G 42G 100G 30% /data tmpfs 595M 0 595M 0% /run/user/0 Procedure Increase the disk size to 15G as compared to 10G at the moment Once you change the size of the volume from vCenter , reboot the vRSLCM appliance Execute journalctl -x to inspect resizing mechanism Sep 29 00:53:03 lcm.cap.org vaos[943]: Thu Sep 29 00:53:03 UTC 2022 Disk Util: INFO: LV Resizing /dev/stroage_vg/storage Sep 29 00:53:03 lcm.cap.org vaos[943]: Size of logical volume stroage_vg/storage changed from <10.00 GiB (2559 extents) to <15.00 GiB (3839 extents). Sep 29 00:53:04 lcm.cap.org vaos[943]: Logical volume stroage_vg/storage successfully resized. Sep 29 00:53:04 lcm.cap.org vaos[943]: resize2fs 1.45.5 (07-Jan-2020) Sep 29 00:53:04 lcm.cap.org kernel: EXT4-fs (dm-2): resizing filesystem from 2620416 to 3931136 blocks Sep 29 00:53:05 lcm.cap.org rsyslogd[713]: imjournal: journal files changed, reloading... [v8.2202.0 try https://www.rsyslog.com/e/0 ] Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: 2022-09-29 00:53:05,329 main ERROR Unable to locate appender "MaskedLogs" for logger config "root" Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: . ____ _ __ _ _ Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: \\/ ___)| |_)| | | | | || (_| | ) ) ) ) Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: ' |____| .__|_| |_|_| |_\__, | / / / / Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: =========|_|==============|___/=/_/_/_/ Sep 29 00:53:05 lcm.cap.org launch-blackstone-spring[944]: :: Spring Boot :: (v2.1.16.RELEASE) Sep 29 00:53:07 lcm.cap.org launch-blackstone-spring[944]: 2022-09-29 00:53:07.150 INFO lcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Starting BlackstoneExternalApplication on lcm.cap.org with PID 962 (/opt/vmware/vlcm/blackstone/spring-common/blac> Sep 29 00:53:07 lcm.cap.org launch-blackstone-spring[944]: 2022-09-29 00:53:07.167 DEBUG lcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Running with Spring Boot v2.1.16.RELEASE, Spring v5.1.17.RELEASE Sep 29 00:53:07 lcm.cap.org launch-blackstone-spring[944]: 2022-09-29 00:53:07.171 INFO lcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStartupProfileInfo] : No active profile set, falling back to default profiles: default Sep 29 00:53:07 lcm.cap.org kernel: EXT4-fs (dm-2): resized filesystem to 3931136 Sep 29 00:53:07 lcm.cap.org vaos[943]: Filesystem at /dev/mapper/stroage_vg-storage is mounted on /storage; on-line resizing required Sep 29 00:53:07 lcm.cap.org vaos[943]: old_desc_blocks = 1, new_desc_blocks = 1 Sep 29 00:53:07 lcm.cap.org vaos[943]: The filesystem on /dev/mapper/stroage_vg-storage is now 3931136 (4k) blocks long. * * * * Sep 29 00:53:07 lcm.cap.org vaos[943]: + log '/etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0' Sep 29 00:53:07 lcm.cap.org vaos[943]: ++ date '+%Y-%m-%d %H:%M:%S' Sep 29 00:53:07 lcm.cap.org vaos[943]: + echo '2022-09-29 00:53:07 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0' Sep 29 00:53:07 lcm.cap.org vaos[943]: 2022-09-29 00:53:07 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0 Sep 29 00:53:07 lcm.cap.org vaos[943]: + log 'main bootstrap everyboot done' Sep 29 00:53:07 lcm.cap.org vaos[943]: ++ date '+%Y-%m-%d %H:%M:%S' Sep 29 00:53:07 lcm.cap.org vaos[943]: + echo '2022-09-29 00:53:07 main bootstrap everyboot done' Sep 29 00:53:07 lcm.cap.org vaos[943]: 2022-09-29 00:53:07 main bootstrap everyboot done When you reboot , the autogrow script detects the change in the logical volume and increases the size automatically Now if i go ahead and execute df -h , i should see the new disk size root@lcm [ ~ ]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 3.0G 20K 3.0G 1% /dev/shm tmpfs 3.0G 1.1M 3.0G 1% /run tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup /dev/sda4 8.7G 3.3G 5.0G 40% / tmpfs 3.0G 9.3M 2.9G 1% /tmp /dev/sda2 119M 28M 85M 25% /boot /dev/mapper/stroage_vg-storage 15G 521M 14G 4% /storage /dev/mapper/data_vg-data 148G 42G 100G 30% /data tmpfs 595M 0 595M 0% /run/user/0 So now since i have made some room for my application to start appropriately , i'll go ahead and perform any maintanence needed on db or any other component as needed