Ildik, Cyborg officially completed the V2 version switch from the Ussuri version [1][2], and introduced microversion, you can refer to [3] or more information about the latest Cyborg V2 API. Sorry, we did not backport Device & Deployable V2 API to Train version. [1]https://specs.openstack.org/openstack/cyborg-specs/specs/ussuri/approved/cyborg-api.html [2]https://review.opendev.org/#/c/695648/, https://review.opendev.org/#/c/712835/ [3]https://docs.openstack.org/api-ref/accelerator/v2/index.html -----邮件原件----- 发件人: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] 发送时间: 2020年7月3日 22:53 收件人: OpenStack Discuss <openstack-discuss at lists.openstack.org> 主题: [lists.openstack.org代发][cyborg] Incomplete v2 API in Train Hi Cyborg Team, I’m working with the CNTT community[1], they are working on building reference architecture for telecom workloads. Cyborg is important for their work to be able to utilize hardware acceleration resources. We are planning to use the Train version of OpenStack projects including Cyborg and it would be great to be able to switch to the v2 API as v1 is deprecated now. If my understanding is correct the v2 API implementation in Train is partial, but the documentation[2] doesn’t give accurate view about what is included. The CNTT team would like to be able to integrate and access the whole v2 API if that is possible. It would be great to discuss the options that we could use on the way forward. Would it be possible to bring this up and discuss on an upcoming Cyborg team meeting? Thanks, Ildikó [1] https://www.lfnetworking.org/about/cntt/ [2] https://docs.openstack.org/cyborg/train/api/api.html#v2-0