When your plugin front-end is making a call for a specific object you should pass the target object ID and target VC GUID as part of the REST call. Instead of passing multiple command line parameters in the form: "-vcenter.guid=5xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx -vcenter.thumbprint=1xxxxxxxxxxxxxxxxxxxxxxxxxx -vcenter.fqdn=vc1.com -vcenter.port=443" you should pass a JSON file that contains an array of VC configurations and parse that file to a Java object using Jackson or a similar library. Your plugin should accept multi-VC configuration at startup. What are the file/function changes we need to make in service/ui code to support this routing? The provided sample does not support working with multiple vCenters. Is it possible to achieve the singleton plugin instance working using the given sdk sample and tools? If so what is the command options we should use to support multiple vCenters? Is it possible to achieve the singleton plugin instance working using the given sdk sample and tools? If so what is the command options we should use to support multiple vCenters?Ģ. Java -jar target/remote-plugin-sample-6.7.0-SNAPSHOT.jar -vcenter.guid=5xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx -vcenter.thumbprint=1xxxxxxxxxxxxxxxxxxxxxxxxxx -vcenter.fqdn= vc1.com -vcenter.port=443ġ. In order to test that, I had registered same instance of plugin with multiple vCenter servers(of 7.0 version in Enhanced Linked Mode) and able to see the plugin by connecting to both vCenters.īut the chassis list actions are always listing VC1 related host list only which is used for manifest server startup command as shown below: I'm trying to test Singleton Plug-in topology as mentioned in Remote plugin SDK documentation(vsphere-client-sdk-7.0-15863815).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |