rackspace / gophercloud

A Go SDK for OpenStack. IN FEATURE FREEZE. See Issue #592
http://gophercloud.io
Other
456 stars 180 forks source link

Server Diagnostics #380

Open jtopjian opened 9 years ago

jtopjian commented 9 years ago

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

jrperritt commented 9 years ago

Hmm... yeah, it's too volatile to implement a struct. map[string]interface{} seems like the way to go.

jtopjian commented 9 years ago

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.

http://lists.openstack.org/pipermail/openstack-operators/2015-September/008114.html