Denis_Chorbadzh Tracker

Re: How to hide the actions instead of disable using Dynamic Extensions in vSphere Client

Denis_Chorbadzh — Wed, 04 Oct 2023 12:35:48 GMT

Thank you for noticing the missing part, Kumar! Will update it.

Re: How to hide the actions instead of disable using Dynamic Extensions in vSphere Client

Denis_Chorbadzh — Tue, 03 Oct 2023 14:15:28 GMT

Hi Kumar,

For 8.0 release, you can set the property "relevant" to "false" for every menu item that you don't want to be displayed at all. Setting the "visible" property just enables/disable the action.

For 7.0 releases, the items will always be displayed and will be enabled/disabled based on the "visible" property.

Best Regards,

Denis

Re: Error during rest request

Denis_Chorbadzh — Mon, 07 Aug 2023 12:37:51 GMT

Hi,

I think Vladi was refering to this thread: https://communities.vmware.com/t5/vSphere-Client-SDK-Discussions/SSL-problems/td-p/2219486

Let us know if you were able to resolve the problem.

Best Regards,

Denis

What's new in vSphere Client SDK 8.0 Update 1

Denis_Chorbadzh — Thu, 25 May 2023 13:23:27 GMT

Hi Folks,

The new vSphere 8.0 Update 1 release brings some new features and resolved issues.

What's new for vSphere Client extensibility and remote plug-ins:

Ability to define action separators - Plug-ins are now able to define separators between their menu actions. This can be achieved by specifying a new object {"type":"separator"} between the plug-in defined actions.
Ability to define multiple summary cards - Plug-ins are now able to define up to 3 cards in a given vSphere object's summary view. In addition, each card can have its own icon and title. If no icon or title are provided, the default plug-in icon and name will be used. This can be achieved by specifying an array of views instead of a single view in a given object's summary section.
Integrated Solution Installation enhancements - Ability to specify required vCenter Server version support. Integrated solutions can now specify which vCenter Server version they support. This will prevent users from installing the solution on a vCenter Server with lower than the specified version. To achieve this, the vmw.vsphereui.solutioninstall.requiredVcVersion property must be specified in the solution's OVF.
Remote Plug-in Sample - Upgraded Angular and Clarity versions for improved security.
Extension Registration Tool - The extension-registration tool now accepts a list of events. This means that plug-in registration may include a list of plug-in defined events.

Resolved Issues:

Actions are now ordered in the way they are written in the plugin.json.
Fixed an issue where a plug-in may be shown as Partially Deployed.
The plug-in action menus are properly live refreshed when the user shows/hides a plug-in.
Fixed an issue where an Incompatible plug-in could be shown as Failed.
The htmlClientSdk is no longer cached by the browser and does not break plug-in upgrades.
Fixed Confirmation Modal layout issues.
Plug-in deployment will no longer fail if it is using an unknown locale. This means that adding a new supported language to the vSphere Client and the plug-in will not break the plug-in's compatibility with older vSphere Client versions.
Fixed an issue where an Incompatible plug-in could not be redeployed.

Known Issues:

Multi Manifest Issue - The Multi Manifest feature requires a default manifest called plugin.json. If a plug-in is using the multi manifest feature, it is required that at least one of the plug-in manifests is named plugin.json. It is recommended that the least desired plug-in manifest is named plugin.json and placed at the bottom of the array of manifests.

For more information and code examples, check the official SDK documentation page and the release notes.

As always, feel free to share your feedback and ideas with us.

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Tue, 21 Mar 2023 14:11:38 GMT

Hi,

From the provided log snippets, we can't infer what might be the issue.

We would need the VC support bundle and the plugin package in order to investigate.

If you can't provide the whole plugin package due to legal concerns, you can provide a stripped down version or modify one of the local plugin samples in order to reproduce the issue.

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Thu, 16 Mar 2023 13:47:50 GMT

Hi @ShivamVerma380 ,

Looking at the logs:

This has no impact on plugin package deployment but is expected only during plugin development. In Production the plugin package should be registered as a vCenter extension

I suspect you have placed your plugin in "/usr/lib/vmware-vsphere-ui/plugin-packages/". It should be registered as a vCenter Server extension and not present in the plugin-packages folder.

The "libraries" folder should be place in your plugin package and be a part of the plugin zip file. It will be downloaded by the vSphere Client and unpacked in "/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/".

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Thu, 16 Mar 2023 12:49:37 GMT

Hi @ShivamVerma380 ,

The META_INF folder is required for VMware certified plugins. It does not impact your plugin's deployment.

Re: Failed to deploy plugin using multi-manifest

Denis_Chorbadzh — Thu, 16 Mar 2023 12:27:59 GMT

Hi @vedaniks ,

Thank you for the valuable feedback.

Since the default plugin manifest file is called plugin.json, it turned out to be required by the system. This is why the following is working fine:

{
"manifestVersion": "1.0.0",
"manifests": [
"plugin-80.json",
"plugin.json"
]
}

We are going to address this limitation in a next vSphere release. Until then, please name the least desired (lowest priority) manifest file as plugin.json. For example:

{
"manifestVersion": "1.0.0",
"manifests": [
"plugin-80.json",
"plugin-70.json"
"plugin.json"
]
}

Best Regards,

Denis

Re: Failed to deploy plugin using multi-manifest

Denis_Chorbadzh — Wed, 15 Mar 2023 15:55:19 GMT

Hi @vedaniks ,

The manifests should be ordered from the most feature-rich (latest) to the more basic. For example plugin-80.json, then plugin-70.json.

The 8.0 vSphere Client will try to deploy plugin-80.json and will succeed. The 7.0 vSphere Client will try to deploy plugin-80.json and will fail. Then, it will try to deploy plugin-70.json and will succeed.

Let us know of the errors you are getting.

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Wed, 22 Feb 2023 11:20:46 GMT

Hi @ShivamVerma380 ,

First, you need to integrate the "libraries" folder in your plugin.zip and not modify directly the plugin cache in "/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/". This directory is used for downloading and unarchiving the plugin deliverables.

Regarding Spring 4.3.9, it is vulnerable to Spring4Shell, and we highly recommend you upgrade to 5.3.XX (LTS).

For vcplugin-ui, you need:
- https://mvnrepository.com/artifact/org.codehaus.woodstox/woodstox-core-asl/4.4.1
and
- https://mvnrepository.com/artifact/org.codehaus.woodstox/stax2-api
Don’t mind the "org.springramework.orm" not being resolved: it is a red herring. It has bundle id of 129, typically plugin bundle ids are in 300 range.

For vcplugin-controller, you need to resolve "org.springframwork.beans" jar first (it is the provider of "org.springframework.beans.factory.annotation").

From the attachments it is not clear why your “org.springframwork.beans” is not resolved (Note: there will be more than one “org.springframwork.beans”, yours will have id in the 300+ range).

It is also not clear why the plugin deployment timed out. It was probably due to the unresolved plugin bundles.

Regarding the type of the plugin, your plugin is a "local" plugin. This means it will be downloaded from the remote location and will be placed inside the VCSA's tomcat server. To be a "remote" plugin, it needs to run on your own server and just provide its views to the vSphere Client. Remote plugins also use a different manifest format, called plugin.json. You can find more information about the remote plugin architecture here. Have in mind that the local plugin architecture is being deprecated and the next major vSphere Release will support only remote plugins.

Finally, you can verify your plugin is successfully installed by finding it in Administration -> Client Plug-Ins and checking its status. Additionally, you can inspect the vsphere_client_virgo.log file and search for your plugin ID to verify there are not errors and the deployment is successful.

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Thu, 09 Feb 2023 08:42:29 GMT

Hi @ShivamVerma380

If you use Spring MVC controllers in your plugin, here is a list of the bundles required to resolve Spring MVC dependencies:

org.apache.servicemix.bundles.aopalliance-1.0_6
org.apache.servicemix.bundles.spring-aop-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-beans-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-context-5.2.22.RELEASE_1
rg.apache.servicemix.bundles.spring-context-support-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-core-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-expression-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-web-5.2.22.RELEASE_1
org.apache.servicemix.bundles.spring-webmvc-5.2.22.RELEASE_1

Best Regards,

Denis

Re: Esxi Webservice Login Not Working

Denis_Chorbadzh — Mon, 30 Jan 2023 08:58:27 GMT

Hi @cubits,

Unfortunately, we are not able to provide an adequate answer since this forum is concerned with vSphere Client extensibility and plug-ins.

You can try posting your question in a relevant forum.

Best Regards,
Denis

Re: Using the integrated solution install mechanism

Denis_Chorbadzh — Fri, 27 Jan 2023 09:54:15 GMT

Hi,

The solution install token is a one-time token that is injected in the deployed VM and has a lifespan of 30 minutes. It is intended to be used for the solution's extension registration and, because of security concerns, cannot be regenerated.

The "api/ui/solutioninstall" is an API of the vSphere UI and is not a part of the mentioned SDKs. You can find more information in the vSphere Client SDK official documentation.

After the solution plugin has been registered, you can log in the vSphere UI, go to the plugin UI and initiate extension update by passing the session information to the plugin's backend which can obtain a vCenter Server session and call the vCenter Server APIs.

Best Regards,

Denis

Re: What's new in vSphere Client SDK 8.0

Denis_Chorbadzh — Fri, 13 Jan 2023 11:53:43 GMT

Hi Kumar,

The new feature allows plugins to define an action that will navigate to another view. Before that, the only allowed actions were the modal actions, where an action opens a modal dialog. Now, you can have an action that navigates to another one of your views.

The remote plugin sample does not demonstrate this.

There are different scenarios. The idea is that you can have an action "Configure VM backup" which will redirect to the VM's configure view of your plugin where users will be able to configure the VM's backup options.

Best Regards,

Denis

Re: vSphere Remote Plugin SDK: Dynamic extensions for Summary cards

Denis_Chorbadzh — Fri, 13 Jan 2023 11:33:45 GMT

Hi Kumar,

Yes, the dynamic cards in the summary views are introduced in vSphere 8.0 and are not supported in vSphere 7.0.

Best Regards,

Denis

Re: Clone Session using Python

Denis_Chorbadzh — Mon, 09 Jan 2023 10:35:57 GMT

Hi vedaniks,

Thanks a lot for sharing a working python example for cloning a user session.

Best Regards,

Denis

Re: VMware VM콘솔 끊김 현상

Denis_Chorbadzh — Mon, 09 Jan 2023 10:28:21 GMT

Hi,

Seems like the question is related to the VM web console and vMotion and this forum's main focus is vSphere Client extensibility and plug-ins. You can try posting your question in the general vCenter Server forum.

Best Regards,

Denis

Re: How to call the GetResourceUsage(getResourceUsage) in python

Denis_Chorbadzh — Mon, 09 Jan 2023 10:08:56 GMT

Hi,

These are specifics to the Management SDK usage. You can try posting your question in the Management SDK forum and people might be able to help.

Best Regards,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Wed, 04 Jan 2023 13:08:03 GMT

Hi,

You will need to place the following bundles inside your "libraries" folder:

https://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/5.3.24_1

https://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/5.3.24_1

Best,

Denis

Re: Failed to deploy a local plugin on vSphere 8.0

Denis_Chorbadzh — Wed, 04 Jan 2023 12:57:32 GMT

Hi,

The package "com.vmware.vim.sso.http" is an internal package and should not be used. The code that uses classes from this package needs to be rewritten accordingly.

Best,

Denis