Allow Deployment Agent to Log Information to Ironic Service

Registered by Tim Miller on 2013-05-13

Currently, there is no way for a deployment agent to log information back to the service in case of problems.

This proposal is to provide an interface for the deploy agent to provide arbitrary log information to the service, to be surfaced at least in a service log file, or perhaps surfaced even as far up as `nova show`.

This will help with troubleshooting, and will enable more informative bug reports.

Blueprint information

Status:
Not started
Approver:
aeva black
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Whiteboard

This functionality was discussed as part of the ramdisk API, and will be fulfilled by allowing the ramdisk's process to POST log data back to Ironic's API service. Some notes were captured here:

https://etherpad.openstack.org/p/IcehouseIronicNodeCommunication

-Deva, 2012-11-12

Gerrit topic: https://review.openstack.org/#q,topic:bp/deploy-agent-logging,n,z

Addressed by: https://review.openstack.org/163737
    Add logs REST resource

Addressed by: https://review.openstack.org/168799
    Collect IPA logs

We definitely need to do this to help out operators.
// jroll 2015-10-15

We're moving from using blueprints to track features to RFE bugs. I've filed one for your change (see related bugs section). Please track further work there using Closes-Bug, Partial-Bug or Related-Bug in commit messages and use this newly created RFE bug.
//vdrok 2015-12-16

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.