Sunday, June 28, 2020

3 Ways to get VMware Platform Services Controller (PSC) information from vCenter Server 6.5




      From vSphere 6.5, VMware Changes its vCenter architecture by introducing Platform services controller (PSC) by replacing vCenter SSO server. VMware Platform Services Controller (PSC) is a component of the VMware Cloud Infrastructure Suite. PSC deals with identity management for administrators and applications that interact with the vSphere platform.

Below are the Components that are installed with platform Service controller includes:
  • VMware Appliance Management Service (only in Appliance-based PSC)
  • VMware License Service
  • VMware Component Manager
  • VMware Identity Management Service
  • VMware HTTP Reverse Proxy
  • VMware Service Control Agent
  • VMware Security Token Service
  • VMware Common Logging Service
  • VMware Syslog Health Service
  • VMware Authentication Framework
  • VMware Certificate Service
  • VMware Directory Service

vCenter Server Deployment Models:

  • vCenter Server with external Platform Services Controller (Separate appliance or server for PSC & vCenter)
  • vCenter Server with embedded Platform Services Controller (Both PSC & vCenter Server are installed on Single VCSA appliance or VM
In most of the larger enterprises, They will be having hundreds and thousands of  ESXi hosts and also multiple vCenter Servers to manage the ESXi hosts in the virtualized infrastructure. With multiple vCenter Servers in the environment, I even personally feel a bit difficult to identify the servers which are associated with vCenter Servers such as  Platform Services controller, External database servers, and Update Manager.  We need to identify the associated Platform services controller before Upgrading vCenter Server. This is essentially important when performing vCenter upgrade and troubleshooting purposes.

1. Get Platform Service Controller from vSphere Web Client

Log in to vCenter Server using vSphere Web Client -> Click on Home -> select Administration -> System Configuration -> Nodes. Select to nodes to understand the deployment type of the node.

2. Get Platform Services Controller from vCenter Advanced Settings

Log in to vCenter Server using vSphere Web Client -> Click on Home -> Hosts & Clusters -> Select vCenter Server -> Configure -> Advanced Settings  and Search for “sso-admin”.

3. Get Platform Services Controller from vCenter Server appliance CLI

Login to your vCenter Server appliance using SSH with root credentials. Switch to Bash shell using command “Shell”. Execute the below command to get the Platform Services controller (PSC) information.

 
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost



Introduction to VMware Tanzu Kubernetes grid





          


            What is VMware tanzu Kubernetes grid? 


    
    It provides a consistent, upstream compatible implementation of Kubernetes, that is tested and  supported by VMware. VMware tanzu Kubernetes grid allows organizations to run Kubernetes with consistently and make it available to developers as a utility. It provides services such as networking, authentication, ingress control and logging that a production Kubernetes environment requires.


 

 
Components of TKG

1.     Bootstrap environment: - 
     
                    The bootstrap environment any physical or virtual server on which you download and run the tanzu Kubernetes grid CLI. This is where the initial bootstrapping of a management cluster occurs, before it pushed into platform where it will run.

2.     TKG management cluster: - 
                  
                    The management cluster will be the first element that need to be deployed when you create a tanzu Kubernetes grid instance. The management cluster is a Kubernetes cluster that performs the role of the primary management and operational center of the tanzu Kubernetes grid instance. You can either leverage the TKG cli or web interface to deploy a tkg management cluster.

3.     Tanzu Kubernetes cluster: -
                  
                    These are the clusters deployed from management cluster by using the tanzu Kubernetes grid cli. You can have multiple clusters running different versions of Kubernetes, depending on the needs of the application they run. By default tanzu Kubernetes clusters implement calico for pod to pod networking
 

 

3 Ways to get VMware Platform Services Controller (PSC) information from vCenter Server 6.5

      From vSphere 6.5 , VMware Changes its vCenter architecture by introducing Platform services controller (PSC) by replacing vCente...