Standardization of VM diagnostics info API.

Bug #1696033 reported by OpenStack Infra on 2017-06-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Hesam Chobanlou

Bug Description
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/nova" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit a9448389932ae010897bf5a19239588bf198ee52
Author: Sergey Nikitin <email address hidden>
Date: Tue Aug 16 15:04:14 2016 +0300

    Standardization of VM diagnostics info API.

    Before this patch, VM diagnostics response was just a
    'blob' of data returned by each hypervisor. New API
    version makes diagnostics response standardized.
    New response has a set of fields which each hypervisor
    will try to fill. If hypervisor unable to provide a
    specific field then this field will be reported as 'None'.

    Tempest tests: I7757c5beeea3d3b0bc15a51cafc5ea2ada65e76c

    DocImpact: admin guide docs should be updated to mention
    standardized version of the diagnostics response

    blueprint: restore-vm-diagnostics

    Change-Id: If0b1493cc5c1c7f0d9896dd68342ad4dea4f7da2

Changed in nova:
status: New → Confirmed
importance: Undecided → Critical
importance: Critical → Low
tags: added: low-hanging-fruit
tags: added: api
removed: nova
Ilya Popov (ilya-p) wrote :

Hello All !

I tried to find blueprint for this features and failed to find. Is there any somewhere or not ?

Or I have to give up and change doc based on commits only ?

Changed in nova:
assignee: nobody → Hesam Chobanlou (hesamchobanlou)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers