Ahosti.Com
Read trending IT updates for cloud businesses, managed service providers, IT pros & what innovation digital transformation is driving in tech industry.

vIDM 3.3.5 deployment utilizing vRSLCM 8.5 REST API in VCF (4.3.1) Conscious Mode

0 5

A while in the past I described the set up strategy of VMware Identification Supervisor 3.3.0 with vRealize Lifecycle Supervisor 2.1 utilizing Ansible (hyperlink right here). That point the one attainable choice to put in vIDM with vRSLCM was a single node with inner PostgresSQL database. vRSLCM 2.x doesn’t carry out cluster-based installations of VMware Identification Supervisor.

Fortuitously it has modified and now vIDM cluster with three nodes will be deployed with vRSLCM.

Moreover ranging from VCF 4.1, vRSLCM is deployed in a ‘VCF Mode’ which permits the mixing with the SDDC Supervisor stock for product deployment and life cycle administration of vRealize Suite parts and it we are able to deal with binary downloads straight from the SDDC Supervisor UI.

One other profit is that vRSLCM, in VCF Conscious mode, will deploy vRealize Suite parts in line with VVD.

And yet another vital factor: load balancer preparation and configuration are not a prerequisite once you use vRealize Suite Lifecycle Supervisor to deploy or carry out a cluster enlargement on vIDM, vROps, or vRA. Load balancer preparation and configuration happen as a part of the deploy or develop operation.

Anyway, when ‘Create Surroundings’ is requested, the request payload ought to comprise property key, “vcfProperties” inside Infrastructure properties. “vcfProperties” identifies if the atmosphere is VCF enabled or not.



"vcfProperties": "{"vcfEnabled":true,"sddcManagerDetails":[{"sddcManagerHostName":"gre26sdm001.domain.com","sddcManagerName":"default","sddcManagerVmid":"default"}]}"
    }

So the cURL request ought to appear to be under:

dataCenterVmid : VMID which you’re going to get as a response of the datacenter GET request;

locker Gadgets: Locker objects resembling passwords and certificates needs to be created OR present airplane textual content password.

cURL request:

$ curl 'https://vrlscm_fqdn/lcm/lcops/api/v2/environments' -i -X POST 
    -H 'Content material-Sort: utility/json' 
    -H 'Authorization: Fundamental ' 
    -d 
'{
  "environmentId": "globalenvironment",
  "environmentName": "globalenvironment",
  "infrastructure": {
    "properties": {
      "dataCenterVmid": "4ec46533-4472-4df5-944f-be7f6ae544e7",
      "regionName": "",
      "zoneName": "",
      "vCenterName": "gre28vcs001",
      "vCenterHost": "gre28vcs001.area.com",
      "vcUsername": "[email protected]",
      "vcPassword": "locker:password:17572db1-d149-4a4c-ac20-9f04f96bed33:vidm_root",
      "acceptEULA": "true",
      "enableTelemetry": "true",
      "defaultPassword": "locker:password:17572db1-d149-4a4c-ac20-9f04f96bed33:vidm_root",
      "certificates": "locker:certificates:5290b759-d193-4beb-8bcd-ee582284848c:vidm_cluster",
      "cluster": "gre28-m01-dc#gre28-m01-cluster01",
      "storage": "gre28-m01-vsan01",
      "folderName": "",
      "resourcePool": "gre28-m01-sddc-mgmt",
      "diskMode": "skinny",
      "community": "xreg-m01-seg01",
      "masterVidmEnabled": "false",
      "dns": "192.168.10.24,192.168.10.25",
      "area": "area.com",
      "gateway": "192.168.20.1",
      "netmask": "255.255.255.0",
      "searchpath": "area.com",
      "timeSyncMode": "ntp",
      "ntp": "",
      "isDhcp": "false",
      "vcfProperties": "{"vcfEnabled":true,"sddcManagerDetails":[{"sddcManagerHostName":"gre28sdm001.domain.com","sddcManagerName":"default","sddcManagerVmid":"default"}]}"
    }
  },
  "merchandise": [
    {
      "id": "vidm",
      "version": "3.3.5",
      "properties": {
        "vidmAdminPassword": "locker:password:17572db1-d149-4a4c-ac20-9f04f96bed33:vidm_root",
        "syncGroupMembers": true,
        "nodeSize": "large",
        "defaultConfigurationEmail": "[email protected]",
        "defaultConfigurationUsername": "administrator",
        "defaultConfigurationPassword": "locker:password:17572db1-d149-4a4c-ac20-9f04f96bed33:vidm_root",
        "defaultTenantAlias": "",
        "vidmDomainName": "",
        "certificate": "locker:certificate:5290b759-d193-4beb-8bcd-ee582284848c:vidm_cluster",
        "contentLibraryItemId": "",
        "fipsMode": "false"
      },
      "clusterVIP": {
        "clusterVips": [
          {
            "type": "vidm-lb",
            "properties": {
              "hostName": "gre28idm001.domain.com",
              "lockerCertificate": "locker:certificate:5290b759-d193-4beb-8bcd-ee582284848c:vidm_cluster"
            }
          },
          {
            "type": "vidm-delegate",
            "properties": {
              "ip": "192.168.20.115"
            }
          }
        ]
      },
      "nodes": [
        {
          "type": "vidm-primary",
          "properties": {
            "vmName": "gre28idm002",
            "hostName": "gre28idm002.domain.com",
            "ip": "192.168.20.112"
          }
        },
        {
          "type": "vidm-secondary",
          "properties": {
            "vmName": "gre28idm003",
            "hostName": "gre28idm003.domain.com",
            "ip": "192.168.20.113"
          }
        },
        {
          "type": "vidm-secondary",
          "properties": {
            "vmName": "gre28idm004",
            "hostName": "gre28idm004.domain.com",
            "ip": "192.168.20.114"
          }
        }
      ]
    }
  ]
}

vIDM is deployed so lets change to NSX-T and examine how .

And now log in to vIDM cluster.

That’s it 🙂 When you’ve got any questions simply ping me 🙂

You might also like
Loading...