Launching the PS cmdlets for talking to Hyper-V takes quite a bit longer than just running the raw WMI queries to get the same information, so figuring out a series of queries to get the same data would be helpful.
There aren't any WMI RPC gems available from what I can see, so the cmdlets would still be used for all write operations.
Possible Models;
[ ] Fog::Compute::Hyperv::Bios
[ ] Fog::Compute::Hyperv::DvdDrive(s)
[ ] Fog::Compute::Hyperv::Firmware
[ ] Fog::Compute::Hyperv::FloppyDrive(s)
[ ] Fog::Compute::Hyperv::HardDrive(s)
[ ] Fog::Compute::Hyperv::NetworkAdapter(s)
[ ] Fog::Compute::Hyperv::Server(s)
[X] Fog::Compute::Hyperv::Switch(es)
Only gets the name and UUID, which is just enough to use it for VM creation or for getting additional data with the reload command.
[ ] Fog::Compute::Hyperv::Vhd
Possible Requests;
[X] Version query
No idea which is these would actually be helped by having them as raw WMI queries, and which would just be more work than it's worth.
It's also very possible that it'd be better to ignore WMI completely and just work on implementing faster cmdlet queries.
Launching the PS cmdlets for talking to Hyper-V takes quite a bit longer than just running the raw WMI queries to get the same information, so figuring out a series of queries to get the same data would be helpful.
There aren't any WMI RPC gems available from what I can see, so the cmdlets would still be used for all write operations.
Possible Models;
reloadcommand.Possible Requests;
No idea which is these would actually be helped by having them as raw WMI queries, and which would just be more work than it's worth. It's also very possible that it'd be better to ignore WMI completely and just work on implementing faster cmdlet queries.