Add request_id field to migrations object

Registered by Zhenyu Zheng on 2018-01-23

This blueprint has been superseded. See the newer blueprint "Add request_id to the InstanceAction versioned notifications" for updated plans.

Both GET /os-migrations API and GET /servers/uuid/migrations API can only simply reply migration status as complete/error etc. Top-layer management software and customer may want to know why it failed.

We may use instance action API to check for failure details, showing instance-action details will need req-id as an input parameter, But migrations obj does not include req-id field, it will be hard to connect to instance-actions.

Simple add req-id to migrations obj and related API response will solve the problem.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Zhenyu Zheng
Direction:
Needs approval
Assignee:
Zhenyu Zheng
Definition:
Superseded
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Matt Riedemann on 2018-03-12

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-req-id-to-migrations-obj,n,z

Addressed by: https://review.openstack.org/536765
    Add request_id field to migrations object

Can we now mark this as superseded by blueprint add-request-id-to-instance-action-notifications ? -- mriedem 20180308

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.