Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

Server Diagnostics #380

Open
jtopjian opened this issue Feb 22, 2015 · 2 comments
Open

Server Diagnostics #380

jtopjian opened this issue Feb 22, 2015 · 2 comments

Comments

@jtopjian
Copy link
Contributor

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
Copy link
Contributor

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

@jtopjian
Copy link
Contributor Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants