openstack/cyborg
Code Issues Proposed changes

fix doc comment

Browse Source 
Change-Id: Ia55824b7f7018e0221a67080d2cbc4a6a5d42a08
This commit is contained in:
songwenping 2022-09-06 11:03:28 +08:00
parent f05e6e7e1d
commit 9bbe9d2733
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/admin/index.rst
View File

@ -217,7 +217,7 @@ calls are routed through that.
{
"events": [
{ "name": "accelerator-request-bound",
"tag": $device_profile_name,
"tag": $arq_uuid,
"server_uuid": $instance_uuid,
"status": "completed" # or "failed"
},
@ -227,9 +227,10 @@ calls are routed through that.
8. The Nova compute manager waits for the notification, subject to the timeout
mentioned in Section Other deployer impact. It then calls the Cyborg REST
API `GET /v2/accelerator_requests?instance=<uuid>&bind_state=resolved`.
API `GET /v2/accelerator_requests?instance=<uuid>&bind_state=resolved` to
get the arqs in status ['Bound', 'BindFailed', 'Deleting'].
9. The Nova virt driver uses the attach handles returned from the Cyborg call
9. The Nova virt driver uses the bound arqs returned from the Cyborg call
to compose PCI passthrough devices into the VM’s definition.
10. If there is any error after binding has been initiated, Nova must unbind