Configuring MYVMware Account in vRSLCM via API

Posted on 29-02-2020 by Manish Jha

One of the method of installing vRealize products via vRSLCM is to configure myvmw repository first and then pulling available product binaries via internet. In this post I will walk through steps of configuring the same via API.

1: Add myvmw credentials to password Store

Method: POST

URL: https://<vrslcm-fqdn>/lcm/locker/api/passwords

Sample Payload:

{
   "vmid":"null",
   "alias":"vstellar-myvmw-account",
   "userName":"xyz@vmware.com",
   "password":"xxxxx"
}

Method: POST

URL: https://<vrslcm-fqdn>/lcm/locker/api/passwords

Sample Payload:

{

"vmid":"null",

"alias":"vstellar-myvmw-account",

"userName":"xyz@vmware.com",

"password":"xxxxx"

}

2: Fetch vmid associated with alias created in step-1: When a new password is added to locker store, vRSLCM assigns a unique vmid to that password and all future references to this password is made via assigned vmid.

Method: GET

URL: https://<vrslcm-fqdn>/lcm/locker/api/passwords

Method: GET

URL: https://<vrslcm-fqdn>/lcm/locker/api/passwords

Sample Output

{
   "vmid":"b19479ed-40cb-4441-a95d-81e4570ad0a8",
   "alias":"vstellar-myvmw-account",
   "userName":"xyz@vmware.com",

vRLI Distributed Install/Upgrade via vRSLCM API

Posted on 29-02-2020 by Manish Jha

In my last Post I demonstrated how to install and upgrade a distributed vROPs via vRSLCM API. In this post I will walk through how to perform install/upgrade a distributed vRLI environment.

Steps for deploying/upgrading any vRealize product via vRSLCM API are pretty much same, only the json payload varies.

vRLI Deployment Procedure

Step 1: Pre-Validate Environment Creation

Method: POST

URL: https://<vrslcm-fqdn>/lcm/lcops/api/environments/import/prevalidate

Sample Payload:

{
   "requestId":"null",
   "requestType":"VALIDATE_CREATE_ENVIRONMENT",
   "environmentRequestDTO":{
      "environmentId":"vRLI-4.8-Distributed",
      "environmentName":"vRLI-4.8-Distributed",
      "infrastructure":{
         "properties":{
            "dataCenterName":"SDDC-MAAS",
            "regionName":"default",
            "zoneName":"default",
            "vCenterName":"vcenter.mgmt.vmw",
            "vCenterHost":"vcenter.mgmt.vmw",
            "vcUsername":"administrator@vsphere.local",
            "vcPassword":"locker:password:e1dfebff-4600-4439-afb5-851e1830a71e:VC-Password",
            "acceptEULA":"true",
            "enableTelemetry":"false",
            "adminEmail":"xyz@vmware.com",
            "defaultPassword":"locker:password:26c77689-e7a8-4f27-8c85-c9a51a77689c:Default-Password",
            "certificate":"locker:certificate:f2558190-2002-46e2-847f-eb83c6c110be:vRLI-Certs",
            "cluster":"MGMT_DC#MGMT_CLU",
            "storage":"vsanDatastore",
            "folderName":"group-v50(MGMT_VMs)",
            "resourcePool":"resgroup-43(MGMT-ResourcePool)",
            "diskMode":"thin",
            "network":"VM_MGMT",
            "masterVidmEnabled":"true",
            "dns":"x.x.x.5",
            "domain":"mgmt.vmw",
            "gateway":"x.x.x.1",
            "netmask":"255.255.255.0",
            "searchpath":"mgmt.vmw",
            "timeSyncMode":"ntp",
            "ntp":"x.x.x.x",
            "isDhcp":"false"
         }
      },
      "products":[
         {
            "id":"vrli",
            "version":"4.8.0",
            "properties":{
               "certificate":"locker:certificate:f2558190-2002-46e2-847f-eb83c6c110be:vRLI-Certs",
               "productPassword":"locker:password:26c77689-e7a8-4f27-8c85-c9a51a77689c:Default-Password",
               "licenseRef":"locker:license:84727216-1e61-4694-bea9-4b19a5969e20:vRLI-4.x",
               "nodeSize":"small",
               "configureClusterVIP":"true",
               "affinityRule":true,
               "configureAffinitySeparateAll":"true",
               "ntp":"x.x.x.x",
               "timeSyncMode":"ntp"
            },
            "clusterVIP":{
               "clusterVips":[
                  {
                     "type":"vrli-cluster-1",
                     "properties":{
                        "hostName":"vrli.mgmt.vmw",
                        "ip":"x.x.x.110"
                     }
                  }
               ]
            },
            "nodes":[
               {
                  "type":"vrli-master",
                  "properties":{
                     "vmName":"vrli-master",
                     "hostName":"vrli01.mgmt.vmw",
                     "ip":"x.x.x.111"
                  }
               },
               {
                  "type":"vrli-worker",
                  "properties":{
                     "vmName":"vrli-worker-1",
                     "hostName":"vrli02.mgmt.vmw",
                     "ip":"x.x.x.112"
                  }
               },
               {
                  "type":"vrli-worker",
                  "properties":{
                     "vmName":"vrli-worker-2",
                     "hostName":"vrli03.mgmt.vmw",
                     "ip":"x.x.x.113"
                  }
               }
            ]
         }
      ]
   }
}

Method: POST

URL: https://<vrslcm-fqdn>/lcm/lcops/api/environments/import/prevalidate

Sample Payload:

{

"requestId":"null",

"requestType":"VALIDATE_CREATE_ENVIRONMENT",

"environmentRequestDTO":{

"environmentId":"vRLI-4.8-Distributed",

"environmentName":"vRLI-4.8-Distributed",

"infrastructure":{

"properties":{

"dataCenterName":"SDDC-MAAS",

"regionName":"default",

"zoneName":"default",

"vCenterName":"vcenter.mgmt.vmw"

vROPs Distributed Install/Upgrade via vRSLCM API

Posted on 27-02-2020 by Manish Jha

vRSLCM is such a great tool that it lifts all the complexity of deploying vRealize suite in just few clicks. Whether you are looking for standalone deployment or a distributed one, you are shielded from all the complexity that goes behind in setting up an environment.

Recently while working on my new project, I was tasked to find out a way where all the UI operations related to vRSLCM can be automated. In my last post I listed all the API’s that are needed to perform end to end vRSLCM configuration. We need to fetch few details before starting install/upgrade of any vRealize product.

This post is extension to my last post and I will be demonstrating how to deploy/upgrade various vRealize products using vRSLCM API. The first in this list will be vROPs. So lets get started.

At this point, I assume you have already fetched details about:

Certificate Name/UUID (From Locker)
Default Password Name/UUID (From Locker)
License Name/UUID (From Locker)
Infra details (DNS, NTP, Datacenter name, cluster name etc)
Local Repo configured and all product install/upgrade binaries uploaded there.

Automating vRSLCM 8.x End to End Configuration via API

Posted on 23-02-2020 by Manish Jha

In this post we will learn how to leverage vRealize Suite Life Cycle Manager (vRSLCM) API to automated deployment & configuration.

With release of vRSLCM 8.x, VMware introduced simple installer (similar to vCSA) for deployment of vRSLCM. Below is screenshot of how the simple installer looks like.

As of now we don’t have any API which can be leveraged to automate appliance deployment, so we will perform this task via ovftool.

Deploying vRSLCM via ovftool

ovftool --name=vrslcm2.mgmt.vmw --X:injectOvfEnv --X:logFile=ovftool.log --allowExtraConfig --noSSLVerify --datastore=vsanDatastore --network=VM_MGMT --acceptAllEulas --diskMode=thin --powerOn --prop:vami.hostname=vrslcm2.mgmt.vmw --prop:varoot-password=XXXXX --prop:va-ssh-enabled=True --prop:va-firstboot-enabled=True --prop:va-telemetry-enabled=True --prop:va-ntp-servers=x.x.x.x --prop:vami.gateway.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=x.x.x.x --prop:vami.domain.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=mgmt.vmw --prop:vami.searchpath.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=mgmt.vmw --prop:vami.DNS.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=x.x.x.x --prop:vami.ip0.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=x.x.x.x --prop:vami.netmask0.VMware_vRealize_Suite_Life_Cycle_Manager_Appliance=255.255.255.0 C:UsersAdministratorDownloadsvra-lcm-installer-14878991vrlcmVMware-vLCM-Appliance-8.0.0.16-14878959_OVF10.ova vi://root@esxmb4.mgmt.vmw/

1	ovftool --name=vrslcm2.mgmt.vmw --X:injectOvfEnv --X:logFile=ovftool.log --allowExtraConfig --noSSLVerify --datastore=vsanDatastore --network=VM_MGMT --acceptAllEulas --diskMode=thin --powerOn --prop:vami.hostname=vrslcm2.

Getting Started With vROPs Tenant App For vCloud Director 10.x

Posted on 23-02-2020 by Manish Jha

In this post, I will walk through step by step installation for the vRealize Operations Manager Tenant App for vCloud Director. But before I jump into the lab, I want to take a moment to explain what this solution is all about and what it looks like from an architectural point of view.

What is vROPs Tenant App for vCloud Director?

vROPs Tenant App is a solution that helps in exposing vRops performance metrics to tenants in a vCD environment. Each tenant can only see metrics data relevant to their organization.

From a service provider point of view, this is an awesome solution as Tenant App enables tenants to have complete visibility of performance metrics of their environment. If an environment is not performing as per expectations, tenants can leverage this solution to root cause analysis of performance issues and they can perform L1-L2 level of maintenance/troubleshooting tasks themselves without raising service tickets with service providers. … Read More

How To Update/Patch Multi Cell vCD 10.x Environment

Posted on 17-02-2020 by Manish Jha

In this post we will learn how to patch/update a Multi cell vCD 10.x environment.

Note: Above steps are for updating vCD from one build to another (patch release) within same version. Please do not confuse this with upgrading a vCD deployment where we jump from one major version to another.

I will breakup this post in 4 sections:

Pre Update Checks.
vCD Update Process.
Post Update Checks.
Post Update Tasks.

Pre Update Checks

There are number of checks which must be performed before attempting to update a vCD environment.

1: vCD Health Check & Primary Node identification: Before updating multi cell vCD environment, please ensure all vCD cells in server group are healthy and functioning correctly.

Also we need to identify vCD primary node as we will be needing this info later when we will be taking backup of the embedded database. To fetch this info we can make use of vCD Appliance API as shown below:

Method: GET

URL: https://<vcd-fqdn>:5480/api/1.0.0/nodes

Headers: x-vcloud-authorization: auth-token

Response Output:

{
   "localClusterHealth":"HEALTHY",
   "localClusterState":[
      {
         "connectionString":"host=192.168.12.11 user=repmgr dbname=repmgr",
         "id":16390,
         "location":"default",
         "name":"vcd1",
         "nodeHealth":"HEALTHY",
         "nodeRole":"PRIMARY",
         "role":"primary",
         "status":"* running",
         "upstream":""
      },
      {
         "connectionString":"host=192.168.12.13 user=repmgr dbname=repmgr",
         "id":25984,
         "location":"default",
         "name":"vcd3",
         "nodeHealth":"HEALTHY",
         "nodeRole":"STANDBY",
         "role":"standby",
         "status":"running",
         "upstream":"vcd1"
      },
      {
         "connectionString":"host=192.168.12.12 user=repmgr dbname=repmgr",
         "id":26349,
         "location":"default",
         "name":"vcd2",
         "nodeHealth":"HEALTHY",
         "nodeRole":"STANDBY",
         "role":"standby",
         "status":"running",
         "upstream":"vcd1"
      }
   ],
   "warnings":[

   ]
}

{

"localClusterHealth":"HEALTHY",

"localClusterState":[

{

"connectionString":"host=192.168.12.11 user=repmgr dbname=repmgr",

"id":16390,

"location":"default",

"name":"vcd1",

"nodeHealth":"HEALTHY",

"nodeRole":"PRIMARY",

"role":"primary",

"status":"* running",

"upstream":""

{

"connectionString":"host=192.168.12.13 user=repmgr dbname=repmgr",

"id":25984,

"location":"default",

"name":"vcd3",

"nodeHealth":"HEALTHY",

"nodeRole":"STANDBY",

"role":"standby",

"status":"running",

"upstream":"vcd1"

{

"connectionString":"host=192.168.12.12 user=repmgr dbname=repmgr",

"id":26349,

"location":"default",

"name":"vcd2",

"nodeHealth":"HEALTHY",

"nodeRole":"STANDBY",

"role":"standby",

"status":"running",

"upstream":"vcd1"

}

"warnings":[

]

}

From the above output we can infer that all 3 vCD nodes are healthy here, cluster health is also healthy and node “vcd1” is the current primary node.… Read More

Spread the Love

Spread the Love

Spread the Love

Spread the Love

What is vROPs Tenant App for vCloud Director?

Spread the Love

Pre Update Checks

Spread the Love