_vladi_'s Posts

Hi, The client log seems fine - plugin is correctly deployed. Tasks are not integral part of the plugin but are normally a recommended addition to the partner solution itself. Given the cmCatalog does not have your plugin resource bundle you should be mostly looking at the vCenter registration. A vCenter extension has a number of properties. Some of the important ones are the "client" and the "server" info which you have already set because they deal with the plugin itself (which is successfully installed). If you need to have task tracking you should also set the following data in the vCenter extension (see API https://code.vmware.com/apis/196/vsphere/doc/vim.Extension.html taskList with all task types your solution is creating. resourceList with all localization data / strings per locale. Tasks normally declare the following keys: Name: <full-task-name>.label = My Task Name Description: <full-task-name>.summary = My Task Description Note that the API is very opinionated with regards to 2.1 and 2.2 and require that you specify the keys with full task name + .label or .summary in order to be picked up by the UI. (Optional) faultList with possible custom defined error messages in the form: Message: <full-fault-class-name>.summary = My Custom Error Message The issues you are facing indicate likely missing 2.1 and/or 2.2. Note also that 1. and 3. above can be inspected in the MOB: https://<vc-ip>/cm/mob/?moid=ExtensionManager but 2. will not be visible there although it was added. Instead, 2. can be inspected in the catalogs of the LocalizationManager for each locale: https://<vc-ip>/cm/mob/?moid=LocalizationManager Given these specifics I guess this is worth a blog post some time soon Cheers, Vladi

Hi Sujeet, The other possibility is that you are missing the mapping to "samples:ChassisB" in the DataProvider: @type("HostSystem,samples:Rack,samples:ChassisB") // declares the supported object types. public class ChassisRackVSphereDataAdapter implements DataProviderAdapter { ... This is required so that the DataService knows who delivers this object types and can execute any filtering. Please let me know if this works. Cheers, Vladi

Please search for "samples:ChassisB" in the plugin.xml of the ChassisB example. You need to 1) define your object type in the templates, 2) use it in your filtering metadata and 3) use it in the target type sections. Some of these are probably missing from your plugin.xml. Most likely, you are missing the vsphere.core.objectTypes extension which is required in conjunction with the prioritization extensions (as documented in the sample plugin.xml). Cheers, Vladi

Hi Sujeet, I don't see any reference of vmware.prioritization.actions in the provided example that doesn't work for you. Could you please follow closely the ChassisB sample which is demonstrating this extension point and provide your xml if it still does not work? Thanks. Cheers, Vladi

Hi Sujeet, Global (context-less) actions like Add require vmware.prioritization.listActions extension point. Context-specific actions like Delete require vmware.prioritization.actions extension point. This allows you to discriminate the 2 cases and apply filtering on the second one only. Cheers, Vladi

This is deprecated extensibility so it is not available in the latest HTML sample in 6.7U3. That said, it is still supported and works in vSphere Client 6.7U3. Just download an older SDK: 6.5U1 from vSphere Web Client SDK - VMware {code} which contains the ChassisB sample you are interested in. Cheers, Vladi

Hi Sujeet, I believe what you are asking for is having global / context-less actions. With the currently recommended extensibility (without custom objects defined in the plugin.xml) you define the whole custom object list in a global view so you can choose any UI elements to show, including actions and menus. With the custom object extensibility used in the screenshot below you can define the action in the ActionSpec as <privateAction> and add this action to another vmware.prioritization.listActions extension which enables the global actions on a list's action button bar. This use case is again demonstrated in the ChassisB sample part of the 6.5U1 SDK. Just have a look at that for reference. Cheers, Vladi

Hi Sujeet, Good question! With the extensibility for local plugins you can achieve this using either <conditionalProperties> tag with a condition to check or <condition> tag with a PropertyConstraint that checks a certain property. Both are available for vise.inventory.representationspecs extensions. These approaches are demonstrated in the old ChassisB sample (see the plugin.xml of chassisB-html project). The sample is available in the 6.5U1 version of the SDK. While still supporting this, recent versions of the SDK (for both local and remote plugins) deprecate custom objects and recommend using own global views to display any custom object lists. This gives you the freedom to implement any kind of UI switching logic without depending on specific extensibility. You can see this pattern in the latest HTML sample (6.7U3 SDK). What approach to make use of is up to you depending on what you want to support. Cheers, Vladi

chrissmith1​ Hi Chris, The team managed to reproduce the sporadic issue with the overlapping header you reported. There is a fix in the vSphere Client now and it will be shipped with a future release vehicle. Very much appreciate the effort to report and record the video - this helped a lot as this type of issues are very difficult to root cause! Thanks! Cheers, Vladi

If you are a plugin developer I would encourage you to send a mail to plugin@vmware.com and indicate your DCPN case id, vendor name and plugin name. This is the alias of all PM, ecosystem and engineering folks on the plugin side who can help you out (even though the issue is not specific to plugins). Neither you, nor the SDK team can provide any meaningful info publicly so the Forum is not the right channel to chase next steps.

Hi Gavin, I understand your points and have raised attention to this problem. This has been escalated internally in VMware by different partners and the vCenter API team is on top of it. I have no visibility over the vSphere beta release plans with regards to fixing this issue - any such communication will go through the standard beta channels. Cheers, Vladi

Hi Angelo, Normally such issues are resolved by RC so that partners can accommodate to any changes. I am not responsible for this API but this particular instance should have already been resolved. If you are a TAP partner please file a DCPN case or check other channels available to you (which you certainly have if you got a beta vSphere version for testing). Again: this is a beta vSphere version and vijava is not a VMware-supported library so this public forum is not the right place to discuss such topics. Cheers, Vladi

Hi Abby, Correct, this is not fixed in the beta builds. Normally, such API mismatches are sorted for RC but this is related to the vCenter API (not the Client API), so I don't have more info. If I am not mistaken you also have a DCPN case open on this and it is the better place than the Forum to discuss any beta feedback as the relevant VMware teams are looped in. Cheers, Vladi

Hi Chris, Thanks for checking the old issue is resolved and reporting the rendering issue. We will check the details - very helpful indeed. Btw, I know it is standard but did you try clearing your browser cache or test it in incognito mode? As for the theming icon support this API is already implemented internally but is planned to go out only in a next release. Great feedback, thank you! Cheers, Vladi

Hi Abby, Thanks for the detailed report. This is not specific to plugins, it is rather a vCenter API so I will take it up with some internal teams. That said, given this is a beta build, we cannot provide details in this public forum. Let's take further feedback offline. Cheers, Vladi

Hi Abby, Please also keep in mind vijava is not a VMware supported library. It is external library - wrapper around vCenter Server APIs so it is playing catch-up with the actual product and any updates to the VIM API can come later. The recommended library is vim25. Could you please check if you can reproduce the same issue with the latest vim25 from the beta or older vim25 versions? Cheers, Vladi