Thursday, 2020-07-09

*** tetsuro has joined #openstack-cyborg00:27
*** Yumeng has joined #openstack-cyborg01:42
*** ollivier has joined #openstack-cyborg02:23
*** tetsuro has quit IRC02:55
*** brinzhang has joined #openstack-cyborg02:55
*** swp20 has joined #openstack-cyborg02:56
*** wangzhh has joined #openstack-cyborg02:57
Yumenghi ildikov, wangzhh, swp20 brinzhang  ^^02:59
brinzhanghi Yumeng ^^02:59
swp20hi Yumeng02:59
brinzhanghi ildikov, welcome to cyborg irc meetting03:00
Yumenghi ollivier, welcome!03:00
brinzhangollivier: welcome too^03:01
Yumengseems we've got enough people. let's get started!03:01
ildikovand thank you :)03:01
Yumeng#startmeeting openstack-cyborg03:01
ollivierThank you03:01
openstackMeeting started Thu Jul  9 03:01:20 2020 UTC and is due to finish in 60 minutes.  The chair is Yumeng. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:01
*** openstack changes topic to " (Meeting topic: openstack-cyborg)"03:01
openstackThe meeting name has been set to 'openstack_cyborg'03:01
Yumengagenda for today
brinzhang#info brinzhang03:02
Yumengwe wil mainly discuss cyborg support in CNTT today and then SPEC review.03:02
ollivier#info Cédric Ollivier03:02
ildikov#info Ildiko Vancsa03:02
Yumeng#info Yumeng03:02
Yumeng#topic cyborg support in CNTT03:03
*** openstack changes topic to "cyborg support in CNTT (Meeting topic: openstack-cyborg)"03:03
ildikovthanks for adding this topic to today's agenda03:03
ildikovollivier and I, we are both involved in the CNTT community03:04
brinzhangildikov, ollivier: you can briefly introduce yourself03:04
Yumengildikov: ^^ my pleasure.03:04
ildikovfor background about CNTT:
ollivierI'm LFN board member, OPNFV functest PTL and I lead a couple of CNTT stream03:06
ildikovI myself work for the OpenStack Foundation and focus on telecom and edge related efforts among some other things03:06
ildikovI've been also involved in OPNFV as well as CNTT03:06
ollivierI'm contributing t the CNTT reference architecture for OpenStack which are especially listing the mandatory services, features/capabilities and their versions/microversions03:07
brinzhangthanks, may you are all experts in VNF/NFV03:08
ildikovCNTT has a strong focus on cloud infrastructure to define reference model and architectures that telecom operators can rely on03:08
ollivierI'm also well involved to the related conformance test suite (mostly leveraging the main tempest tests and plugins)03:08
ildikovbrinzhang: ollivier more than I am :)03:09
Yumengildikov: yeah cool. we've met before in the edge discussions.  ollivier: cool, hope we can discuss in cyborg related tempest  in CNTT support.03:09
ildikovas I briefly described on the mailing list hardware acceleration is an important capability for telco use cases especially with 5G and edge and therefore CNTT is looking into including Cyborg in the architecture03:10
brinzhangildikov: thanks, it is always good to know that you are good at something.03:10
ildikovand we ran into a bit of a challenge as CNTT is currently moving to Train, but would like to use the v2 API for Cyborg to avoid switching between API versions later03:11
ollivierYumeng: cyborg tempest plugin could be on my Functest agenda03:11
*** brinzhang_ has joined #openstack-cyborg03:11
Yumengollivier: great! that's also one of our important in this release!03:11
ildikovso we wanted to see what options we have with the Train version03:12
brinzhang_yes +1 Yuemng03:12
*** songwenping_ has joined #openstack-cyborg03:12
ollivier(Functest supports U-release and master)03:12
Yumengildikov: yes, we started to deprecate V1 API from Train release, and removed V1 in Ussuri release. here is the new V2 API:
ollivierYes. we can hardly leverage an already deprecated API (v1) and then we would have targeted Cyborg v2 and its microversion support which fit our model03:13
ollivierI read the thread "Incomplete v2 API in Train""03:13
ollivierI would ask for a few clarifications (sorry for that).03:14
brinzhang_olivier: Do you have any plans to upgrade to U release03:14
ildikovYumeng: yes, we are aware of the deprecation03:14
ollivierout of Baraque (September).03:14
Yumengildikov: I was not clear why CNTT chose Train. from my perspective. as I replied in maillist, I would recommend CNTT use Ussuri with complete API and functionality.03:15
ollivierYes we will keep rolling the OpenStack releases according to our criteria (possibly 6 months later)03:15
*** brinzhang has quit IRC03:15
brinzhang_We are introducing the v2 API and perfecting it. If we can choose to upgrade to Ussuri, it may be the best.03:15
*** swp20 has quit IRC03:15
Yumengollivier: yes sure, please go ahead. if we can help in the V2 API clarifications03:16
ollivierYumeng: I am sending you our criteria. Ussuri is too new regarding our criteria03:16
ildikovYumeng: brinzhang_: when it comes to Telecom environments operators need hihgly stable platforms and available commercial support among other criteria03:17
ollivierWhen you mention it's incomplete, I'm not sure if v2 could backport it to Train at lest from a theorical point of view.03:17
Yumengollivier: alright. got it.03:18
ildikovthis usually prevents that community to stay close to master or use the latest release both in production environments and even in CNTT unfortunately03:18
ildikovI hope it will improve in the future03:18
ollivierDoes it depend on specific service Ussuri versions (e.g. nova)?03:19
brinzhang_ildikov: I think you can  backport the v2 api to Train, but there are many patches you should backport to Train03:19
ildikovbrinzhang_: do you mean backporting downstream?03:20
brinzhang_I can be sure that the API for backport v2 downstream should work, but the function of interacting with nova may not be backport, it depends on nova version and other related packages03:21
brinzhang_If you want to use nova-cyborg-interaction feature, I suggest you upgrade your platform03:22
Yumengfrom cyborg's perspective, just backport V2 API to Train is theorically possible, but the nova-cyborg integration is not that easy if backport to train(which needs nova's help and may affect much).03:22
ollivierHere I would consider first the backport in Cyborg stable/ussuri03:22
ollivierWould it also ask for backports in Nova as well?03:23
*** shaohe_feng has joined #openstack-cyborg03:23
shaohe_fenghi all03:24
ildikovas CNTT is consuming upstream code but not maintaining patches locally at this point I'm not sure downstream backport is an option03:24
brinzhang_Unless you don’t want to use the nova-cybrog-interaction feature03:24
shaohe_fengconflict with other meeting.03:24
Yumengbrinzhang_:yes, +103:24
Yumenghi shaohe_feng: no pb.03:25
ildikovbrinzhang_: what's included in the nova-cybrog-interaction feature?03:25
ildikovbrinzhang_: I assume some API endpoints depend on it?03:25
Yumengildikov: nova operations like creating a VM with accelerator(provisioned by cyborg) , this kind of function depends on nova/ussuri version03:26
brinzhang_ollivier: Whether it is nova or cyborg, I think it can be used from Ussuri backport to stable/Train, but it will definitely encounter problems, I think it needs to be seriously considered.03:27
ollivierbrinzhang_: It's just checking what's doable. It would ask for backports in both Cyborg and Nova which seem quite serious.03:28
brinzhang_ildikov: agree with Yumeng, if you dont want to use nova-cyborg-interaction, I think you dont worry about to backport the cyborg V2 api to stable/train03:28
Yumengnova-cybrog-interaction feature will affect creation, deletion, soft reboot, hard reboot, VM wih accelerators this kind of operations
ildikovYumeng: thanks for the clarification, I believe that feature would be very much in our interest03:29
Yumengpls check supported operations in the link above.03:29
ildikovollivier: I assume you mean backproting upstream, right?03:29
*** s_shogo has joined #openstack-cyborg03:30
brinzhang_ollivier: yes, the nova-cyborg-interaction feature is big, you can see
s_shogosorry for late03:30
shaohe_fengildikov what's your openstack version?03:30
ollivierildikov: yes as you mentioned, here it's only about the OpenStack projects. All operators are free to backport by themselves but it would be out of CNTT.03:31
Yumengildikov: does CNTT wanna support full function now or like half a year later?03:31
olliviershaohe_feng: Train for our next release (September)03:31
Yumengok. got it.03:32
ildikovYumeng: the aim is full support, but the question is if it is doable or not03:32
shaohe_fengseems it is mor easy for Train03:32
ildikovYumeng: if upstream backport is not an option then our interest would be to fix up the documentation for Cyborg to be clear about what is available in Train03:33
shaohe_fengseems it is easier for Train03:33
*** xinranwang__ has joined #openstack-cyborg03:33
Yumengildikov: yes, that would be easier as a start! I can help.03:33
xinranwang__Hi all.03:33
ollivierYumeng: yes we will keep rolling. As far as I understand, waiting CNTT to select U or newer seems the best option03:33
Yumengollivier: agree!03:34
Yumenghi xinranwang__03:34
xinranwang__Sorry for late.03:34
xinranwang__Just finish another meeting03:34
brinzhang_xinranwang_, shaohe_feng, s_shogo: Just right~03:35
ollivier1 to fix
ollivier"Updated Cyborg APIs to version 2" should be removed as we just discussed, right?03:36
Yumengxinranwang__,s_shogo: no worries.03:36
brinzhang_ollivier: yeah, thanks, you can update that, it's not very accurate03:37
ollivierI would think that "" is possible wrong too. "see The Train release introduces version 2.0 APIs. Details of these APIs can be found here."03:37
Yumengwe did update part of APIs to version2, do you wanna a detailed list saying what are removed to V2, what are not yet03:37
ildikovollivier: +1 on U or newer for CNTT03:37
ildikovYumeng: the Train docs refers to the spec I think when it comes to the API and it is misleading in terms of what is available in Train03:38
ollivierYumeng: yes please. I'm always lost when we say that an API version is divided into 2 releases03:38
brinzhang_ollivier: thanks point this.03:39
ildikovYumeng: it would be better I think to be explicit and have the proper API documentation for Train with the available functions03:39
brinzhang_Yumeng: We need to clarify which APIs in Train support V2 and which are completed in Ussuri.03:39
ildikovollivier: +103:39
ollivierHow can we somehow deprecate v1 if v2 is partial?03:40
brinzhang_As I know, deprecate the v1 API until we completed the v2 API in Ussuri03:41
brinzhang_In v1, some attribute cannot support to request03:41
xinranwang__v1 api does not match current data model. We have  changed data model pretty much, that 's why we need a new set of api(v2) as well03:43
Yumengildikov: here it is the list. Train supports limited V2 APIs : Device Profiles API and Accelerator Requests APIs. and Ussuri supports full V2 APIs: Device Profiles API and Accelerator Requests APIs and Devices APIs, Deployables APIs,03:43
xinranwang__I agree that we should clarify this in document03:43
YumengI will update documentation today to clarify.03:43
ildikovthanks Yumeng03:44
songwenping_ollivier you can find corresponding api in v2 for deprecate v1.03:44
brinzhang_Yumeng: thanks03:44
ollivierok v2 is well a superset of v1 (from operations point of view).03:44
ildikovI think it will be a big improvement to have the documentation uodated03:44
ollivierJust a last question: Device Profiles v2 API and Accelerator Requests v2 APIs were released in Train, right?03:45
brinzhang_ildikov: thanks, Improve the readability and accuracy of the document, this is what we have been doing.03:45
Yumengollivier: yes. they are released in Train.03:45
ollivierand the microversion support?03:46
ollivierTrain as well?03:46
ollivierIt should be03:47
Yumengollivier: nope. microversion is released in Ussuri03:47
xinranwang__microversion is in U03:47
ollivierok it's very clear. Then your release notes are quite ok if we consider the time you wrote them (before ussuri). Mentioning the API capability (Device Profiles API and Accelerator Requests APIs) could enhance it a litlle bit.03:49
ollivierAbout Functest, I could integrate your tempest plugin in Functest Kali (U-release) or Functest master (next Victoria) but I'm not clear how I can gate it (specific hardware?)03:51
ollivierI will check the devstack configuration. It would allow integrating the testing part in advance until CNTT selects U or newer.03:52
Yumengollivier: not necessary to use specific hardware, current tempest-plugin is using a fake driver(you can understand it as a fake device) to test the cyborg workflow03:53
ildikovollivier: I think testing on specific hardware would require third-party CIs, I don't think our infra has those type of resources available03:54
Yumengcyborg-tempest-plugin(U-release) should work fine. since it is complete to do test for the basic cyborg workflow and cyborg-nova integration workflow03:54
Yumengildikov: yes, exactly03:54
ollivierYumeng: great. That shouldn't be a challenge in that case. I will have a look to your testing plugin before my holidays (in a couple of days)03:55
Yumengok. cool03:55
ildikovLooks like we have a plan :)03:55
ollivierildikov: at least we could in OPNFV (I think OpenStack as well). Here it's more about verifying the test integration in Functest SUT. If we can select fake drivers, it should work easily.03:56
ildikovollivier: yeah, it would be great to make it work in Functest so when CNTT gets to U and newer we already have that figured out03:57
ollivierYes very clear on my side. Thank you. I will give you my feedback about the testing part.03:57
Yumenggreat! ping me at this channel if you have more questions.^^03:57
ollivierYumeng: sure03:57
ildikovthanks Yumeng and team!03:57
ollivierildikov: yes that's the best model03:58
Yumengildikov,ollivier: you are welcome :)03:58
ollivierThank you all03:58
ollivier(Sorry for the second topic)03:59
Yumenghaha. no pl.  the rest topic from my side for today would be the review03:59
ildikovollivier: and thank you for getting up this early :)03:59
ollivierildikov: my pleasure. it's quite the same for you, right?04:00
ildikovollivier: yep04:01
Yumengshaohe, xinran, wangzhh, and all: we need review specs and get them merged. Add Attribute API specification, Add Inspur® FPGA driver specification. Add Intel QAT driver specification.04:02
Yumengand also shogo's program V2 patch. that's for milestone-204:03
xinranwang__Ok, will do this04:04
Yumengthat's all from my side. Does anybody want to bring up anything else?04:04
Yumeng#topic AoB04:04
*** openstack changes topic to "AoB (Meeting topic: openstack-cyborg)"04:04
Yumengalright. if nothing else, let's wrap up this meeting and I'll see you all again next week04:05
YumengThank you all. Have a good day or night.04:05
*** openstack changes topic to "Pending patches (Meeting topic: openstack-cyborg)"04:06
openstackMeeting ended Thu Jul  9 04:06:06 2020 UTC.  Information about MeetBot at . (v 0.1.4)04:06
openstackMinutes (text):
*** tetsuro has joined #openstack-cyborg04:34
*** brinzhang0 has joined #openstack-cyborg05:13
*** songwenping__ has joined #openstack-cyborg05:13
*** songwenping_ has quit IRC05:16
*** brinzhang_ has quit IRC05:16
*** songwenping__ has quit IRC05:16
*** swp20 has joined #openstack-cyborg05:18
*** links has joined #openstack-cyborg05:43
*** songwenping_ has joined #openstack-cyborg05:53
*** swp20 has quit IRC05:57
*** brinzhang_ has joined #openstack-cyborg05:59
*** songwenping__ has joined #openstack-cyborg06:01
*** brinzhang0 has quit IRC06:03
*** s_shogo has quit IRC06:03
*** songwenping_ has quit IRC06:04
*** wangzhh has quit IRC06:10
*** brinzhang0 has joined #openstack-cyborg06:48
*** brinzhang_ has quit IRC06:51
*** ildikov has quit IRC06:55
*** ildikov has joined #openstack-cyborg06:58
*** xinranwang__ has quit IRC07:44
*** shaohe_feng has quit IRC07:53
*** gmann has quit IRC08:03
*** gmann has joined #openstack-cyborg08:06
*** songwenping_ has joined #openstack-cyborg08:17
*** songwenping__ has quit IRC08:20
*** songwenping__ has joined #openstack-cyborg08:25
*** songwenping_ has quit IRC08:28
*** tetsuro has quit IRC08:38
openstackgerritYumengBao proposed openstack/cyborg master: update API documentation
*** songwenping_ has joined #openstack-cyborg08:54
*** songwenping__ has quit IRC08:57
*** songwenping__ has joined #openstack-cyborg09:07
*** songwenping_ has quit IRC09:10
*** swp20 has joined #openstack-cyborg09:11
*** songwenping__ has quit IRC09:13
*** songwenping_ has joined #openstack-cyborg09:39
*** swp20 has quit IRC09:42
*** jraju__ has joined #openstack-cyborg09:57
*** links has quit IRC09:58
*** songwenping__ has joined #openstack-cyborg10:14
*** songwenping_ has quit IRC10:17
*** songwenping__ has quit IRC11:15
*** songwenping__ has joined #openstack-cyborg11:16
*** songwenping_ has joined #openstack-cyborg11:25
*** songwenping__ has quit IRC11:28
*** songwenping__ has joined #openstack-cyborg11:42
*** songwenping_ has quit IRC11:45
*** songwenping_ has joined #openstack-cyborg11:52
*** songwenping__ has quit IRC11:55
*** songwenping__ has joined #openstack-cyborg12:14
*** songwenping_ has quit IRC12:17
*** songwenping_ has joined #openstack-cyborg13:13
*** songwenping__ has quit IRC13:17
*** songwenping__ has joined #openstack-cyborg13:35
*** songwenping_ has quit IRC13:38
*** jraju__ has quit IRC14:57
*** songwenping_ has joined #openstack-cyborg17:16
*** songwenping__ has quit IRC17:19
*** ollivier has quit IRC17:20
*** songwenping__ has joined #openstack-cyborg19:13
*** songwenping_ has quit IRC19:16
*** Yumeng has quit IRC20:13
*** songwenping_ has joined #openstack-cyborg21:26
*** songwenping__ has quit IRC21:29

Generated by 2.17.2 by Marius Gedminas - find it at!