Current problems with the current provisioner (org.opennms.netmgt.provision.service.vmware.VmwareRequisitionUrlConnection):

1) The current provisioner is going to erase all the nodes from the requisition if the vCenter server is not responding for some reason. This is a problem if the user wants to preserve the statistics, because when the vCenter comes online, all the nodes are going to be re-created from scratch which means new node IDs.

2) If a user adds additional asset records and/or categories to the requisitions maintained by this provisioner, those changes will be gone after the next synchronization. There are useful use-cases when a user wants to manually categorize the ESXs and VMs for reporting purposes. In this kind of situations, the current implementation can't be used.

3) The current implementation only allows the user to filter by only one custom attribute. It will be more flexible to match several custom attributes, and also specify regular expressions against their values.

4) Currently the hosts and the VMs are on the same requisition. It will be nice if we can split them into different requisitions.