Yes, Alex, this command does confuse me a bit.
Hope we can support bind/unbind accelerators in the future.
I also found some errors in kolla-ansible when deploying cyborg. I want to know how active is the cyborg project?
Shall we fix the deploy bug in kolla-ansible and backport the bug fixes to released branches?
在2021年12月13日 16:35，Alex Song (宋文平)songwenping@inspur.com 写道：
Anyway, we should shield this cmd to avoid misoperation of arq and lead the instance start error for now.
发件人: Alex Song (宋文平) 发送时间: 2021年12月13日 16:27 收件人: 'xiaolihope1008@163.com' xiaolihope1008@163.com; 'openstack-discuss@lists.openstack.org' openstack-discuss@lists.openstack.org 主题:答复: [lists.openstack.org代发][cyborg][nova][qa]Question about Accelerator unbinding
Emm, the arq unbind cmd is used of deleting instance.
Recently we donot support hot-plug/unplug device for instance. We only support binding devices when create instance and unbinding devices when delete instance.
Best Regards.
发件人: Di XiaoLi [mailto:xiaolihope1008@163.com] 发送时间: 2021年12月13日 9:54 收件人: openstack-discuss openstack-discuss@lists.openstack.org 主题: [lists.openstack.org代发][cyborg][nova][qa]Question about Accelerator unbinding
hi, Cyborg and nova team:
I am using cyborg with "Wallaby" release to manage my accelerator devices, while I'm trying to unbind the accelerator I found that the device was not actually unbound from the virtual machine.
Here are my questions:
1. What is the function of the arq unbind command in cyborg ?
2. How to unbind the accelerator which bounded to vm? Does nova or cyborg support this function now？
Here are my steps:
step1: openstack accelerator arq unbind ed205084-f58d-4fad-99b4-327a1398858f +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | uuid | ed205084-f58d-4fad-99b4-327a1398858f | | state | Unbound | | device_profile_name | ssd | | hostname | None | | device_rp_uuid | None | | instance_uuid | None | | attach_handle_type | | | attach_handle_info | {} | +---------------------+--------------------------------------+
step2: login vm and check the device, but it still here.
step3: stop vm and start vm, met the following error:
"nova.exception.AcceleratorRequestOpFailed: Failed to get accelerator requests: Cyborg returned no accelerator requests for instance ca77ef4e-421c-4c6c-9d76-7618a90ec921"