Back to bug 1041121

Who When What Removed Added
RHOS Integration 2013-12-12 13:43:56 UTC Whiteboard upstream_milestone_none upstream_status_unknown
RHEL Program Management 2013-12-12 17:30:33 UTC Target Release --- 5.0
RHEL Program Management 2013-12-12 18:00:55 UTC Keywords FutureFeature
Red Hat Bugzilla 2013-12-12 18:00:55 UTC Doc Type Bug Fix Enhancement
RHOS Integration 2013-12-17 00:43:10 UTC Target Milestone --- Upstream M2
Whiteboard upstream_milestone_none upstream_status_unknown upstream_milestone_icehouse-2 upstream_status_needs-code-review
Stephen Gordon 2014-01-06 21:24:25 UTC Keywords Triaged
URL https://blueprints.launchpad.net/nova/+spec/diagnostics-namespace https://blueprints.launchpad.net/nova/+spec/v3-diagnostics
CC ndipanov, rbryant, sgordon
Component RFEs openstack-nova
QA Contact ajeain
Stephen Gordon 2014-01-06 21:24:45 UTC Priority unspecified medium
Severity unspecified medium
RHOS Integration 2014-01-07 05:02:50 UTC Target Release 5.0 ---
Target Milestone Upstream M2 Upstream M3
Whiteboard upstream_milestone_icehouse-2 upstream_status_needs-code-review upstream_milestone_icehouse-3 upstream_status_needs-code-review
RHEL Program Management 2014-01-07 05:19:46 UTC Target Release --- 5.0
John Skeoch 2014-01-13 01:09:49 UTC CC hateya
Dave Allan 2014-01-21 21:56:39 UTC Status NEW ASSIGNED
CC dallan
Assignee rhos-maint dripton
RHOS Integration 2014-02-19 21:41:47 UTC Whiteboard upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_definition_approved
RHOS Integration 2014-02-20 15:53:05 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 17:32:39 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 17:50:47 UTC Status ASSIGNED POST
Target Release 5.0 ---
RHEL Program Management 2014-02-20 18:29:28 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 21:42:50 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 22:19:23 UTC Target Release --- 5.0
RHOS Integration 2014-02-21 17:09:01 UTC Severity medium low
RHOS Integration 2014-02-22 05:03:03 UTC Whiteboard upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_definition_approved upstream_milestone_next upstream_status_needs-code-review upstream_definition_approved
Severity low unspecified
Stephen Gordon 2014-02-22 20:56:56 UTC Target Release 5.0 ---
Target Milestone Upstream M3 ---
RHOS Integration 2014-03-21 04:22:21 UTC Whiteboard upstream_milestone_next upstream_status_needs-code-review upstream_definition_approved upstream_milestone_none upstream_status_needs-code-review upstream_definition_drafting
Dave Allan 2014-05-21 16:53:44 UTC Assignee dripton berrange
John Skeoch 2014-06-24 00:11:07 UTC CC dallan pmyers
RHOS Integration 2014-06-25 04:02:34 UTC Target Milestone --- Upstream M3
Whiteboard upstream_milestone_none upstream_status_needs-code-review upstream_definition_drafting upstream_milestone_juno-3 upstream_status_good-progress upstream_definition_approved
Severity unspecified low
RHOS Integration 2014-07-30 04:02:27 UTC Whiteboard upstream_milestone_juno-3 upstream_status_good-progress upstream_definition_approved upstream_milestone_juno-3 upstream_status_needs-code-review upstream_definition_approved
RHOS Integration 2014-08-28 04:01:49 UTC Whiteboard upstream_milestone_juno-3 upstream_status_needs-code-review upstream_definition_approved upstream_milestone_juno-3 upstream_status_implemented upstream_definition_approved
RHEL Program Management 2014-10-05 02:06:28 UTC Target Release --- 6.0
Lon Hohberger 2015-01-12 22:27:47 UTC Status POST MODIFIED
Fixed In Version openstack-nova-2014.2.1-11.el7ost
Daniel Berrangé 2015-01-16 11:14:14 UTC Doc Text Feature:
Standardized data reporting for the 'diagnostics' command / API call

Reason:
The historic diagnostics API, for retrieving status and statistics about the operation of a running instance, had no formal specification. As a result every virtualization driver in Nova reported a different data set. This made it difficult to write applications to consume the data in a predictable manner

Result:
A new version of the diagnostic API was implemented in the v3 API that defines a standardized set of data items that virtualization drivers must use for reporting. It is now possible to write applications that consume the data reliably across different virtualization platforms.
Julie 2015-01-20 04:34:02 UTC CC juwu
Doc Text Feature:
Standardized data reporting for the 'diagnostics' command / API call

Reason:
The historic diagnostics API, for retrieving status and statistics about the operation of a running instance, had no formal specification. As a result every virtualization driver in Nova reported a different data set. This made it difficult to write applications to consume the data in a predictable manner

Result:
A new version of the diagnostic API was implemented in the v3 API that defines a standardized set of data items that virtualization drivers must use for reporting. It is now possible to write applications that consume the data reliably across different virtualization platforms.
With this feature, there is now a standardized data reporting mechanism for VM diagnostics. The historic diagnostics API had no formal specification. As a result, different virtualization drivers in Nova reported a different data set and made it difficult for VM diagnostics to consume the data in a predictable manner. With this update, a new version of the diagnostic API was implemented in the version 3 API, and it now defines a standardized set of data items that virtualization drivers must use for reporting.
Scott Lewis 2015-02-09 20:04:54 UTC Status MODIFIED CLOSED
Resolution --- CURRENTRELEASE
Target Milestone Upstream M3 ga
Last Closed 2015-02-09 15:04:54 UTC
Summer Long 2015-03-24 04:05:38 UTC CC slong
Doc Text With this feature, there is now a standardized data reporting mechanism for VM diagnostics. The historic diagnostics API had no formal specification. As a result, different virtualization drivers in Nova reported a different data set and made it difficult for VM diagnostics to consume the data in a predictable manner. With this update, a new version of the diagnostic API was implemented in the version 3 API, and it now defines a standardized set of data items that virtualization drivers must use for reporting. With this feature, there is now a standardized data reporting mechanism for VM diagnostics. Previously, the diagnostics API had no formal specification. As a result, different virtualization drivers in the Compute service reported a different data set and made it difficult for VM diagnostics to consume the data in a predictable manner. With this update, a new version of the diagnostic API was implemented in the version 3 API, and it now defines a standardized set of data items that virtualization drivers must use for reporting.
Perry Myers 2016-04-26 19:08:47 UTC CC pmyers
Russell Bryant 2019-09-09 14:57:09 UTC CC rbryant

Back to bug 1041121