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
{{ message }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
The result is a hash/map whose keys are different for each server and hypervisor, so I would think the Get results would just be a generic map[string]interface{}, but I'm not sure the best way of implementing something like that using the patterns of existing services.
Per a recent thread on the openstack-operators list, it looks like Server Diagnostics in the Nova v2.1 API has become uniform. When Nova v2.1 is added to Gophercloud, a more structured... struct will be possible.
What would be the best way to implement Server Diagnostics?
http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-diagnostics
The result is a hash/map whose keys are different for each server and hypervisor, so I would think the Get results would just be a generic
map[string]interface{}
, but I'm not sure the best way of implementing something like that using the patterns of existing services.Examples of other diagnostics output can be seen here:
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
The text was updated successfully, but these errors were encountered: