-
Notifications
You must be signed in to change notification settings - Fork 292
CP-53470 Additional traces around xenopsd VM_migrate & rejoin traceparents in requests forwarded to xenopsd by xapi #6275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CP-53470 Additional traces around xenopsd VM_migrate & rejoin traceparents in requests forwarded to xenopsd by xapi #6275
Conversation
cf535d2
to
077961f
Compare
updated DCO & ran ocamlformat |
I had no idea CI workflows "required approval from a maintainer" - I gave mine to see if everything passes here. |
To cover the entire body of a function with a
|
discussed during standup that the PID changes could be split into a PR of its own. |
077961f
to
97c2305
Compare
97c2305
to
82890cc
Compare
latest trace available here: https://jaeger.kfd.eng.citrite.net/trace/695ffeb561c7ceaa9aa4e73302401a86?uiFind=151f83755d94c4d9 |
Signed-off-by: Aidan Allen <aidan.allen1@cloud.com>
Signed-off-by: Aidan Allen <aidan.allen1@cloud.com>
82890cc
to
6587b75
Compare
BVT + BST : 212301 |
Reconnected VM_receive_memory span to VM.migrate:
When xapi passes the traceparent header to xenopsd it is serialised under the additional_headers field of the json body, updated xenopsd to expect that instead of sourcing it from the non existent traceparent field
Added some additional spans around vm migration critical section including the specific point we receive the suspend from emu-manager/xenguest - this required moving the with_tracing function to a more common location