You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Blind guess: they are missing because the TraversalSpec I'm using doesn't match them. From what I can remember they are similar to resource pools. Until now I haven't been able to play around with an environment where vApps are a thing. I'd love to implement this, and it would be great to also visualize vApps as such. Things to do:
extend the traversal specification
evaluate whether it is worth the effort to create a dedicated table for VirtualApps
figure out when they have been introduced. This module supports 5.5, blind guess: requests might fail when asking for a VirtualApp on that version.
If anyone has the possibility to grant me temporary read access to a test environment with some VirtualApps configured in a realistic way this could help to speed things up. The more complex the environment (nesting, whatever) the better it is.
If anyone has the possibility to grant me temporary read access to a test environment with some VirtualApps configured in a realistic way this could help to speed things up. The more complex the environment (nesting, whatever) the better it is.
Unfortunately I cannot give you such an access.
Nevertheless, I could gather various information from our environment (even the production) and send them to you by email (after reviewing if there are some confidential information). So, I could execute some vsphere cli commands, some sql queries on the module db,...
Expected Behavior
All the Virtual Machines should be listed through the Icingaweb2 module, including the VM which are part of a vApp
Current Behavior
It seems that the info related to VMs which are part of a vApp are not printed (not gathered?) in the Virtual Machines page of the module.
Possible Solution
Steps to Reproduce (for bugs)
Create a VMware vApp and assign some vm to it.
Your Environment
The text was updated successfully, but these errors were encountered: