container-service-extension icon indicating copy to clipboard operation
container-service-extension copied to clipboard

CSE deployed vApps - vROps dashboard

Open Vijendrasi opened this issue 4 years ago • 6 comments

Is it possible to create a separate dashboard in VROPs for vApps created using CSE (K8s cluster vms) ?

Vijendrasi avatar Oct 14 '19 10:10 Vijendrasi

Vijendrasi

I will connect you with the person with in VMware who might know the answer.

Aashima

goelaashima avatar Oct 14 '19 19:10 goelaashima

Thank you Aashima, We have observed that CSE don't have any database which keeps record for kubernetes cluster deployed by it.

In vCloud director kubernetes vApps has some kind of metadata information which is used to fetch CSE cluster list command to identify list of vApps deployed through it.

At the moment we are unable to identify this information. Once we would get unique identification of kubernetes vApps deployed by CSE server than next step will be filter this information in vROps and create custom dashboard for it.

Vijendrasi avatar Oct 15 '19 05:10 Vijendrasi

There is no direct CSE involvement when it comes to vROPS monitoring of the deployed clusters. The Container Management Pack in vROPs https://marketplace.vmware.com/vsx/solutions/vrealize-operations-management-pack-for-container-monitoring might be of help. There is also a vCloud Director management pack for vROPS, that IIRC can understand vCD metadata, so you might be able to use this to identify K8s vApps.

tschoergez avatar Oct 15 '19 18:10 tschoergez

HI,

All vApps that are CSE native clusters, will have the following metadata on them cse.cluster.id : uuid cse.version : cse version string cse.template.name : name of the template used to create the cluster cse.template.revision : revision of the template used to create the cluster

The metadata cse.cluster.id should be enough by itself to identify a CSE native cluster.

rocknes avatar Nov 05 '19 22:11 rocknes

Hi, we can see the CSE-vApp metadata are available on vROps as metrics for vApp objects, still it's not possible to use them in a View as they simply not show up in the View builder. We can only see the "vapp.origin.id", "vapp.origin.name", "vapp.origin.type" metrics, which are the "standard" metadata available for vApp objects. Is there any change to make on the vcloud.properties file on vROps, or something else we should do to actually use the data (again, that is present on vROps)?

cohizzle86 avatar Nov 11 '19 14:11 cohizzle86

I guess the question above is meant for vROPs, @Vijendrasi , can you please look into it?

rocknes avatar Nov 11 '19 18:11 rocknes